Jump to content

Long "Micro Stutters" occurring in Exteriors


mshane951

Recommended Posts

Hello, Recently I starting dealing with these "long" aka up to 2 seconds long micro stutters every 15 seconds when travelling out in exteriors. Its nothing game breaking and as soon as I enter an interior it is gone, I know it is LOD of world-spaces related but I am not sure how to fix it. I played around with new vegas stutter remover to try to fix it however it does not seem to do the trick, crashing is rare happens on average of every 2 hours or so nothing that is of concern. I am under the assumption that mods are the cause particularly those who affect the exteriors widespread such as NMC's texture pack. Not sure if this matters but I am below the "hypothetical" plugin limit which does not really exist but is commonly thought of 130ish plugins at 116. In case the size of my game matters, it is about 30 gigabytes in total roughly 21.3 gigabytes of mods. I went way beyond this is Fallout 3 which is roughly 40 gigabytes with 180ish plugins and the stutter there is minor nothing like here. Its probably some sort of mod conflict or so, so if you know this type of issue take a look at my modlist and plugin list.

Thanks

 

Edit: I am running through the FNV4gb.exe which helps with stability.

Edited by mshane951
Link to comment
Share on other sites

NevadaSkies - TTW Edition.esp

 

This is a plugin bundled in the Main Download file of the Nevada Skies mod on Nexus. It's purpose is to provide the mod content to those users running the Tale of Two Wastelands project.

 

uninstall the out dated version and install the updated version.

 

reason.jpg

Edited by Purr4me
Link to comment
Share on other sites

  • 2 weeks later...

Alright after some very careful sorting the stutters were fix, does anyone have ANY CLUE on how to fix this godforsaken out of memory error? Please, its really bad. Plugin limit cannot be the issue so don't say that since I know its not true. I am at 121 active plugins.

My updated modlist is below.

Link to comment
Share on other sites

* If you are using the full 4GB of memory, most likely your CTD problem (now or in the future) is the default "heap size" is too small. It's so common you might as well deal with it now. Please see the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu') entry in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* You can also get "out of memory" errors from the graphics system (which is separate from exhausting system memory), even with the game 4GB enabled. The video pipeline is known to have "memory leaks", and these occur faster with "beautification mods". Here the cause is a combination of larger image sizes ("higher resolutions", aka "hi-rez"), hi-rez texture packs for skin, hair, clothes, weapons, and landscape; along with mods that increase the number of NPCS in a given cell. (All those hi-rez texture "personal accessories" get multiplied by the number of Actors.) Please see the wiki "Display resolution versus Image Size" article. While "ENBoost" can help, you may need to switch to lower resolution/ smaller sized images or even lower quality in your game graphics configuration.

* Don't install every optional file for a mod. Read the install instructions carefully. Optional files need to be selected on a "case by case" basis. For example: with any mod you usually only need one ESP (and possibly one ESM) "base" file depending upon whether you have all the DLCs active or not. Only if you don't have them all active do you need to install any specific DLC versions if there is an "Ultimate Edition/All/Merged DLC" version.

 

I.e.: You probably don't need the individual "WME - GRA ..." files if you have "WME - GRA Complete" installed. You definitely do not need "WME - Ironsights - DLCs.esp" and "WME - Ironsights - GRA.esp" when you have "WME - Ironsights - DLCs + GRA.esp" installed. The latter combines both of the former into a single plugin.

* "Compatibility patches" to make one mod work with another need to be placed after (as in "physically lower, higher numbered") in the "load order" than ALL of the plugins they are designed to make compatible. (This also applies to "fix" files.) ESMs should always be placed at the top (lowest numbered) positions in the "load order", followed by the related ESPs though they can be separated from their ESMs by other plugins. LOOT does a good job of determining those basic orders. Getting the "load order" incorrect will cause "Missing Masters" errors as well. You can make minor adjustments to the order and tell LOOT how to remember them. It's in the on-line documentation under "Metadata".

FYI: The "pre-order packs" (aka "POPs": Caravan, Classic, Mercenary, and Tribal; available now in the "Courier's Stash" addon), are not considered "true DLC expansions" by most mods and are treated as "compatibility patches" because they just add certain unique items. So their absence should not deter you from using "All DLC Merged" plugins. Where they are included, they should come after "GunrunnersArsenal.ESM" which is a true DLC expansion. When in doubt, follow the process in the wiki "Missing Masters" article to confirm they are not "master files" for that plugin.

* Don't install every optional file for a mod. Read the install instructions carefully. Optional files need to be selected on a "case by case" basis. For example: with any mod you usually only need one ESP (and possibly one ESM) "base" file depending upon whether you have all the DLCs active or not. Only if you don't have them all active do you need to install any specific DLC versions if there is an "Ultimate Edition/All/Merged DLC" version.

* "Compatibility patches" to make one mod work with another need to be placed after (as in "physically lower, higher numbered") in the "load order" than ALL of the plugins they are designed to make compatible. (This also applies to "fix" files.) ESMs should always be placed at the top (lowest numbered) positions in the "load order", followed by the related ESPs though they can be separated from their ESMs by other plugins. LOOT does a good job of determining those basic orders. Getting the "load order" incorrect will cause "Missing Masters" errors as well. You can make minor adjustments to the order and tell LOOT how to remember them. It's in the on-line documentation under "Metadata".

FYI: The "pre-order packs" (aka "POPs": Caravan, Classic, Mercenary, and Tribal; available now in the "Courier's Stash" addon), are not considered "true DLC expansions" by most mods and are treated as "compatibility patches" because they just add certain unique items. So their absence should not deter you from using "All DLC Merged" plugins. Where they are included, they should come after "GunrunnersArsenal.ESM" which is a true DLC expansion. When in doubt, follow the process in the wiki "Missing Masters" article to confirm they are not "master files" for that plugin.

* Don't install compatibility patches for mods you do not have installed/active (e.g. get rid of any "TTW" patches if you aren't running TTW). The reverse also holds true: don't install mods that are not compatible with, or specific to, TTW or FNC if you are playing with them.

* You really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article.

Don't use competing mods that attempt to do similar things: such as WME and WMX. With "overhauls" there is more likelihood that they will make competing changes to the same things. In those instances, you will need to manually adjust your "merged patch" file to reconcile the differences between their approaches; and then repeat the process if they are updated.

 

Please see the 'Common Game Problems' section of the wiki "FNV General Mod Use Advice" article.

 

-Dubious-

Link to comment
Share on other sites

Alright yeah I found the fix the dxd9.dll but this presents a new problem, the interface essentially lost its entire stabiltiy, it lags terribly when I open the main menu, shooting is alot more laggy and there are many new issues. I don't want the out of memory crash or this so I am trying to find a middle ground and its just not working for me.

Link to comment
Share on other sites

Alright yeah I found the fix the dxd9.dll but this presents a new problem, the interface essentially lost its entire stabiltiy, it lags terribly when I open the main menu, shooting is alot more laggy and there are many new issues. I don't want the out of memory crash or this so I am trying to find a middle ground and its just not working for me.

sent required files for graphics on discord

Link to comment
Share on other sites

  • Recently Browsing   0 members

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