- Joined
- Sep 27, 2023
Never had this problem before, must be a technical problem on your end and nothing with the game. People who run 4K texture mods and other graphical enhancements do tend to run into lower FPS/lag spikes, so I would remove these first thing and check if the game works better.Debugging New Vegas whilst trying to mod it is a huge pain, I've got a pretty big modlist myself and every 20 minutes I experience these 2 minute-long lag spikes, and when I say random and lag spikes, I mean out of nowhere and going down to like 5 FPS, mouse lag included. I can chalk this up to the game compiling shaders, or loading assets, but when I open the Pip-Boy the game returns to a smooth 60 FPS. The thing is, there's one specific area on the world map that consistently lags for me (Goes down to 10-15 FPS) but when I open the Pip-Boy the FPS remains the same.
I've got plenty of technical know-how myself and I've debugged other games but New Vegas has no easy-to-access debug mode that you don't need dev tools to access, I guess that's just part and parcel of trying to run it on an engine made in 1997.
I've actually had this problem in London and one particular mod in Fallout 4, but that is a strictly engine related problem and is a sign of a lack of knowledge on the modders part. In short, Fallout 4 GECK is much more temperamental than the FNV/F3 version of the geck, if you remove something from the map in a wrong way or even place it in the wrong way, it fucks up the entire area and you suffer horrific lag spikes on even the best machines. This is what happens with a lot of amateur mods who don't know how the GECK works, in London's case a lot of green areas like the country side lag the game because the grass adds "invisible" lag spikes due to how foliage works in this engine, especially in higher fidelity. Pepper the area with high quality grass, bushes and trees, and you get single digit frames. For Fallout 4, it is usually a modder not placing something properly or haphazardly removing something from the map, and similarly you get "invisible" lag spikes from a confused game that tries to parse the cell in the wrong way. As far as I know, this isn't the issue for F3 or New Vegas, or at least I didn't encounter this issue there.
