Weird bug with Someguy Series.

[wfandrews]

I finally got my games to work with no problem with Win 10, a matter of reinstalling the OS as it was corrupt. They no longer burn in the computers before shipping them, a fact I was unaware of.

 

I had oldrim and SSE running with no problems so I decided to install and play FNV as it is a game I enjoy very much.

 

I did my usual installation on any new start by playing the intro with just the game stability mods, NVAC, NVSR, YUP, etc. loaded, then saving and starting to install my mods four or five at a time, loading the save, exiting, doing it again, and so on. Time consuming but much less so than installing all the mods you are going to play with and then discovering there is a conflict.

 

I had about twenty or thirty mods loaded and got to my Someguy Series mods, I already had Someguy Series installed. I installed NVBI, NVBII,The Inheritance, and Russell and two other mods, then ran around Doc Mitchell's house until everything loaded that was going to load and then exited out. When I exited out the game froze, so I uninstalled all those mods I had just installed and started to install them one at a time and playing.

 

Turns out the culprits were NVBII and The Inheritance. So I uninstalled all the Someguy Series mods and have been playing the game for about five hours now with fifty or so mods with no problem.

 

I really have no idea why this bug happened. I have played with these same mods with no problems before.

 

If anyone has a suggestion as to how to find a way to play with those mods or what is happening I would appreciate it. I really like the Someguy Series mods and would happily start a new game with them if I could get them to work without having to sign out every time I quit the game.

[dubiousintent]

While I have had some issues with the SomeGuy Series mods, none occurred simply because the mods were loaded (but I am not on Win10 either). "The Inheritance" in particular was troublesome, so you might want to try without that one. I simply installed the NVB series one at a time as I completed each previous one.

 

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' (NVSR related)
* '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'

The "FastExit" setting in NVSR does work with Win10.

 

-Dubious-

[wfandrews]

Thank you for your reply Dubious. I will try your suggestion of not loading NVBII until I have completed NVBI. Other the problem with those mods I am very happy with the performance of this game in Win 10; a sharp contrast to my feelings a week or so ago when I thought my problems were a direct result of this OS. Although they were in a way, but just because the OS was corrupt.