Skip to content

STATUS

This mod is still in development and not available to the general public yet! If you want to become a tester, join our Discord

FAQ

Is this project like NV:MP?
This project is entirely independent from NV:MP. We have our own rules, moderators, functionalities etc...

Is the project open source?
No. the project is closed source due to security issues, as said in the terms and conditions.

Where do donation/subscription money go?
Donations and subscription directly fund the mod. all donations will be distributed to working developers (not moderators or testers).

How much time does the mod take?
The time for release/updates is vague, we do not constantly work on the mod 24/7, this is a pure passion project.

Troubleshooting

NV:O couldnt find NVSE

You can try to:
1. Make sure you have the correct fnv path by going in NVOPrefs.ini (usually located in your NVO install folder)
2. Install NVSE manually again
3. Re-Install the launcher
4. Do a clean install of FN:V

NV:O did not restore my old FNV files

There are a few ways you can fix this:
1. Check the "NVO" folder in your FNV root, remove the current folders in your FNV data folder and paste the folders in your NVO folder, then you may remove the NV:O folder completely.
2. Remove all files in the data folder and reinstall FN:V

As to prevent this, please make sure to NEVER END NVO'S COMMAND LINE BY FORCE VIA TASK MANAGER OR ANY OTHER PROGRAM THAT DOES SOMETHING SIMILAR UNLESS COMPLETELY NECESSARY

My old load order is not like before

If NV:O did not restore your old load order, you can simply either:
1. Regenerate the files with your mod organizer (if possible)
2. Check NVO's folder for "LoadOrdTemp.txt" and "PluginsTemp.txt" and replace your LoadOrder.txt and Plugins.txt files with these. If you don't know where these 2 are, check AppData\Local\FalloutNV

NV:O keeps asking for my FN:V root folder

Please make sure that:
1. Your NV:OPrefs.ini is in the same folder as NVOLauncher.exe
2. Your NVOPrefs.ini contents include the correct FNV path

NV:O keeps asking for my login

This is not a bug and is completely normal behavior. Login system may be updated in further side-updates.

NV:O crashes on startup

This is a very common problem cause it can be related to a multitude of cases.
1. Check if your game runs without NVSE
2. Check if your game runs with NVSE by starting the NVSE.exe manually.
3. Check if your NV:O is updated
4. Do a clean reinstall of FN:V
5. Post your nvse.log and ask a developer
6. Post your .dll log (should be NVOPh2.log or nvse_plugin_example.log) and ask a developer

If it still doesn't work, chances are it's a server problem.

How to do a clean install?
  1. Uninstall FN:V directly from steam
  2. Open your steam directory (default: C:\Program Files (x86)\Steam\steamapps\common) and find Fallout New Vegas
  3. Open the Fallout New Vegas folder and delete everything inside
session.txt not found

This file Is generated by your launcher and used by the plugin, then deleted automatically. If this file Is not found, all you have to do Is close FNV and close the launcher.

NV:O broke my FN:V

This Is a common bug caused by closing the launcher instead of the FN:V instance. Closing the launcher will stop it from doing the necessary operations needed to restore FN:V.
Never close the launcher: always quit the game or close the FN:V instance. The only fix is to do a clean re-install of the game.

Error HTTP 403

This error is caused by the launcher not being able to send information to the server.
Make sure your windows defender, antivirus apps or firewall aren't blocking NV:O.
If the solution above doesn't work this is likely a launcher build problem and you should wait for a fix.

Missing masters
  1. Check for the .esm files in your FNV data folder
  2. Check your NVOPrefs.ini contents for "FNVRoot" and check if the directory is correct
  3. Launch FNV atleast once, get to the main menu then leave.
  4. Open FalloutNVLauncher.exe and select "Data Files". Check the checkboxes of each master file.
  5. Check your loadorder.txt and plugins.txt and make sure they're correct.