It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like:Chrome,Firefox,Internet Explorer orOpera

×
arrow-down2arrowcart2close4fat-arrow-leftfat-arrow-rightfeedbackfriends2happy-facelogo-gognotificationnotifications-emptyownedremove-menusad-facesearch2wishlist-menuwishlisted2own_thingsheartstartick
high rated
I've put together a Wine wrapper for Fallout 3, allowing it to be played on Linux almost like a native game & with no Wine knowledge required.

Simply place the script, resource archive and installer files together in the same directory & run the script. The output is a directory containing a "GOG-style" ready-to-go Wine-wrapped version of the game (the build script also has the option to create a tarball of the assembled game package); from there installation is simply a case of moving the directory to wherever you want it installed to - then just run the start script to play, create a shortcut for the game, access the advanced options etc :)

(to uninstall simply delete the game directory and any shortcuts you created, and the game's user data directory in ~/.local/share if you don't want to keep your saves & settings)

Running the start script with the argument "play" will bypass the menu and start the game immediately (this is the default setting for shortcuts created by the script).

User saves are stored under ~/.local/share/fallout3

Full details are in the readme.txt and release notes. Here is the download link:

fallout3_wine.tar.xz
(13.5 kB, SHA256: 9cf88b6f5ab4e4acd14696c5da23f4cfe9db88c2f7f6417d053d62233dd0e2cb)

Updated 2017/11/01: Some small improvements to the build script and documentation. A small tweak has been made that should improve performance on systems using the open graphics drivers.

The wrapper uses Wine Staging 2.0 with CSMT enabled. Wine and Winetricks will be downloaded automatically if not present; to avoid redownloading for other scripts the downloaded Wine package will be stored in ~/.cache/winewrap

In addition to Wine and Winetricks, Wine Mono will also be downloaded. This will be stored in ~/.cache/wine to save having to redownload it if it's needed again for something else.

If anyone runs into any problems then post in this thread, Adamhm's Linux Wine Wrappers - News, FAQ & Discussion and/or The "Judas™ does this run in Wine" thread v1.173.

(note that in addition to the issues listed in the release notes I've since found that some minor radio stations (e.g. relay tower broadcasts) may not work, and some can cause the game to crash. Make sure to save before attempting to listen to those just in case)

Using Fallout Script Extender (FOSE)

The start script includes options for running custom commands and creating custom shortcuts for mods, tools/utilities etc. such as FOSE. To use FOSE with this wrapper:

- Install FOSE into the game's directory inside the Wine prefix as you would on Windows (this can be found at <wrapper dir>/prefix/drive_c/Fallout 3)
- You can then launch it by running the start script with the argument: runwine=fose_loader.exe
- You can create a shortcut to use FOSE automatically. Run the start script with no arguments to bring up the menu, select the option to create a shortcut, and set the shortcut arguments to: runwine=fose_loader.exe

This approach can be used for running other launchers & mod managers etc. Read the release notes for more details on the various launch options and script features.

For more of my Linux Wine wrappers (including wrappers for Fallout 1, 2, Tactics and New Vegas) see my GOGmix: adamhm's Linux Wine wrappers. Also check out Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion
Post edited November 01, 2017 by adamhm
avatar
adamhm: As this was just released here today this has had very little testing so updates/tweaks are likely, but I've used my retail copy (with a crack & disabled GFWL) in Wine for a long time now and it mostly runs great so I'm assuming there shouldn't be any major problems with the GOG version either.
Don't bet on that, at least not with "New Vegas".

I've made the mistake of assuming they didn't tamper too much with the files but I seem to have been wrong.

It installs on WinXP but when trying to run it I get:

QueryFullProcessImageNameA in DLL "Kernel32.dll" not found
Well, shit...
GOG may have broken something.

Now trying with WINE...
Post edited June 01, 2017 by Klumpen0815
avatar
Klumpen0815: Well, shit...
GOG may have broken something.

Now trying with WINE...
It seems to run just as well in Wine as it's ever done here. Fallout: New Vegas seems to work great too :)
avatar
Klumpen0815: Well, shit...
GOG may have broken something.

Now trying with WINE...
avatar
adamhm: It seems to run just as well in Wine as it's ever done here. Fallout: New Vegas seems to work great too :)
The "PlayOnLinux" setup/pre-config for New Vegas doesn't work either. :(

Edit: Nevermind, found it:
https://www.gog.com/forum/fallout_series/fallout_new_vegas_for_linux

Will try.
Post edited June 01, 2017 by Klumpen0815
avatar
Klumpen0815: <snip>
Ganni1987 reported that he needed to add an override to disable winegstreamer to prevent Oblivion from crashing frequently. I heard similar stories about Fallout 3 crashing in Wine unless that was disabled, although they all work fine here without doing that. I'll do some testing & if it doesn't seem to cause any detrimental effects here I'll probably update all 3 wrappers to disable it by default.
Post edited June 01, 2017 by adamhm
Hey adamhm,

Very nice to see someone working on such scripts. Question for you: Did you ever managed to run Fallout 3 under Wine with an Intel HD? There is a patch for F3 that works under Windows, it includes a patched dll as far as I remember and loading it with WINEDLLOVERRIDE didn't change the crash after starting a new game. I never tried it on this machine (HP 350 G1), since there was never Windows on it. WineHQ closed the related bug claiming it wasn't relevant, since the specifications did not mention Intel HD. I have no problem running Fallout NV, but that's quite different.

I think your scripts would benefit from using some arrays, especially for the repetitive file/version checking. Let me know if you're interested.
avatar
Klumpen0815: <snip>
avatar
adamhm: Ganni1987 reported that he needed to add an override to disable winegstreamer to prevent Oblivion from crashing frequently. I heard similar stories about Fallout 3 crashing in Wine unless that was disabled, although they all work fine here without doing that. I'll do some testing & if it doesn't seem to cause any detrimental effects here I'll probably update all 3 wrappers to disable it by default.
I had the same problem with Oblivion.
avatar
emeres: Very nice to see someone working on such scripts. Question for you: Did you ever managed to run Fallout 3 under Wine with an Intel HD? There is a patch for F3 that works under Windows, it includes a patched dll as far as I remember and loading it with WINEDLLOVERRIDE didn't change the crash after starting a new game. I never tried it on this machine (HP 350 G1), since there was never Windows on it. WineHQ closed the related bug claiming it wasn't relevant, since the specifications did not mention Intel HD.
I just tested on an i3-6100 system with HD 530 graphics; the game starts but unfortunately crashes on trying to start a new game. This was on Mint 18.1 with kernel 4.10.0-21 using Mesa 17.1.1 from Padoka's stable Mesa PPA.
avatar
emeres: I think your scripts would benefit from using some arrays, especially for the repetitive file/version checking. Let me know if you're interested.
Thanks for the offer :) I did consider doing something like that, but I'm not sure it would make enough of a difference to be worthwhile. The build scripts in particular haven't really changed much since the first wrappers I did so they're still pretty basic, as it hasn't been a problem to just drop in parts or search+replace to update/modify as needed.
avatar
Klumpen0815: I had the same problem with Oblivion.
I already updated the wrappers to disable it, as disabling it doesn't seem to cause any problems :)
Post edited June 04, 2017 by adamhm
This is just awesome. Thanks so much adamhm!
avatar
adamhm: I just tested on an i3-6100 system with HD 530 graphics; the game starts but unfortunately crashes on trying to start a new game. This was on Mint 18.1 with kernel 4.10.0-21 using Mesa 17.1.1 from Padoka's stable Mesa PPA.
Thanks for the info. In the end the registry vendor and device id override seems to work. I used the wrong format for my registry file for F3. In case anybody is interested, this should work:

[code]
REGEDIT4

[HKEY_CURRENT_USER\Software\Wine\AppDefaults\Fallout3.exe\Direct3D]
"VideoPciDeviceID"=dword:00000402
"VideoPciVendorID"=dword:000010de
REGEDIT4
[/code]

Load the entries with regedit 'Fallout 3.reg', where 'Fallout 3.reg' holds the above content. WINEPREFIX has to point to the prefix holding F3 installation as well, obviously.
avatar
adamhm: Thanks for the offer :) I did consider doing something like that, but I'm not sure it would make enough of a difference to be worthwhile. The build scripts in particular haven't really changed much since the first wrappers I did so they're still pretty basic, as it hasn't been a problem to just drop in parts or search+replace to update/modify as needed.
It should be easier to maintain the scripts. I have a good example here should you change your mind github repository.

Edit: fixed link
@admin GOG has no code tags? Change to whatever is equivalent.
Post edited June 05, 2017 by emeres
avatar
emeres: Thanks for the info. In the end the registry vendor and device id override seems to work. I used the wrong format for my registry file for F3. In case anybody is interested, this should work:
I'll add that to the first post :) With my wrapper just run the start script to bring up the menu, select "Advanced options..." --> Registry Editor and then import it from there.

avatar
emeres: It should be easier to maintain the scripts. I have a good example here should you change your mind github repository.
Thanks - I'll take a look.
avatar
emeres: Thanks for the info. In the end the registry vendor and device id override seems to work. I used the wrong format for my registry file for F3. In case anybody is interested, this should work:
avatar
adamhm: I'll add that to the first post :) With my wrapper just run the start script to bring up the menu, select "Advanced options..." --> Registry Editor and then import it from there.
Should the application specific key not work, the general might.
Change HKEY_CURRENT_USER\Software\Wine\AppDefaults\Fallout3.exe\Direct3D to HKEY_CURRENT_USER\Software\Wine\Direct3D.
avatar
emeres: Should the application specific key not work, the general might.
Change HKEY_CURRENT_USER\Software\Wine\AppDefaults\Fallout3.exe\Direct3D to HKEY_CURRENT_USER\Software\Wine\Direct3D.
I've now updated my wrapper's start script to automatically apply this workaround when it's being run on a system using an Intel GPU. An option to override the automatic setting is provided from the script's menu.
With the latest update this should now perform a bit better on systems using the open graphics drivers :)