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.

In a word, yes. That said, if the warning on the front page was not enough, This guide is only meant for devices running SteamOS 3.7.8 and higher. Other users have reported successful installations with the following distributions:

• Fedora
• Linux Mint
• Bazzite
• Ubuntu
• CachyOS

There will be absolutely no help or support provided in these cases. You are on your own. Due to the nature of SteamOS, and this guide's careful decision to use commonly-available Linux applications, With enough trial and error Viva New Vegas could theoretically be successfully installed on Any Linux distribution that can run Steam, but the difference between theory and practice is larger in practice than in theory. tl;dr. Yes, but caveat emptor, we won't help you if you do.

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 it probably runs like garbage on PC handhelds anyway.

After completing the guide, you can access them quickly by opening Mod Organizer 2 and selecting the Saves tab in the right pane.

There are a great many helper tools designed to facilitate game modding on Linux, and I am acutely aware of them. For some honourable mentions

• SteamTinkerLaunch - an all-purpose shell script for Linux gaming
• Limo - a native Bethesda mod manager for Linux
• NaK - an interactive helper script for ModdingLinked guides made with AI

While these tools are great in their own right, We chose not to use them because they are all varying degrees more complicated to use, and this guide exists to show the ModdingLinked staff that supporting Linux users is simple, and will not add too much overhead to their day-to-day. Some of these tools do geniunely have an advantage of the MO2 installer we recommend, but it requires more time and effort on your part to understand how they work and what you're doing.

This could happen for various reasons:

• You have set your launch options incorrectly.
• The 4GB Patcher wasn't run. Follow the steps in the guide.
• You may need to manually install vcrun2022 with Protontricks. You may do so by invoking the following command in the Terminal
  protontricks --no-bwrap 22380 -q vcrun2022
• 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.

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

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.

• 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.

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.