Pink faces

[Doihavetoregisterwow]

Hello there Nexus users, this is my first time modding Fallout New Vegas after modding alot of Fallout 3, and this time I've had help from freind. I downloaded a range of mods including Character Overhaul and NV Redesigned 3. I just saw my first pink face which was a Powder Ganger. I want to fix this. I did the fix where you go into the Ini and change that one thing to =1. I also have the NMM Acrhive Invalidation checked. I will show you my load order now.

 

FalloutNV.esm

DeadMoney.esm

HonestHearts.esm

OldWorldBlues.esm

LonesomeRoad.esm

GunRunnersArsenel.esm

ClassicPack.esm

MercenaryPack.esm

TribalPack.esm

CaravanPack.esm

Interior Lighting Overhaul - Core.esm

Freeside Open.esm

New Vegas Redesigned 3.esm

FCOMaster.esm

Interior Lighting Overhaul - L38Ps.esm

Gomorrah Redesigned v2.esp

 

(WARNING: This plugin has the file extension .esp, but its fine header marks it as an esm!)

 

NVStripOpen.esm

Project Nevada - Core.esm

NVInteriors_Core.esm

IWS-Core.esm

Project Nevada - Equip,emt.esm

NevadaSkies.esm

Project Nevada - Extra Options.esm

Interior Lighting Overhaul - Ultimate Edition.esp

Project Nevada - All DLC.esp (UNCHECKED)

EVE FNV - ALL DLC.esp

Vurt's WFO.esp

New Vegas Redesigned 3.esp

FCO - NPC Changes.esp

FreesideOpenPatch.esp

CAGE 1.9.3.2.esp

Better Burned Man.esp

FCO - Glowingone.esp

FCO - OHSB NPC Edits.esp

ILO - Nevada Skies Patch.esp

FCO - Russell.esp (UNCHECKED)

Project Nevada - EVED All DLC.esp

StripOpenMain.esp

IWS-Core-Civilians.esp

IWS-DM.esp

IWS-HH.esp

IWS-LR.esp

IWS-OWB.esp

The Mod Configuration Menu.esp

NevadaSkies - TTW Edition.esp (UNCHECKED)

NevadaSkies - Ultimate DLC Edition.esp

NevadaSkies - Basic Edition.esp

 

 

 

 

[dubiousintent]

Most likely you're running out of graphics memory. See this entry in the TESTG "Troubleshooting" section.

 

-Dubious-

[Doihavetoregisterwow]

Most likely you're running out of graphics memory. See this entry in the TESTG "Troubleshooting" section.

 

-Dubious-

Thank you for the reply Dubious, I looked at that forum. Unless my game is locked for a certain amount of VRAM then it is not me. I currently have a GTX 1080 and if it helps I am on Windows 8.1.

[dubiousintent]

There is a known (and acknowledged) bug for some people with the PASCAL driver in the 1080 card. Please see this thread.

 

VRAM is dedicated memory on the video card. These days most video cards come with control software (nVidia Control Panel in your instance), which can tell you exactly how much the card has. When the game calls for more "graphics memory" than the card can provide, the system uses some of it's System RAM (which is usually slower) to fill the request. When that is not enough, it starts to use it's "page file" to swap code out of system memory. This usually manifests as "stuttering", but the interactions and requirements are complex. How much "graphics memory" is needed by the game is determined by several things like screen resolution, number of colors displayed, texture resolution, and graphic effects. My point is: VRAM alone is not sufficient to tell if you are going to run out of what the game needs. "Pink faces" is an indicator that for whatever reason, you are running out of what it needs graphically to display those particular textures.

 

How many plugins do you have installed in the game DATA folder? (Your number of active plugins in the LO is fine.) Active or not; more than 130-140 in that folder can also cause that "texture" problem.

 

Are you using a graphics post-processor like SweetFX or ENB?

 

Windows 8.1 means we are not dealing with the limitation added by Win10, so that is to the good.

 

All of that said: check out that bug in the thread linked at the beginning of this post, first. Changing anything in the game is useless if the problem is hardware related.

 

-Dubious-

[Doihavetoregisterwow]

There is a known (and acknowledged) bug for some people with the PASCAL driver in the 1080 card. Please see this thread.

 

VRAM is dedicated memory on the video card. These days most video cards come with control software (nVidia Control Panel in your instance), which can tell you exactly how much the card has. When the game calls for more "graphics memory" than the card can provide, the system uses some of it's System RAM (which is usually slower) to fill the request. When that is not enough, it starts to use it's "page file" to swap code out of system memory. This usually manifests as "stuttering", but the interactions and requirements are complex. How much "graphics memory" is needed by the game is determined by several things like screen resolution, number of colors displayed, texture resolution, and graphic effects. My point is: VRAM alone is not sufficient to tell if you are going to run out of what the game needs. "Pink faces" is an indicator that for whatever reason, you are running out of what it needs graphically to display those particular textures.

 

How many plugins do you have installed in the game DATA folder? (Your number of active plugins in the LO is fine.) Active or not; more than 130-140 in that folder can also cause that "texture" problem.

 

Are you using a graphics post-processor like SweetFX or ENB?

 

Windows 8.1 means we are not dealing with the limitation added by Win10, so that is to the good.

 

All of that said: check out that bug in the thread linked at the beginning of this post, first. Changing anything in the game is useless if the problem is hardware related.

 

-Dubious-

Thanks again for the reply Dubious, looking further into the thread you linked me and the questions you gave me to give to you, hear is my response.

 

I have just updated to the most recent GeForce Experience Driver version 372.70, and from what the Customer Support guy said on the forum post that problem will be fixed next driver update. But from what people are saying with that problem they are getting crashes when playing. So far I am not, so this could be non related (The pascal thingy might also cause other problems like mine though obviously).

 

I have 47 plug ins in NMM, three inactive

 

I am not using any types of ENBs.

 

Also nooby question, how do you get rid of extra plug ins that are just red and unchecked in your load order? Like the Russel one or TTW plug ins I want to get rid of.

 

-DoIHaveToRegisterWow

[dubiousintent]

Try rolling back the nVidia driver. Lately "the latest" from both nVidia and some Windows updates have been dropping support/creating problems for FNV players.

 

I presume you are referring to the recommended "bLoadFaceGenHeadEGTFiles=1" setting? That's good.

 

NMM, huh? Have you tried toggling "ArchiveInvalidation" off and then on again? Seems you need to do that every time you add a mod with textures/meshes in NMM.

 

The "red" plugins are missing their "master" files from what I've read. I'm not a NMM user, but what this article indicates is that "Uninstall them" from the current profile is what you want to do. That should not affect the "downloaded" files. Check the "Download Manager" after you uninstall a test file just to be sure.

 

-Dubious-

Edited September 8, 2016 by dubiousintent

[Doihavetoregisterwow]

Try rolling back the nVidia driver. Lately "the latest" from both nVidia and some Windows updates have been dropping support/creating problems for FNV players.

 

I presume you are referring to the recommended "bLoadFaceGenHeadEGTFiles=1" setting? That's good.

 

NMM, huh? Have you tried toggling "ArchiveInvalidation" off and then on again? Seems you need to do that every time you add a mod with textures/meshes in NMM.

 

The "red" plugins are missing their "master" files from what I've read. I'm not a NMM user, but what this article indicates is that "Uninstall them" from the current profile is what you want to do. That should not affect the "downloaded" files. Check the "Download Manager" after you uninstall a test file just to be sure.

 

-Dubious-

Hello there Dubious,

 

I can try out the Nvidia thing

 

bLoadFaceGen yes I did edit that

 

Archive Invalidation I have turned on and off and can try again once more

 

At this rate do you think it would be a smart Idea to completely reinstall both FCO and Fallout Redesigned 3?

 

-DoIHaveToRegisterNow

[dubiousintent]

RE: FCO and Fallout Redesigned 3. The former is supposed to affect PCs while the latter NPCs. (I haven't used either, so I can't tell how cleanly they keep that separation.) Uninstalling both, restoring any previous "loose" files they replaced, and then installing and testing one at a time is the only way to confirm they are not conflicting with each other, unless someone with experience with both cares to contribute a comment. However ....

 

Your LO seems to me to be heavy on "texture" enhancements: lighting, skies, interiors, etc.. Those have cumulative effects on the demands upon VRAM, which (as I've said before) eventually will result in problems like "pink faces" if you add too many. (Don't focus too much on the "faces" aspect. That is just a symptom of insufficient graphics memory.) At which point you have to decide which graphics factors are less important than others. It makes sense to prioritize your "replacers" and remove/reinstall/test them one at a time. Just don't try to use ALL your current replacers, as now you know you are pushing your limits.

 

Have you tried to see if reducing the in-game "texture quality" setting from "High" to "Low", or if reducing your screen resolution down to 800x600, or both, makes any difference to confirm the overloading of graphics memory is the cause?

 

The big problem with "replacers" is that they do just that: replace existing files. Just uninstalling is insufficient unless your mod manager can actually restore the files from earlier mods. (The vanilla files are all in BSA files and will be used if there are no matching "loose" files. But be sure to toggle "AchiveInvalidation" when done "restoring".)

 

Just a suggestion: Nevada Skies has been implicated in other mod conflicts in the past. You might try uninstalling it first, as a test.

 

-Dubious-

Edited September 9, 2016 by dubiousintent

[dubiousintent]

One more thing you can try, which I just added to the "Fallout NV Mod Conflict Troubleshooting" article.

 

Implement "ENBoost" (which is NOT the "ENB Series" graphics post-processor with it's attendant FPS hit) if you have more than 4GB of system RAM. See the S.T.E.P. ENB Guide and S.T.E.P. ENBoost QuickStart pages.

 

This increases the amount of system memory made available to the game graphics.

 

-Dubious-