Posted June 04, 2018
adamhm
GOG for Linux
Registered: May 2009
From United Kingdom
oleerik
New User
Registered: Nov 2012
From Norway
adamhm
GOG for Linux
Registered: May 2009
From United Kingdom
Posted June 04, 2018
I suspect that there might be conflicts with newer packages in Ubuntu 18.04, since my wrapper uses a fairly old Wine release (2.21-staging). It works great here but I'm using Mint 18.3, which is essentially Ubuntu 16.04.
POL bundles some additional libraries with their Wine packages that may cause issues; I already remove libz* (and POL stopped bundling them with more recent releases) as those were a frequent source of problems for Arch users. You could try removing the rest of the bundled libraries and seeing if that helps - remove all the files from "Fallout 3/wine/lib/", leaving just the libwine.so.* libraries and the wine directory there.
If that doesn't work then my scripts have the ability to use alternative Wine builds for testing. I just checked with some newer builds and it looks like staging is still required, but Lutris' build will have to be used as POL have only recently started catching up with staging builds & don't have them all yet. Run the build script like this to have it use Wine Staging 3.8 from Lutris:
./fallout3_wine.sh -winever=staging-3.8 -winesource=lutris
If you do this you should run this command with the start script when it's done as redirecting wined3d.dll is no longer necessary for enabling CSMT (and it's not necessary to enable CSMT manually now either):
./start.sh runwine=reg : delete "HKCU\Software\Wine\DllRedirects" /v wined3d /f
I plan on updating all wrappers that are stuck on pre-3.0 builds soon, once POL start providing them (I don't use the Lutris builds by default as they don't provide checksums for their packages).
One more thing - if you haven't already then make sure that Mesa is up to date if you're using the open drivers (which is strongly recommended with AMD GPUs).
POL bundles some additional libraries with their Wine packages that may cause issues; I already remove libz* (and POL stopped bundling them with more recent releases) as those were a frequent source of problems for Arch users. You could try removing the rest of the bundled libraries and seeing if that helps - remove all the files from "Fallout 3/wine/lib/", leaving just the libwine.so.* libraries and the wine directory there.
If that doesn't work then my scripts have the ability to use alternative Wine builds for testing. I just checked with some newer builds and it looks like staging is still required, but Lutris' build will have to be used as POL have only recently started catching up with staging builds & don't have them all yet. Run the build script like this to have it use Wine Staging 3.8 from Lutris:
./fallout3_wine.sh -winever=staging-3.8 -winesource=lutris
If you do this you should run this command with the start script when it's done as redirecting wined3d.dll is no longer necessary for enabling CSMT (and it's not necessary to enable CSMT manually now either):
./start.sh runwine=reg : delete "HKCU\Software\Wine\DllRedirects" /v wined3d /f
I plan on updating all wrappers that are stuck on pre-3.0 builds soon, once POL start providing them (I don't use the Lutris builds by default as they don't provide checksums for their packages).
One more thing - if you haven't already then make sure that Mesa is up to date if you're using the open drivers (which is strongly recommended with AMD GPUs).
oleerik
New User
Registered: Nov 2012
From Norway
Posted June 04, 2018
Thank you, I'll test the wineversion and the libraries!
adamhm: One more thing - if you haven't already then make sure that Mesa is up to date if you're using the open drivers (which is strongly recommended with AMD GPUs). Mesa is very, very up-to-date :)
EDIT:
After following your instructions (except the libs as there were only libwine.so* there), I've had no crashes yet. Might be as stable as the lutris installer now, or better! Only time will tell :)
EDIT:
After following your instructions (except the libs as there were only libwine.so* there), I've had no crashes yet. Might be as stable as the lutris installer now, or better! Only time will tell :)
Post edited June 04, 2018 by oleerik
adamhm
GOG for Linux
Registered: May 2009
From United Kingdom
Posted June 05, 2018
Glad to hear it seems to be working now :) Some occasional random crashes can be expected as the game itself tends to crash every so often even on Windows, but it shouldn't be a frequent thing.
I guess you used the Lutris Wine build (they don't bundle any extra libraries).
I guess you used the Lutris Wine build (they don't bundle any extra libraries).
Post edited June 05, 2018 by adamhm
elderlypunk
New User
Registered: Jan 2011
From United States
Posted July 01, 2018
Thank you so much for this! As a newb I very much appreciate the "No wine knowledge" part. LOL. Anyways, the game seems to run great! But now to get greedy: is there any way to get my wireless xbox 360 controller to work with it? I've tried following several guides with no luck. Thank you!
Kind regards,
Mark
Kind regards,
Mark
adamhm
GOG for Linux
Registered: May 2009
From United Kingdom
Posted July 10, 2018
Kind regards,
Mark
Yootti
New User
Registered: Dec 2018
From Hungary
Posted December 30, 2018
Hello! I've read the readme txt and this post, but I dont understand NOTHING at all... like how to install it...
Like run the fallout3_wine.sh script... if I click it it just opens a bunch of code and where should I put the -respath"<path>" like which part of the code????? I just dont understand a single part of this stuff
Like run the fallout3_wine.sh script... if I click it it just opens a bunch of code and where should I put the -respath"<path>" like which part of the code????? I just dont understand a single part of this stuff
adamhm
GOG for Linux
Registered: May 2009
From United Kingdom
Posted December 30, 2018
Like run the fallout3_wine.sh script... if I click it it just opens a bunch of code and where should I put the -respath"<path>" like which part of the code????? I just dont understand a single part of this stuff
I'd recommend running it from the terminal anyway so you can see what the output is if there are any problems. If the wrapper and installer files are all in one directory then you can simply run the script like so:
./fallout3_wine.sh
If the installer files are in another directory then you'd run e.g.:
./fallout3_wine.sh -respath="<path to installer>"
See the attached image for an example. The wrapper files are in "/mnt/hdd/Temp" (where I've opened the terminal) and the installer files are in "/mnt/hdd2/Downloads/goginstallers/windows"
BStone
New User
Registered: May 2011
From United States
Posted October 27, 2019
Having the same "Permission Denied" errors again. :(
New Vegas magically started working on its own (before I had to reinstall Zorin due to a bad HDD problem), maybe FO3 will to.
New Vegas magically started working on its own (before I had to reinstall Zorin due to a bad HDD problem), maybe FO3 will to.
Post edited October 27, 2019 by BStone
-doofwarrior-
New User
Registered: Aug 2021
From United States
Posted September 29, 2023
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 data is stored under ~/.local/share/fallout3
Full details are in the readme.txt and release notes. Here is the download link:
fallout3_wine.tar.xz
(40 kB, SHA256: d088648e0b4b17ea044937b94fd5e9793c8c0be37ae55f02df6332a1aff8e707)
Last updated 2021/07/11
The wrapper uses Wine 6.0 + DXVK. 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.
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 check out post 3 in this thread: Adamhm's Linux Wine Wrappers - News, FAQ & Discussion
brouzuf
New User
Registered: Apr 2012
From France
