Fallout 1 FIXT megamod for Mac OSX?

V

VaultBoy2507

First time out of the vault
Does anyone know if there is a way of installing the FIXT Megamod for the OSX GOG.com version of fallout 1?

Thus far, I've had no luck!

Much appreciated!
 
Ah! I see :(

I don't suppose you happen to know any of the patches that are available on OS X?

I'm desperate for these fixes/additions of cut content etc!
 
I'm not sure, but as long Sduibek used only the traditional scripts Fallout handle (I don't know if there are extensions for Fallout 1, but there certainly are for Fallout 2 through sfall), the cut content and fixes (except engine fixes, that is) should be able to run on the Mac version. What I don't know is how to install them.
 
Yeah, I'm on the same boat with regards to installation!
I tried using WineSkin and installing them through that (rather foolishly!), but it only corrupted the files and made it unplayable! Hopefully I'll find a way to do it soon!

Thanks for your help though!
 
Same here I sure hope the author can make a way to wrap it so it will work with the GOG versions of 1&2
 
The closest thing to a MacOS(X) version is to install on a Windows system and then manually move everything over. Which is a total pain in the ass, I know.

The other problem is I don't think Sfall works on Macs (this is what allows speed change of game and some mouse/keyboard options) and I'm not sure about f1_res (high resolution patch) working either.

I am open to the idea of getting it going on MacOS(X), but I need someone to tell me a good installer for that operating system. I'm using Inno Setup for my installer currently. If someone good with Macs could write an installer for me, that would be even better :grin: :grin: :grin:

I could make a self-extracting version for MacOS, but it wouldn't have any of the customizations that the current version has, because of not having an installer. I would just include some template configurations.

For the time being, the patches you want if you can't use mine:
(in this order)
No Children Fix
TeamX 1.2.1
TeamX 1.3.5
TeamX NPC 3.5
​
 
Hmm, I'm afraid I can't offer any advice on installers! :(

BUT (though I can't speak for everyone) I would be more than happy with template configurations as opposed to fuller customisations if it were to work.

In the meantime I'll definitely check out those patches!! Thanks for the help :D

I played fallout when it came out on PC and having moved to Mac years ago, I'm just happy it's finally become available on OS X as opposed to paying £60+ on eBay for the PowerPC version for mac!
 
Hi guys, I too am in the same boat, here is what I've tried:

Fallout 1:
Download from GOG - Worked fine
Download from GOG > Updated Wineskin Wrapper - Worked fine
Download from GOG > Updated Wineskin Wrapper > Updated Wineskin Engine - Black screen/flicker glitch
Download from GOG > Installed FIXIT 6.1 - Loaded fine, tried to change screen settings and it crashed
Download from GOG > Installed FIXIT 6.1 > Updated Wineskin Wrapper - Black screen/flicker glitch
Download from GOG > Updated Wineskin Wrapper > Installed FIXIT 6.1 - Error messages in beginning

Fallout 2:
Download from GOG - Worked fine
Download from GOG > Updated Wineskin Wrapper - Worked fine
Download from GOG > Updated Wineskin Wrapper > Updated Wineskin Engine - Did not load
Download from GOG > Installed RP 2.2 - Graphics error
Download from GOG > Installed RP 2.2 > Updated Wineskin Wrapper - Graphics error
Download from GOG > Updated Wineskin Wrapper > Installed RP 2.2 - Graphics error

I've been testing all night :P
 
Last edited:
Converseallstar95 said:
Hi guys, I too am in the same boat, here is what I've tried:

Fallout 1:
Download from GOG - Worked fine
Download from GOG > Updated Wineskin Wrapper - Worked fine
Download from GOG > Updated Wineskin Wrapper > Updated Wineskin Engine - Black screen/flicker glitch
Download from GOG > Installed FIXIT 6.1 - Loaded fine, tried to change screen settings and it crashed
Download from GOG > Installed FIXIT 6.1 > Updated Wineskin Wrapper - Black screen/flicker glitch
Download from GOG > Updated Wineskin Wrapper > Installed FIXIT 6.1 - Error messages in beginning

Fallout 2:
Download from GOG - Worked fine
Download from GOG > Updated Wineskin Wrapper - Worked fine
Download from GOG > Updated Wineskin Wrapper > Updated Wineskin Engine - Did not load
Download from GOG > Installed RP 2.2 - Graphics error
Download from GOG > Installed RP 2.2 > Updated Wineskin Wrapper - Graphics error
Download from GOG > Updated Wineskin Wrapper > Installed RP 2.2 - Graphics error

I've been testing all night :P
Click to expand...

Following the steps listed here might help http://falloutmods.wikia.com/wiki/F2RP_Technical_Info.
 
Converseallstar95 said:
Hi guys, I too am in the same boat, here is what I've tried:

Fallout 1:
Download from GOG - Worked fine
Download from GOG > Updated Wineskin Wrapper - Worked fine
Download from GOG > Updated Wineskin Wrapper > Updated Wineskin Engine - Black screen/flicker glitch
Download from GOG > Installed FIXIT 6.1 - Loaded fine, tried to change screen settings and it crashed
Download from GOG > Installed FIXIT 6.1 > Updated Wineskin Wrapper - Black screen/flicker glitch
Download from GOG > Updated Wineskin Wrapper > Installed FIXIT 6.1 - Error messages in beginning
Click to expand...

Similar issues here too. I'd like to note (especially to Sduibek) that the current OSX version from GOG.com is built on WINE and is thus basically the same as the Windows version. This is apparantly because the OSX port is built for PowerPC architechture and doesn't run on new versions of OSX.

There are some problems though. Everything seems to work with the GOG version, and even after installing the Hi-Res Patch 4.1.7 there seem to be no problems. But with FIXT 6.4 installed on top of the GOG version there are various graphical issues. With default settings (GRAPHICS_MODE=1) the graphics are only updated when the mouse is clicked, resulting in black screen and/or seriously jerky graphics, depending on how fast you can click. :)

Setting to GRAPHICS_MODE=0 fixes the previous issue, but replaces it with seriously warped palette, and none of the palette fixes seem to work (at least on WINE). GRAPHICS_MODE=2 breaks the palette in a different way, but it didn't work with GOG version+Hi-Res Patch either. Oh, and changing the COLOUR_BITS won't help either.

The issue is most likely very much connected to WINE, but since it doesn't happen without FIXT, I'm thinking there's something there too. But I'm stuck on how to debug/fix it.
 
@zarr, what about if you remove ddraw.dll and ddraw.ini from your Fallout folder, does that help the graphical issues to go away?
 
Last edited by a moderator:
Nope, the issues still remain. Sfall works though, because if I don't remove those files, I can pick different display modes. Dx9 mode doesn't actually have either of the mentioned issues (lazy updates, glitchy palette), but the video clips are horribly corrupted.

Another issue, independent of the graphic issues, is that entering the game preferences crashes the game. This also doesn't happen before installing FIXT.

--EDIT--

Wow, it seems that the GOG guys had rolled their own ddraw.dll to fix the issues. Replacing FIXT-installed Sfall-ddraw.dll with the original GOG version and changing GRAPHICS_MODE to 0, graphics seem ok. The issue of game preferences still remains though. Also there is no FOW in the first level, but I'm not sure if this is an issue or a feature.
 
Last edited:
It sounds like maybe one of the settings I provide in f1_res.ini isn't playing nice on some Mac systems. If you replace the f1_res.ini with default and the crashes go away, you could change them back to FIXT defaults one at a time and see which one is causing it.

(so, move your f1_res.ini to somewhere else, download f1_res from here, then open up each ini side-by-side. See which settings are different and one at a time, change it to whatever the FIXT f1_res.ini had, open the game, see if it crashes. Repeat. That's what I would do if it were my system.)
 
Last edited:
The crash in game preferences happens even if I disable the hires patch completely, so that doesn't seem to be the reason.

--EDIT--

I examined the crash a bit on a debugger, but all I can get is that a pointer seems to be zero, causing the crash. Initializing the pointer to readable memory (through the debugger) prevents the crash, but I have no idea what the real effect of the pointer is. And there may still be other similar crashes waiting to be uncovered. Doesn't look too promising.

--EDIT2--

It seems that this crash is prevented by removing DATA/DATA/VAULT13.GAM entirely. The file is empty anyway, so this shouldn't probably affect gameplay? So the only features lost will be from Sfall when the ddraw.dll is replaced with the original from GOG installation?

--EDIT3--

Well, at least the FOW is back after removing DATA/DATA/VAULT13.GAM, so there obviously is some effect...
 
Last edited:
What does FOW mean?

Vault13.gam is absolutely essential to the game working properly, and the file should not be empty. I don't know how or why that happened. This is the file that holds the list and starting value of all the game's global variables.
 
Sduibek said:
What does FOW mean?

Vault13.gam is absolutely essential to the game working properly, and the file should not be empty. I don't know how or why that happened. This is the file that holds the list and starting value of all the game's global variables.
Click to expand...

Fog Of War. The darkness. The cave was completely lighted so I could see all the enemies from the start position. But that would probably have something to do with the missing variables. I'll have to check how the files install on a Windows machine, maybe there's an extraction error. The game seemed pretty playable without the file. Didn't test that far yet though.
 
Ah, okay, thank you.

The most likely thing I can think of is that the installer runs sed.exe to modify a bunch of the file's entries.... it's a Windows creation of an already-existing Linux application.

Maybe WINE doesn't like running Windows-compatible versions of Linux executables? It's a stretch, but the only idea I have at the moment. :(

If you'd like, I can create a test version of the installer that runs these commands unhidden and pauses after each, so you could see if the commands line executions are causing errors.
 
Last edited:
That sounds like a very plausible explanation. It could be that the sed.exe requires some library or runtime that doesn't exist in the WINE environment.

The mentioned test installer would totally help in uncovering the issue.
 
You must log in or register to reply here.
Back
Top