I tried running the installer for it in wine, but it didn’t work. I had to set it up in windows and copy it. It re-encodes all the audio from fallout 3, so it takes a long time. I followed the instructions on the new Vegas multiplayer blog, and that version lets you get away without using mod organizer. It does use LOOT, but you only have to run it once, and that part does work in wine.

https://wiki.nv-mp.com/en/server-hosting/mods/tale-of-two-wastelands

I was able to get nvmp working as well, and my wife and I started paying fallout 3 together. Her on windows and me in my Steam deck.

Quoting: sobinsirilWhat is the best way to setup TTW mod for Fallout on Linux?

The guides either involve a separate Windows instance to install then copy the files from, or as in some YouTube tutorials using PlayOnLinux. Both options seemed a bit finicky for me. Also the installation of Mod Manager was suboptimal.

So have anyone had any luck with TTW? If so please share your experience.

I don't know what you consider optimal, but from my experince you are best off doing the installation in a VM and copying out the result to launch it with your favourite way of running wine. I opened a thread on a similar topic before: see here.

Well I guess that I have no choice but to do it in a virtual machine. Will try it out and share my experiences on how it went. Thanks for your input.

I just did an install using the guide on "The Best of Times" and what worked for me was to install the GOG versions through Heroic into their own subfolders in an overarching TTW folder.

Next, and this is the step that hung me up for the longest time, I launched both games, and ran through the introduction until I could make a hard save. For me this was a necessary requirement for the TTW version of MO2 to recognize the game.

Next, I installed the TTW version of MO2 into its own sub folder in the main TTW folder, and finally copied the TTW Installer into the root of that folder. Note that MO2 ran fine under WINE, though I did have to adjust properties to enable running it as a program.

After that, I set up a Windows 10 VM with my TTW folder set up as a shared folder so I could access it through the VM. That done, I just ran the installer, let it do its thing, and there it was. That done, I exited the VM.

All of this was done on Pop_OS! and I also have a modded Steam install of FNV on the same machine with its own portable MO2 instance.

I also did a couple of QOL tweaks, but these only work if you have another FNV MO2 instance, so your mileage may vary. From one of my failed installs, I already had a folder with a number of the essential mods from the guide already installed, so I just copied those to my Mods folder in the TTW MO2. Note that this doesn't work for mods you install into the root of the game--those have to be installed separately.

However the big one was using the same download folder for both the FNV and TTW instances of MO2. It saves a lot of time and bandwidth for compatible mods, especially if you have a free Nexus account. The one quirk here was that even though I linked both MO2 instances with Nexus, any time I try a Mod Manager download, it fires up the Steam version and downloads to that instance (one reason I use the shared download folder).

I hope this helps.