Jump to content

Game lagging after a long playthrough


charwo

Recommended Posts

I'm used to the game slowing down after playing a session. The solution is simple: restart. But now after well over a hundred hours of single playthrough, the game is lagging severely from the moment the save boots up. I'm playing a ton of mods, and I'm trying to get through the Someguy Series, and I'm about halfway through New Vegas Bounties II. I started a new game as a test and it's not lagging any more than usual, and I also cleared out a majority of my save game files so I've eliminated save bloat.

Do I need to start a new game, or is there something else I can do?

Link to comment
Share on other sites

What size are your saves? If they are unusually big then that may be why. Save bloat is probably the cause for your lag. If not that, then something in your system may be causing a bottleneck all of the sudden when playing this game. The problem with Bethesda games is that everything is kept in your save, and over time that all adds up to a very large save file. That is why things will get less playable over time - although sometimes certain mods can increase the speed of this process and that is not a good thing.

Link to comment
Share on other sites

Games will always lag after a long playthrough, and unfortunately unless you're an absolute mastermind at fixing up other peoples mods, you will run into lag problems due to inefficient scripts or even save game bloat. Also NV has really bad problems with managing memory so that's another cause as well.

Link to comment
Share on other sites

See the section "Solutions to Performance problems" in the "Fallout NV Mod Conflict Troubleshooting" guide for some common causes and solutions. Also look into "heap size" under 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu'.

 

-Dubious-

 

Thanks, I got it working! For anyone in the future looking at this, try going to the New Vegas Stutter remover config file in data/NVSE and find bHookLightCriticalSections=1 and set to bHookLightCriticalSections=0. It worked like a charm for me.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...