This NVSE behavior is inexplicable and I cannot explain it

[Asterra]

I recently migrated from Win7 to Win10. There was much pain involved, but I eventually got everything working the way it was in Win7, more or less.

 

So I thought.

 

I have one remaining issue that needs to be tackled. I can only describe the chain of events and hope that someone has an idea what's going on.

 

Scenario: A clean save at Doc Mitchell's house. No mods loaded on the save. I load the save with Mod X. Mod X takes advantage of NVSE. Mod X works flawlessly. I now make save #2. I exit the game. I start the game and load save #2 with Mod X also loaded. Mod X now malfunctions in this very specific way: Any script which takes advantage of Array searches (Ar_Find) returns null, every time. This sometimes generates errors, sometimes doesn't; it depends on what the mod was trying to do with the data.

 

Scenario 2: A save which has used Mod X extensively. I load the save with Mod X. Mod X malfunctions as above.

 

In a nutshell: Mods which use Ar_Find work fine ONLY the first time they are used; game saves already associated with such mods result in those mods being broken in this very specific fashion. This is what I came back to. Half a dozen very different and very specific mods being broken because arrays are suddenly SELECTIVELY working correctly.

 

If I had to give a second interpretation, what seems to be happening is the arrays themselves are being rendered empty upon loading the save; only if the mod specifically fills them do they have anything in them, and that generally only happens the very first time the mod is loaded. Hence the behavior of things working and then not working.

 

Now, I have had my fill of Windows 10's shenanigans. I have given full permissions to everything I possibly can. I have given every executable in sight admin privileges. This does not seem to be the solution in this case, though.

 

I have double-checked to make sure NVSE and JIP are the very latest. My mod count is sub-120, so no weird behavior should be occurring due to excessive modding. Basically I am out of ideas. The only reason I upgraded was so I could finally get 60fps out of this game. Frustration is high.

Edited October 29, 2018 by Asterra

[Asterra]

I've decided to bypass the problem by personally enforcing array filling for all the mods this weird problem affects. Who really has time to troubleshoot these days? Just work around the problem and move on.

[dubiousintent]

There is definitely a wrench moving from Win7 to Win10. But your problem is NOT that common. At least, no one else in the last 4 years has pinned it down so specifically, and one would expect to see a lot of complaints about mods if arrays were that broken. Here are known issues with Win10.

 

* Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. System updates often cause issues with games installed to these folder trees. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

The following entries in the wiki 'Fallout NV Mod Conflict Troubleshooting' guide specifically address known Win10 problems:
* 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)'
* 'Issue: Incomplete save game load' (NVSR related)
* 'Issue: Vanilla game Hangs on startup'; specifically "Cause-1" regarding DirectX9 drivers.
* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'
* 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play'
* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed (or not)'. In particular "Cause-4" regarding video card settings. The latest video drivers may not be the best suited to an older game like FNV. All vendors drop testing of old games at some point. Backwards compatibility is never guaranteed, much less "optimization".
Also, "Cause-7" regarding "Superfetch" and "File search indexing". Windows updates will often reset these back on.
* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'
* 'Issue: ENB Support for Windows versions later than Win7'
* 'Issue: Problems using ENB/SweetFx on Windows 10'

-Dubious-