Intensely bright tree cause severe FPS drop!

[benburg]

I guess the title pretty much describe the problem. The tree is found just south of California Sunset Drive-in, pretty sure it's added with the Wasteland Flora Overhaul (dead version) mod. As you can see in the screenshot, it's glowing a little, and when I look in the direction of the tree, the game almost grinds to a halt.

It doesn't matter if I can see the tree or how far away I am, when it loads in, I can't look in that direction.

Tried removing the mod, the tree is gone but the surrounding vegetation is still glowing.

 

Any ideas? Could it be a NMC thing?

 

This is the load order LOOT made for me, there's probably something wrong with that too hah... Even though it never failed me in FO3.

 

 

benne^

[benburg]

Day and night, that's how they look.

 

 

 

benne^

[dubiousintent]

Hmm. Most likely this is due to texture files that overwrote some vanilla file, and some remnant of that being left behind. I would guess it's a "glow map" file, except it shouldn't appear during daylight. See "Glow Map" in the "Glossary" of the TESTG site.

 

If you only "deactivated" instead of uninstalled the mod, try uninstalling. Then toggle "ArchiveInvalidation" off-and-on again. (If you aren't sure how to do this, see the 'Mod Managers' section of the wiki "FNV General Mod Use Advice" article.)

 

OTOH, this is the first I have heard of a glow map causing an FPS hit. Curious to see if that really is the cause. Are you by any chance using a "post-processor" such as ENB or SweetFX?

 

-Dubious-

[benburg]

Well, I made a new character and went straight for that area, the glowing things are gone, but not for the other character. Seems like everything is in order now.

Never used ENB or anything like it, tried for Skyrim some years ago, wasn't my thing and my PC hard a hard time with it anyway.

 

Is my first playthrough of FONV, so I'm just happy it didn't happen 100 hours later than it did.

 

 

benne^

[dubiousintent]

Seems it got "burned into" the save game file. Which means something about those objects was "changed" during play, as the save files only carry forward "changes" like moved objects. All of which goes to point out how important it is to save often so you don't have to go back too far to find a point prior to a change. Also why it is recommended to not change your mods once you start playing in earnest, or at the very least know which save was before any change.

 

-Dubious-

Edited April 19, 2017 by dubiousintent

[benburg]

Yeah, it's odd. I ran the game before modding it, just to make sure it's running and made a test character for the mods, then I deleted that character and started the one I got the glowing tree problem with, didn't make any changes after that.

 

I have always done a 7 day cycle, as I call it, started back with Morrowind. Basically I can go back to the beginning of the previous 7 days I played the game, and I make those saves at the beginning of a session. Only lost a few hours of gameplay, so it's fine.

 

It wasn't just the Flora Overhaul tree, there were a few bushes around (I couldn't see them for the glow) that weren't a part of that mod. Wish I figured out what caused it, I really want to know now.

 

 

benne^

[dubiousintent]

Well, since you can save 1,000 files in FNV, I hold on to all the "full saves" beginning with "SAVE #### < PCname >") and periodically clear out all the others. That 1K file limit (and the save number) includes quick saves, auto-saves, and any others found in the "Users Saves" folder. I'm up to "SAVE 5720+" in 784 files at the moment, but I can go all the way back to "SAVE 2" before I left Doc Mitchell's for the first time after roughly 400 hours of play.

 

As for what caused the glow, don't obsess over it. There are just some things we are not meant to know due to changing circumstances.

 

-Dubious-

Edited April 20, 2017 by dubiousintent