I've put together Wine wrappers for Fallout, Fallout 2 and Fallout Tactics, allowing them to be played on Linux almost like native games & with no Wine knowledge required.

Simply run the build script to create the wrapper. If the installer files are not alongside the wrapper build files then the path to them will need to be specified either by passing it as an argument to the build script with -respath="<path>" or by setting an environment variable named WINEWRAP_RESPATH containing it. You can change the path to build the wrapper in and the name of the wrapper directory with the -buildpath= and -dirname= arguments. The build path can also be set with the WINEWRAP_BUILDPATH environment variable.

The output will be a directory containing the game set up within a preconfigured Wine prefix, along with its own copy of Wine, extracted game icons, documentation, and start script(s). From there simply run the start script to play. The start script also includes options for creating a shortcut, configuring the wrapper 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)

User saves are stored under ~/.local/share/fallout, ~/.local/share/fallout2, ~/.local/share/fallout_tactics

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

fallout_wine.tar.xz
(557.9 kB, SHA256: d1f88a674f1ef227ed2ff90979f62ac9e22dbd25df96e4879e9ceeb42e214df3)

fallout2_wine.tar.xz
(41.3 kB, SHA256: d1b9d6c8fb6770fb3dbe8213a07537f72049e8ca33c6fe7507d8e36454c209e0)

fallout_tactics_wine.tar.xz
(39.1 kB, SHA256: 7ee880230829e340bdbe9e35e98bc53d93d1311a7f3926393b46a485024e57aa)

Last updated 2021/07/11

The wrappers use Wine 6.0. 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.

Consider these to be very much beta releases for now- I only put them together yesterday so they've had very little proper testing. These games have worked great for me before though and have platinum ratings on WineHQ's AppDB so I'd be surprised if they have any problems. However if anyone does run into any problems then post in this thread, Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion and/or The "Judas&trade; does this run in Wine" thread v1.173.

Multiplayer in Fallout Tactics hasn't been tested & may or may not work (if not then installing DirectPlay through Winetricks might work).

For more of my Linux Wine wrappers check out post 3 in this thread: Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion

What about uninstalling the games?
In case of PlayOnLinux I just remove "virtual disk" (or whatever is the container I've installed the game into). In case of pure Wine installation I'm always a bit irritated by some leftovers, dropped shortcuts, remaining folders etc.

Delete game directory, delete any shortcuts you made, done. If you don't want to keep saves & settings delete the user data dir in ~/.local/share for the relevant game as well

Thanks for the awesome work, adamhm! +1
... and congrats to the 4th star :-)

Manny thanks adamhm! Could you tell me if the script works with the Fallout 1.5: Resurrection and if yes how to make them work properly? Thanks in advance1

It took some doing (tried a lot of things attempting to get it to work & almost gave up on it) but I think I've got it figured out. However it needs a risky DLL override that might result in some instability so I can't rule out problems occurring past the start...

1. Run the start.sh script and from the menu select "Advanced options...", then "Run...". Navigate to & select FoRes_EN_1_5_install.exe and click ok, then ok again to run the installer (Fallout 2 is installed to C:\Fallout 2). Don't bother creating any start menu entries or desktop shortcut, and don't launch it when it's done.

2. Run the start script again, "Advanced options" --> "Configure Wine". Under the libraries tab, in the "New override for library:" box enter "ddraw" then click "add". It'll warn about this, but say yes to it anyway. It should add an entry: ddraw (native, builtin). Click "apply" then "ok". This override will break the base game however - see below for an alternative solution.

3. From the game directory, go to prefix/drive_c/Fallout 2/Resurrection and open ddraw.ini in a text editor. Find the line that says: SingleCore=1 and change it to SingleCore=0, then save & exit.

4. Now it's about ready, but you should create shortcuts for it so it's not a hassle to play. Run the start script, select "Create shortcut..." and enter the following:

Shortcut name: Fallout 1.5 - Resurrection Configuration
Shortcut filename: fo15r-config.desktop
Shortcut arguments: runwine="fores_config.exe" cd="Resurrection"

I suggest placing this one in the game directory alongside the start script as you won't be needing it much. Do the same again to create a shortcut for the mod itself with these:

Shortcut name: Fallout 1.5 - Resurrection
Shortcut filename: fo15r.desktop
Shortcut arguments: runwine="fores.exe" cd="Resurrection"

Put this shortcut wherever you want it. If you want to use the mod's icon then before creating the shortcuts you'll need to open a terminal in prefix/drive_c/Fallout 2/Resurrection and run these two commands to extract it:

wrestool -x -t14 fores.exe -o fores.ico
icotool -x -i6 fores.ico -o ../../../../support/fores.png

Actually never mind - I attached it to this post for convenience, just save it & drop it into the support directory :) Then just select fores.png when creating the shortcuts.

Make sure to run the configuration tool before playing. When configuring it only use the recommended DirectDraw 7 32bit option - I encountered problems when trying any of the others.

Since the ddraw override breaks the base game, you might not want to use it all the time. So instead of following step 2 you can do this: after creating the shortcut for the mod, select the shortcut and do right-click-->properties (or open it in a text editor) and add this to the start of the launch command: env WINEDLLOVERRIDES="ddraw=native,builtin"

e.g. so that instead of this:

"/home/ad/Games/Fallout 2/start.sh" icon="fores.png" runwine="fores.exe" cd="Resurrection"

it's this:

env WINEDLLOVERRIDES="ddraw=native,builtin" "/home/ad/Games/Fallout 2/start.sh" icon="fores.png" runwine="fores.exe" cd="Resurrection"

I really appreciate all your effort at finding a solution for a mod installation, which is beyond your original intent. Many thanks.
Unfortunately, I can't test the solution (I was missing the override and singlecore points) because the fallout2_wine.sh is facing some error (not indicated) when testing SHA256 and then the files are not set up to install. I have tried the scrip when you posted at May 05 and it worked fine for a clean Fallout 2 install (without mods). Could you verify this please? Sorry for asking too much and thank you.

Make sure that both fallout2_wine.sh and fallout2_res.tar.xz are the latest versions and remove any existing directories named "Fallout 2" or "temp" in the same directory as them before running fallout2_wine.sh - the build script works fine on my systems here, it should output a message to the terminal if there are any problems.

If the previous version worked fine there shouldn't be any problems with the updated version & it's very odd for it to be failing at the resource test stage, which besides the updated checksum for fallout2_res.tar.xz is unchanged. What exactly happens when the build script fails on your system?

I don't get it too. The terminal panel simply closes after some seconds. The attached image is what I get before the terminal vanishes:

Open a terminal window in the directory where the script is so it doesn't close and run it using the command: "./fallout2_wine.sh"

Alternatively you can download & use this: https://www.dropbox.com/s/7kdamprrx3nmbzh/fo2-log.sh.tar.xz?dl=0

Simply extract it into the same directory as the other files & run it. It'll start the FO2 build script and direct the output into fo2-log.txt - once it exits post the contents here.

I now see the confusion I have made. When I said that I have used the script for Fallout it was meant to Fallout 1, not F2 as I said. And the script for F1 works nicely. But for Fallout 2 the checksum looks for a 'setup_fallout2_2.1.0.18' which does not exist. There is a setup_fallout_2.1.0.18 for F1 and a setup_fallout2_2.1.0.17 for F2. The script for F2 should look for the last one, ending with '17', not '18'. That explains why the script does not continue when checking (Ln 88).

Sounds like you need to download the newer version from GOG first then. The scripts were made to work with the latest versions of the installers and for Fallout 2 this is setup_fallout2_2.1.0.18.exe

Hmm, the lastest version avaiable to me is the setup_fallout2_2.1.0.17.exe. Notice that I have the Fallout Classic files (I bought them long before the Bethesda version).

Interesting, I just checked and the files appear to be the same between the classic + new entries for the other two games. It's probably a mistake so it might be worth contacting GOG support about it.