Still getting stuttering after installing NVSR and then some.

[Moredy]

So after installing NVSR (following the step guide to get get the ini file optimised) and then following this guide using number 7.6, I still get stutters quite regularly and enough that it is quite annoying, I certainly don't remember New Vegas running like this before so I don't think it's my hardware, just in case I have an i5-8600k, a GTX 1060, 16gb RAM and Windows 10. I'm using Mod Organizer for my mod manager and have used LOOT to sort my load order and the stutters mainly happen when i'm just walking around outside, the cause is probably new terrain etc loading in. Here is my load order.

 

Any help is appreciated,

 

Thanks.

Edited July 16, 2019 by SpankeyDankey

[dubiousintent]

If you add (or remove) any VWD/LOD textures (such as NMC, Vurt's WFO, or Ojo Bueno), please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the need to run both TES4LL and FNVLODGen; or xLODGen - Terrain LOD beta for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL. Also recommend you read the 'LOD/VWD Texture Packs' section of the wiki "FNV General Mod Use Advice" article first.

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.

The wiki "Fallout NV Mod Conflict Troubleshooting" article is a collection of problems and solutions. It does not attempt to be a "step-by-step guide". You may need to check and possibly implement all of the "Issues" in section 7 (Solutions to Performance problems). The "S.T.E.P." guide is very good. This article attempts to provide solutions for things that either don't work for all people / systems or are not otherwise provided, because there are so many variables.

 

-Dubious-

[Glenrhee]

If you use Mod Organizer I'd actually recommend not using any kind of LOD generator. They've got known issues working MO's file system and I noticed more stuttering, worse performance, and uglier LODs after using them in both NV and 3, all of which went away when I deleted their generated LODs.

[dubiousintent]

Please see the short thread "TES5Edit Generate LOD (via MO)". Summary answer from the author zilav: "You either need to disable BSA management in MO, don't use MO or unpack archives."

 

-Dubious-