FPS drop at Pause Menu

[tank12758]

Hi all!

I cannot find any information on the web about this problem. I started a new game and whenever I use the pause menu, the fps drops from ~58 to ~15-18 fps. It stays this way until I load into a new cell. I use ENB for graphics and NVR for its performance capabilities. I have spent 7 hours + modding my game and when I installed CASM this happened. I uninstalled it and this issue persists (may not be CASM). I do have NVSR and NVAC. Autosaves are off, threadedai is used, a bashed patch was made, and a merged patch was made, so I have the basics. Any suggestions are welcome. Here is my load order: https://pastebin.com/ce3vSQEJ

Here is my fallout.ini file: https://pastebin.com/vtD7H4t1

Thanks for the help!

 

[tank12758]

The issue *seems* to be triggered by menus in general. The longer the duration in a menu, the more often this happens. Also never mind on loading cells completely solving it. It sometimes solves it, which could mean that its just a duration problem. I also get infinite loading screens which seem tied to the problem.

Edit: I disabled all UI mods and the problem persisted and had an fps drop even earlier, almost immediately.

Edited May 28, 2019 by tank12758

[dubiousintent]

Menus of all sorts generally don't care about FPS. They are (by design) waiting on you (the user) to make some input and to signal that you have done so (usually with either an <Enter> or some hotkey). That your FPS is still low AFTER the menu closes is the problem.

 

Nothing in your load order jumps out at me as a potential cause, except that you are heavy into "beautification mods" which means you might be stressing your graphics system pipeline. Switching to a menu may have been enough to push the pipeline over the edge. "FPS drop" is very similar to "stutter or micro-stutter" issues.

 

Re: Stuttering or "micro-stutters". All visual stuttering problems are caused by the video stream having to wait for the "art assets" required to render the display OR the game writing something to disk (such as a save game file or logging). Mostly these are due to the hard disk drive being orders of magnitude slower than VRAM, with System RAM (e.g. "ENBoost") and "solid state drives" (SSDs) being in between. Keep in mind that this game was designed for older PC and XBox console systems, and it is now possible for your new "latest and greatest" gaming machine to be faster than it can handle. There are internal design choices that cannot be overcome. The "video pipeline" has always been prone to problems. The following are "mitigations" that have been found to help some people.

Please see the following entries under the 'Solutions to Performance problems' section in the wiki Fallout NV Mod Conflict Troubleshooting" guide if you haven't already.
* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'
* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed'
* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'
* 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' for other settings that can indirectly affect micro-stutter.
* There are also some NVSR configuration suggestions under the 'Issue: Game in slow motion' and entries. (These will not help with the "Tick Fix" alternative mod, but the author of NVSR now has a suggested configuration for Win10 linked there.)
* The 'Issue: What's with these Solid Green billboard signs in the distance (LOD)?' entry under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section can also help if your problems started after you installed VWD/LOD texture packages.
* If you are using CASM or some similar "auto-save" mod to manage your save game files (recommended), try increasing the "time between saves" set in the "save frequency"; and reducing the number of occasions it saves to the minimum (e.g. disable most "Autosave Events" in CASM) and see how that impacts the game seeming to freeze temporarily.
* If you have "NVSE logging" enabled (see the 'Checklist Item #4' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide), disable it until actually needed.

Reading from or writing to disk for any reason is the slowest thing the game does.

The size of your image files also has an impact. Larger/higher resolution is not always "better". Please see the wiki "Display resolution versus Image Size" article.

The 'Issue: What INI edits seem to be most beneficial to performance' entry of the wiki "Fallout NV Mod Conflict Troubleshooting" guide) may also be some help. However, the above mitigations are more likely to have a fundamental beneficial effect with or without any INI adjustments, so consider them as the last resort.

As you can see, there are a number of things that can underlie your problem. If one of these doesn't fix it, I would be interested to hear about any eventual solution that does.

-Dubious-

[tank12758]

Thank you for your post and help. I tried all of the solutions you listed and even retried the ones I have done before. Nothing I have tried has affected the fps drop. This is most likely some settings file or something on my computer, so I am just going to do a reboot on my game.

[tank12758]

Update- I redid my modded new vegas exactly as it was before when the problem existed, except I ran it on Windows 7. Runs smoothly at 60 fps. If all else fails, just get Windows 7. 10 has too many issues.

Update 2- Win7 broke after a while, it was really just OneTweak for some reason

Edited August 6, 2019 by tank12758