Read the Introduction page.

Short answer: No.

You cannot use an existing Fallout: New Vegas save to play Viva New Vegas. Even though a save might load, there are too many changes for it to work correctly. No support is provided if you do this anyway.

While this guide is written with the intent of merging with the main guide later, and as such only officially supports SteamOS 3, You should be able to follow this guide with any of the following Linux distributions:

• Bazzite
• ChimeraOS
• Playtron
• HoloISO
• Nobara Linux
• Arch Linux
• Manjaro
• CachyOS

Be aware that no support will be provided for users of these distributions, but if you're in the position to try other Linux distributions, you are likely competent enough to make up the difference in this guide's blind spots.

Piracy is not supported in any way, shape, or form. Any proof that you're using a pirated copy or piracy-related talk will lead to a ban from the ModdingLinked Discord server.

We will not provide any support for NVMP, redirect all questions to their server. Furthermore, I don't even know how well it'll run on a Steam Deck.

After completing the guide, your save files will be located in
~/.steam/steam/steamapps/compatdata/22380/pfx/drive_c/Modding/MO2/profiles/Viva New Vegas/saves
But you can access them quickly by opening Mod Organizer 2 and selecting the Saves tab in the right pane.

This could happen for various reasons:

• Make sure you have Steam Tinker Launch set as your compatibility tool.
• The 4GB Patcher wasn't run. Follow the steps in the guide.
• xNVSE is not installed correctly or at all, make sure that you have all of the utilities..
• You have incompatible mods lingering in your game's Data folder, this is why a clean slate is required.

Verify your game files.

You will need to re-run the BSA Decompressor and 4GB Patcher after doing this.

As MO2 is the only supported manager, instructions for other managers will not be provided:

1. Click the folders list in the top of MO2.
2. Click Open Profile Folder.
3. The modlist will be written in modlist.txt (written in reverse order but you can reverse this easily with text editors) and the load order is in loadorder.txt.

MO2 requires that you run most tools, including GECK, through its list of executables. This allows the programs to be run with VFS, loading all the mods alongside it.

Launch the game once, then restart the MO2 installer and try again.

Click the button at the top of MO2 and select INI Editor.

Clear the contents of both Fallout.ini and FalloutPrefs.ini, making sure to save both.

Run the game's launcher through MO2 and you'll have new INIs.

Verifying game files will revert the BSA decompression and the executable patch. You can solve this by re-running the correct patcher based on your game version, then re-running the BSA Decompressor.

This is just a case of mods logging that they are not meant for the GECK if made for the game, or the other way around. Can be safely ignored.

• 5:0000065434: Make sure Steam is running. If that doesn't fix it, run your game directly through Steam once. You may also need to restart Steam and/or Mod Organizer 2. If that still doesn't work, place a copy of your Steam.exe (not a shortcut) into the game's Root folder.
• P:0000065432: This might be related to the PCR release of the game. Override the Steamapp ID with MO2's executable settings and set it to 22490.

This is safe and intentional as long as your mods in the left pane of MO2 are in the exact order as they appear in the guide.

Disable Improved Lighting Shaders in your Mod Organizer 2 modlist by unchecking its box. This issue seems to be hardware related but we do not know the specific cause at the moment.

1. Click the button at the top of MO2 to open the settings.
2. Go to the Nexus tab, then click Associate with "Download with manager" links.

1. Move Vanilla UI Plus below the MCM and its hotfix (MCM BugFix 2) in the left pane of MO2.
2. Make sure that you have applied the guide's load order.

1. Click the button at the top of MO2 and select INI Editor.
2. Select the FalloutCustom.ini tab, which should already have all the guide's settings if you followed the Custom INI steps.
3. Edit the 3 FOV settings to your liking, then save.

No, but you can generate vastly more detailed LOD (at a performance cost) by following the LOD guide. If you are using a Viva New Vegas Extended list with no changes, you can skip a large chunk of the LOD regeneration process by using the VNV Pre-Generated LOD (the resources listed in the LOD guide are still required).

All the INI changes you'll need for stability and performance are already in the guide's Custom INI.
If you find some other settings you wish to tweak, add it to FalloutCustom.ini through MO2's INI Editor ( on the top of MO2).

Ultimate Edition ESM Fixes already does this (far more than what automated xEdit cleaning would do).

Yes, but you'll have to take extra steps for it to work:

1. Click the button at the top of MO2 and select INI Editor.
2. Select the FalloutPrefs.ini tab.
3. Change the following settings in the Display section:
   iSize W = your screen width
   iSize H = your screen height
4. Start the game then open the Tweaks menu in the settings.
5. Filter for Ultrawide then enable the support tweak.

Leveled DLC Delay delays DLC until you meet the required level or visit the respective location. Lone Star also moves the pre-order pack items to the following locations:

• Tribal Pack: Lucky Jim Mine House
• Caravan Pack: Hell's Motel
• Classic Pack: Wrecked Highwayman
• Mercenary Pack: Bradley's Shack