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: New Vegas, 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/falloutnv

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

falloutnv_wine.tar.xz
(12.3 kB, SHA256: 9fe6dbfaa812bd0d6ab99f06c1c890f54dd009a840aa63a141f617fc09732e9d)

Updated 2017/09/12: Update for all wrappers' start scripts to create additional user directories inside the prefix that may be needed if installing things such as third party tools/utilities, or certain redistributables. Some wrappers also have other small misc improvements.

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 with this 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 New Vegas Script Extender (NVSE)

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

- Install NVSE 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 New Vegas)
- You can then launch it by running the start script with the argument: runwine=nvse_loader.exe
- You can create a shortcut to use NVSE 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=nvse_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, 3 and Tactics) see my GOGmix: adamhm's Linux Wine wrappers. Also check out Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion
Post edited September 12, 2017 by adamhm

sh falloutnv_wine.sh
falloutnv_wine.sh: 3: [: unexpected operator
falloutnv_wine.sh: 5: [: unexpected operator
falloutnv_wine.sh: 15: [: -v: unexpected operator
falloutnv_wine.sh: 15: [: unexpected operator
Using Wine version:
Checking for innoextract...
falloutnv_wine.sh: 27: falloutnv_wine.sh: innoextract: not found
System installed innoextract not found.
falloutnv_wine.sh: 38: [: unexpected operator
Checking for icoutils...
falloutnv_wine.sh: 66: [: unexpected operator
Checking for installer and resource files...
falloutnv_wine.sh: 93: [: unexpected operator
All files found. Testing SHA256 hashes...
setup_fallout_new_vegas_1.4.0.525_(12010)-1.bin: OK
setup_fallout_new_vegas_1.4.0.525_(12010)-2.bin: OK
setup_fallout_new_vegas_1.4.0.525_(12010).exe: OK
falloutnv_res.tar.xz: OK
falloutnv_wine.sh: 119: [: unexpected operator
Wine package not found, attempting to download...
--2017-06-01 22:34:03-- http://wine.playonlinux.com/binaries/linux-x86/PlayOnLinux-wine--linux-x86.pol
Resolving wine.playonlinux.com (wine.playonlinux.com)... 51.254.83.230, 2001:41d0:2:37ca::1e
Connecting to wine.playonlinux.com (wine.playonlinux.com)|51.254.83.230|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-06-01 22:34:03 ERROR 404: Not Found.

ERROR: Failed to download PlayOnLinux-wine--linux-x86.pol
rm: cannot remove 'PlayOnLinux-wine--linux-x86.pol': No such file or directory
(running current MINT with Mate)
Post edited June 01, 2017 by Klumpen0815
Tried "bash falloutnv_wine.sh" or just "./falloutnv_wine.sh" ?
avatar
adamhm: Tried "bash falloutnv_wine.sh" or just "./falloutnv_wine.sh" ?
That was it!
I didn't even know about the bash command before, would be great if you could mention it somewhere, I always used the sh command.

It runs like a charm, thank you very much, you made me not have wasted 10€ AND gave me the chance to finally play New Vegas for the first time ever after having finished Fallout 1+2 so bloody often and the third once on XP.
I've also seen that you made such a script for Witcher 1, which is another one I never could play.

Do you plan on doing such for Crysis, Crysis Warhead and Gothic 3 too at some point?

Is it also possible to donate somewhere for your work?
You did more for me than GOG did.
Post edited June 02, 2017 by Klumpen0815
avatar
Klumpen0815: Do you plan on doing such for Crysis, Crysis Warhead and Gothic 3 too at some point?
Yes, but I don't know when. Crysis is actually more or less done already, but there are some small issues to resolve first. Crysis Warhead is very unstable in Wine atm though, or at least the 64-bit version is (and GOG doesn't currently provide the 32-bit version).
Post edited June 02, 2017 by adamhm
avatar
adamhm: snip
Hi, I'd like to compress the resulting folder to put it on my backup drive but get this error message.

An error occurred while adding files to the archive.

Error opening directory '/home/klumpen/installer/fallout_-_new_vegas_ultimate_edition/windows/Fallout New Vegas/prefix/dosdevices/z:/root': Permission denied
When trying it with admin rights I get another message:

An error occurred while adding files to the archive.

Error opening directory '/home/klumpen/installer/fallout_-_new_vegas_ultimate_edition/windows/Fallout New Vegas/prefix/dosdevices/z:/dev/fd/7': No such file or directory
What can I do?
Post edited June 02, 2017 by Klumpen0815
Thanks for your hard work. Much appreciated.
avatar
Klumpen0815: What can I do?
Whichever method you're using to create the archive is trying to follow through all of the symlinks in the Wine prefix and add the contents of those to the archive as well.

As mentioned in the readme, the build script has the ability to create .tar.gz or .tar.xz archives respectively after building, simply run it with the arguments:

./falloutnv_wine.sh -gz
or
./falloutnv_wine.sh -xz

You can also do it yourself with the command: tar -cf "Fallout New Vegas-Linux.tar.xz" "Fallout New Vegas" --xz
(replace xz with gz if you want a .tar.gz archive instead- it'll be much faster to compress but won't compress as well. Either way be prepared to wait quite a while for it to finish though)
Post edited June 02, 2017 by adamhm
Thanks adamhm. I have saved the wrapper for when I get the FNV.
avatar
Klumpen0815: What can I do?
avatar
adamhm: Whichever method you're using to create the archive is trying to follow through all of the symlinks in the Wine prefix and add the contents of those to the archive as well.

As mentioned in the readme, the build script has the ability to create .tar.gz or .tar.xz archives respectively after building, simply run it with the arguments:

./falloutnv_wine.sh -gz
or
./falloutnv_wine.sh -xz

You can also do it yourself with the command: tar -cf "Fallout New Vegas-Linux.tar.xz" "Fallout New Vegas" --xz
(replace xz with gz if you want a .tar.gz archive instead- it'll be much faster to compress but won't compress as well. Either way be prepared to wait quite a while for it to finish though)
Oops, I should have read more carefully, thanks again!

This is great, I'll make Linux packages for my backups with all your scripts as soon as I find the time.
I'd just have liked to make a normal archive cut into multiple files with max 4GiB each, but I guess this will do.
Post edited June 02, 2017 by Klumpen0815
I've been trying to get an optimal setup for NV for a while now but couldn't seem to get it right. This worked absolutly perfect, Thanks!

Edit: I've been playing around with this a bit more and got the FOMM working perfect. Went through winetricks and installed dotnet2 and duplicated the start.sh to open the modmanager exe.

And the setup you did with zenity, winetricks launching, and everything else, it's great.
Post edited June 04, 2017 by coryrj1995
avatar
coryrj1995: Edit: I've been playing around with this a bit more and got the FOMM working perfect. Went through winetricks and installed dotnet2 and duplicated the start.sh to open the modmanager exe.
I updated the wrapper to install Wine Mono so installing .NET might not be necessary with the latest version.

BTW I designed the start script to easily allow running other commands by passing them to it via command line arguments (and custom shortcuts can be created to run them automatically), so it shouldn't be necessary to create a modified version. The details about this are in the release notes :)
Hi, Thank you for all the hard work making my all-time favorite game playable on Linux!

On that note, I know that Wine has had some success with New Vegas on Steam, but the biggest bug left in vanilla was never fixed, primarily because of Steam, that being the application (or lack thereof) of the LAA (large address aware) flag. On Windows, this was fixed with the FNV4GB launcher, which bypassed the need for the manual application of the flag, but unfortunately, this hasn't worked in Wine. I bought the game again partially to support all of you guys' hard work, but also to test whether applying the flag now works.

Has anyone else had a chance to test this?
avatar
theluigus: snippity poops
I have checked the FalloutNV.exe that comes with the GOG release and can see that it already set to be large address aware - however I discovered that AFTER I typed the below post, so I'm going to leave it here in case you want to check yourself:

FNV4GB.exe doesn't work in Wine, however you can use CFF Explorer in Wine to set the LAA flag manually, and permanently, in the executable. This has in my experience worked perfectly and made things like NMC's texture pack work fine.

So here's some instructions because I'm nice:
Download the thing, click above link and scroll down - or have a direct link.

Install it. Doesn't have to be in your FNV Wineprefix but it also wouldn't do any harm to put it there - just double click or run the installer with 'wine' like you would normally.

Go to the installation folder (something/drive_c/Program Files/NTCore/Explorer Suite) and run CFF Explorer.exe.

Find FalloutNV.exe, on the side panel click FILE HEADER. The bottom row in the main view is called "Characteristics" and there's a blue box with 'Click here' on it. Click it, a new window will open, tick "App can handle >2gb address space". Save the exe - DON'T OVERWRITE THE ORIGINAL BACK IT UP SOMEWHERE.

So there you go.
Dude, thank you for getting back to me so fast! It is so good to hear that the executable is already patched! I'll use the instructions you gave, because I'm excited to learn how, but I also trust your findings. I had been under the (perhaps mistaken) impression that if Steam was installed first and then used to install the game into the same wine prefix, the executable would be re-downloaded by steam whenever it detected the patching. I had been searching for a solution on various forums, but eventually decided to wait for a new development (aka GOG release), and play without using RAM intensive mods.

So again, thanks!