That's great news. Thank you for the work.

When we talk about RPGs - what do you think about doing Vampire The Masquerade Redemption and Vampire The Masquerade Bloodlines? There is a sale now and if you do not own the games I'm sure I won't be the only one happy to gift you a copy:)

Thanks for your work adamhm, I really appreciate it as New Vegas is one of my favorite games. I recently switched over to Linux, and I was wondering how one goes about in installing mods for New Vegas on Linux. I'm a newbie to linux, so I don't know too much about the OS itself (running Mint 18 atm), and even less of Wine. I ran your script and got the game installed and running, but I'm at a lost when it comes to mods that require archive invalidation and mod ordering (I used the Nexus Mod Manager along with BOSS when I was using Win7, so I'm a bit spoiled......). Any tips or guides for modding New Vegas on Linux? (Very inexperienced with Wine btw)

I have tested both of them in Wine before & plan to do a wrapper for VTM:B at some point :) I'm prioritising other games atm though as there is a small rendering glitch with VTM:B that I'm hoping will be resolved before I get around to it.
You might find my Linux Mint & PlayOnLinux guides helpful: https://www.gog.com/forum/general/the_try_linux_repostrewrite :)

You could try installing NMM etc. into FONV's Wine prefix and see if they work (they might need some additional tweaking to run though). I haven't tested anything like that myself yet though (I'm going to play through FO3 first as it'll be much harder to do FO3 after FONV). If you run the start script and access the advanced options menu, you can use the "Run..." option to try running the installer for things like NMM.

To run them after installation you'll need to run the start script with the argument: runwine="<command>"

You can use Windows pathnames for this, but double up the backslashes if you do, e.g.: runwine="C:\\Fallout New Vegas\\nvse_loader.exe"
If any arguments are required, specify them with args="<args>" after the runwine argument.

If that doesn't work things like Archive Invalidation can be done manually; you should be able to find them on Nexus Mods etc.

With the latest update this should now perform a bit better on systems using the open graphics drivers :)

Can you provide some advice on getting FOMM running? Or otherwise setting up ArchiveInvalidated?

I've tried everything, and can't get the archive invalidated to work consistently. I've edited my ini files, added the bsa, made sure I only have one "textures" and "meshes" folder, etc. I still get texture corruption.

Which mods are you trying to use? I'll take a look

We can start with Nevada Skies. At one point I had everything running, no texture errors.

Then an errant mod addition screwed everything up and I decided to start from scratch with a smaller mod list. This time around, I can't get the ArchiveInvalidated to take, and I get static moon textures across my night skies.

My fallout.ini Archive section:

[Archive]
SInvalidationFile=
iRetainFilenameOffsetTable=1
iRetainFilenameStringTable=1
iRetainDirectoryStringTable=1
bCheckRuntimeCollisions=0
bInvalidateOlderFiles=1
bUseArchives=1
SArchiveList=ArchiveInvalidationInvalidated!.bsa, Fallout - Voices1.bsa, Fallout - Sound.bsa, Fallout - Misc.bsa, Fallout - Textures.bsa, Fallout - Textures2.bsa, Fallout - Meshes.bsa

I have the relevant BSA in the data folder.

This happens with NMC's textures, too. The ground (dirt) texture shows up as a purple.

Ok, I've looked into it and it looks like a native Windows library is needed for them to work. Run the start script and select the "Advanced options..." item in the menu, then select "Winetricks". Enter "d3dx9_38" in the box (or just "d3dx9" to install all of the d3dx9_##.dll libraries, which may prevent similar issues in future although doing this also risks causing other issues) then click ok, and then try playing again. This seemed to fix it for me, at least with Nevada Skies (I didn't test the other).

Just wanted to say thanks, Adam, for providing the best (non-native) gaming experience I've ever had with an AAA title. I'm a programmer on Linux so I know how much bash scripting sucks. Your scripts look bonkers but they worked flawlessly.

About 50 hours playtime with the usual bethesda-amount of bugs and crashes.

Thank you for this! I've always had 50/50 luck with Wine, but this worked off the bat.

Now to my question: Is there a mod loader that works with this? FOMM, while detecting my installed esm's and the nots and letting me enable them, nothing happens in game. NMM fails to launch no matter what I do, just crashes continuously. And theres another I can't think of, but that in itself would fail just on the premises of how it works, which is a virtual data file.

Thanks again, even without mods this is playable without crash for hours on end.

I haven't had much success getting them working fully so manually enabling & setting load order is required for now, but I'm planning to update all of the wrappers to Wine 3.0/3.0-staging when that's ready - I'll have another look into this once that's done & hopefully they will work better with the newer Wine version :)

What's the recommended way to update my installation to take advantage of the performance improvements? Backup saves/mods/etc and fresh install? I used this script back when it was released.

Yes, that would be the easiest way to do it. You can rename the original wrapper's directory (or move it out of the way somewhere) and then use the updated script to create the new version & copy your mods etc. across from there.

I'm running dual monitors and the terminal output says that my resolution is 3840x1080 ?
Also when running the start.sh inside the fallout new vegas folder I get a light blue screen and it then closes.

Current display resolution: 3840x1080
Gamma (R/G/B) = 1.000 / 1.000 / 1.000
Userdata directory: /home/lukaboot/.local/share/falloutnv
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Running: FalloutNVLauncher.exe
Using virtual desktop with resolution: 3840x1080
wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
Wine cannot find the ncurses library (libncurses.so.5).
wine: Unhandled page fault on read access to 0x00000004 at address 0x7ea75b41 (thread 0026), starting debugger...
winedbg: Internal crash at 0x7e8ceb41
-> Red 1.000, Green 1.000, Blue 1.000
<- Red 1.000, Green 1.000, Blue 1.000

It looks like you're missing some of Wine's dependencies, which is why it's crashing.

As for the desktop issue, it's detecting your full desktop resolution (the combined resolution of both monitors is reported by the system). You can make the game run in a smaller virtual desktop instead by running the start script with desktop=<res> or by setting it via the desktop file in the support directory. I don't have much experience with multi-monitor setups & don't have access to one I can test with though.