Skip to content

Instantly share code, notes, and snippets.

@kabyidon
Last active January 6, 2024 12:34
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kabyidon/076e3d489ff4e788f9b59f4e2cdb363c to your computer and use it in GitHub Desktop.
Save kabyidon/076e3d489ff4e788f9b59f4e2cdb363c to your computer and use it in GitHub Desktop.

NVR3R: New Vegas Redesigned 3 Revised FAQ

READ THIS

The mod is in a stable state and has accomplished its mission. I will not be releasing patches or fixing bugs that arise from conflicts. In other words, if I can’t reproduce your bug, I won’t fix it. You are responsible for your own game.

YUP and many other mods get updated, so conflicts are to be expected. You may need to make your own patch.

If you want something to be done, do it! GECK, FNVEdit, and all other tools you need are free. Contributions are always welcome. If you’ve made other patches, post them on Nexus. If you send a link to me, I will add a link in the mod description.

Steps For Fixing Issues

Do this before you report an issue.

  1. Read or search the FAQ (Ctrl+F is your friend). Chances are, someone has asked your question before.
  2. Make sure you have essential stability and bugfix mods installed. For information on what mods are essential for stability, read up to the end of the Tweaks section on this website.
  3. Use MO2 and FNVEdit to determine and fix mod conflicts. Confirm which mods are conflicting with NVR3R or confirm that nothing is conflicting. It is extremely easy to do this using FNVEdit. If any mods are conflicting with NVR3R, you have to fix those conflicts. Refer to "How to Fix Conflicts".
  4. Isolate the problem. Disable all your mods except essential ones. Chances are, the problem is on your end.
  5. Take screenshots or videos of your problem. If something is wrong with an NPC, find its Editor ID (you can do this in the console).
  6. If you’ve confirmed that there are no conflicts and your game is stable, make a bug report in the BUGS section. Include all the information you gained from the above steps in your post, along with a pastebin of your modlist and plugin list. This is obtainable using MO2.

How to Fix Conflicts

The included patches in NVR3R (and most patches in general) are band-aid solutions. They are easy to use and install, and probably will have better results than no patch, but can never be perfectly right for your setup because they are made by someone else. To do it right, you need to get your hands dirty.

  1. Read this to understand how to use xEdit and what conflicts are.
  2. Follow "The Method". At the end you will have a fully patched load order and every conflict that doesn't need intervention will be hidden, leaving room for additions and ease of patching.

FAQ

First of all, thanks everyone for the friendly comments/endorsements. I won't reply to every one to avoid spam but much appreciated.

Is this compatible with TTW / Why no TTW patch?

Probably.

For TTW players: Try installing FCO 2.3.1, then this mod. Overwrite all with NVR3R. Confirmed working by Parkemet500, but needs further testing.

According to Qwinn these problems are apparently due to FCO having a problem with child races.

Is this compatible with mod X? Why doesn’t this work with X? Where is the patch for X?

I recommend loading all plugins that change cells and NPCs under New Vegas Redesigned 3.esm.

If you want to eyeball "guess" whether you need to make a patch or not for mod X, consider the following.

  1. First, check if there is a patch that applies to your situation. If so, probably not.
  2. Otherwise, in general: Yes, if X modifies NPC records. No, if X doesn't.
  3. If you really want to know, use MO2 to determine if there is a conflict, and xEdit to determine what conflict it is causing.

NVR3R's scope limits 99% of what it does to changing face textures and meshes. So that's the scope of any problem that mod conflicts should cause, as long as you load them below NVR3.

Some NPCs look vanilla, or not how I expect them to.

While extensive, NVR3R doesn't change every NPC. If you're sure it does and you're not seeing the cfhanges, refer to the above section, "How to Fix Conflicts".

I don’t like how an NPC looks and they look better in another mod / a past version of NVR (e.g. 3.6) / without nudity. How do I change this?

Make a patch in FNVEdit and regenerate face textures. For nudity, you can try Undies Underneath but I doubt that will fix the entire issue. You can make suggestions if you don’t want to make a patch yourself, but they will almost surely be ignored. You have been forewarned.

Should I set bLoadFaceGenHeadEGTFiles=1?

Short answer: Yes, set it to 0. Make sure falloutcustom.ini, fallout.ini, and falloutprefs.ini have it set to 0.

Long answer (modified from Qwinn's original answer): If you changed your bLoadFaceGenHeadEGTFiles settings in any of your three INI files (fallout.ini, falloutprefs.ini, and falloutcustom.ini) to 1 to get NVR3 to work for you, you should set them back to 0. Obviously if you're using another mod that requires that setting be set to 1, you may not be able to do this, but at least this mod will no longer place that demand on the engine.

What does the empty .esp file do?

Short answer: Nothing. Feel free to disable it. It is now not installed by default.

Long answer (from Qwinn): QRNVR3 contains an empty "New Vegas Redesigned 3.esp" plugin. QRNVR3 makes NVR3 no longer require an ESP - all necessary records are in the 3 main plugins now. This empty ESP exists to prevent problems by overriding the original in case people accidentally try to enable the original. This ESP also serves a secondary purpose in that there are many patches for NVR3 out there that require "New Vegas Redesigned 3.esp" as a master.

Should I keep FCOMaster.esm enabled?

(from Qwinn) Yes, if you want to use the custom player races from FCO or already had it enabled in your ongoing game. No otherwise.

I see the “white face / whiteface” bug; body and face colors don’t match! How do I fix this?

Possibility one: If the head and body look very different in brightness, you almost certainly have another mod modifying face and body textures. This especially applies to mods like Dragbody’s overhauls.

There’s no perfect way to fix this. You can try setting bLoadFaceGenHeadEGTFiles=1, which sacrifices performance. If you're willing to put in some effort, you can read this post for an alternate solution.

Possibility two: Note that not every difference in skin tone between the head and chest is the whiteface bug. The below screenshot was taken with bLoadFaceGenHeadEGTFiles=1. In other words, we can't fix this:

A lot of these NPCs will have weird lighting issues in the engine that cause the head and body textures to look very different in brightness especially indoors, just an issue with neckseams and lighting calculations. No mod can fix this, although T4 + T4-NVR3 can make it much more bearable for female NPCs. Unfortunately, there isn't much you can do for many male NPCs in NVR3 as no one has made a Improved Vanilla Male Body (or any other seamless male mesh) patch for NVR3/FCO meshes.

There is a simple way to test whether you're really getting the white face bug.

If you set bLoadFaceGenHeadEGTFiles=1 and it still occurs, then you're just experiencing the lighting of the Gamebyro engine.

I see meshes clipping (e.g. lip, mustache, eyebrow)!

Inherent problem with the FCO dependency. Use another mod.

I see pink faces!

(from Qwinn) You have installed FCO version 3.0+ instead of FCO 2.3.1. Per the NVR3 installation instructions, 2.3.1 is the correct version to use.

I see glitchy textures!

Use a modern mod organizer like Mod Organizer 2 with Archive Invalidation. Don’t use ENBs. Make sure you have essential stability and bugfix mods installed (see the Steps above)

My game crashes or is laggy (e.g. McCarran Concourse, Ultra-Luxe Bathhouse)! And I know it’s NVR3R because when I disable NVR3R it works!

I will not fix performance/crash bugs because they are not problems with NVR3R. This is especially true after the 1.5.0 update. You have a conflict, or your game is not stable. In other words, mod your game correctly.

This mod will affect performance, but it should run smoothly on a modern PC with reasonable specs. Every location reported as causing stability issues has been tested extensively with no problems.

Patches

All described in the FOMOD. Load JSUE's patch under YUP if you want JSUE's changes.

Updated patches. These are the only ones supported!

These should also work largely for version numbers > the ones listed.

  • Patch for YUP 12.6
  • Patch for JSUE 5.3.8
  • Patch for Uncut Wasteland from VNV Resources
  • Patch for Mojave Raiders v1.1.0

Qwinn’s legacy patches - some may be outdated

  • Patch for A World Of Pain v6.01
  • Patch for Adam Trooper Gloves Patch v4.5.1
  • Patch for Arizona Slave Army - A Legion Overhaul v1
  • Patch for Armor Replacer Child NPC Fix v1.0
  • Patch for Caesar's New Regime Legion Overhaul v1.2
  • Patch for ELECTRO-CITY - Relighting the Wasteland v12A
  • Patch for Equipment Restoration Project v3.0.0
  • Patch for Improved Companion Sandbox v3.2
  • Patch for Legion AI-Combat Bark Fix v3
  • Patch for Legion Quests Expanded v1.21
  • Patch for New Vegas Uncut - Outside Bets v1.4
  • Patch for NPC Trooper Overhaul - Distributed v1.0
  • Patch for Project Nevada - Equipment v2.5
  • Patch for Spice of Life - Variety Armor and Clothing Robert Breeze Type3 v1.2
  • Patch for Unofficial Patch Plus v2.04
  • Patch for Vendor Containers Respawn Fix - Elaborate Edition v1.4
  • Patch for Vendor Containers Respawn Fix - Simple Edition v1.1
  • Patch for Weapons of the Wasteland v0.9b

Other

Installing BNW

There is an image on the NexusMods page that shows a “correct” installation of every updated mod as well as Type4 and BNW. There is no one-size-fits-all installation: use it as a reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment