ENBoost causing problems?

[BabylonNoir]

I don't know if I'm doing something wrong or what, but I installed ENBoost (wrapper version) and it's been causing me problems. For example, after I install it and I'm in-game, I'll enter or leave a building and it just keeps loading. And if it does eventually finish loading, once I'm outside everything is glitched out followed by a short freeze, which forces me to Alt-Tab out of the game and force quit it. Also sometimes when the game launches the menu never loads up. I uninstalled and reinstalled ENBoost to make sure that was the problem, which seemed so. Also, not sure if matters, but I'm using a laptop (NVIDIA GTX 1070 i7-7700HQ). Any idea why or what I should do? I'm fairly new to modding NV so if you can be more specific I'd appreciate it.

Edited April 3, 2020 by BabylonNoir

[dubiousintent]

ENBoost uses some of your general system RAM and allocates it to the video pipeline. It's purpose is to "buffer" video from the hard drive into faster system RAM, as a stopgap before the demands of the even faster VRAM of the video card. (See "Stuttering" below.) But when you "change scenes" it's less likely to have cached the art assets of the "new scene" such as when you switch between interior and exterior cells.

 

Have you looked at the 'Solutions to Post-Processor (ENB/SweetFX et. al.) problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article?

 

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-