Jump to content
Kelmych

Problems with Fallout Stutter Remover

Recommended Posts

Fallout Stutter Remover has been a great help reducing problems with the Fallout 3 game engine (and Fallout NV and Oblivion) but several users have recently reported problems with some of the recommended settings for the associated INI file.

 

iDefaultMode = 3 (under Critical Sections)

Audley mentioned recently when using the new Fall Creators Update for Win 10 that setting this parameter to any value other than 1 caused constant crashes

GeneralJohn reported recently in a Fallout 3 Nexus FSR post that setting this parameter with the Fall Creator's Update to any value other than 1 caused freezes

 

bHookLightCriticalSections = 1 (under Master)

Gopher's suggestion is to set this to 0

Audley previously mentioned in the STEP guide form that setting this to 0 caused a drastic reduction in FPS on his system

 

bReplaceHeap = 0 (under Master)

 NVSR creator's recommendation is to use 1, but it's a tradeoff between performance and stability

 

fMaximumFPS = 0 (Under FPS_Management)

 In the Fallout 3 FSR Nexus page Loveblanket mentioned the possibility of setting this to 30 to reduce FPS and allow using higher resolution textures on his system (I'm not sure whether other users will find this useful).

 

iHeapSize = 250 (under Heap)

 In the Fallout 3 FSR Nexus page Loveblanket mentioned the possibility of setting this to a larger value (between 250 and 450) to accommodate the increased memory provided by the LAA fix. This assumes, of course, that the heap is enabled.

 

 

The FO3 guide will be updated for at least the iDefaultMode comments. It would help if other users test this and other FSR parameters mentioned that seem useful to change.

 

Share this post


Link to post
Share on other sites

Do you know what the proper way to test iHeapSize would be? ... and how to see the performance/stability trade off? Never really had to test anything like this much other than Skyrim way back when. Can't even remember what I did.

Share this post


Link to post
Share on other sites

The biggest issue will be testing stability since it is affected by many things and isn’t easy to measure. Performance testing is fairly straightforward. I don’t have any performance problems with FO3 soI leave the heap off for better stability.

Share this post


Link to post
Share on other sites

iHeapSize doesn't work if heap manager is not replaced when bReplaceHeap = 0

Share this post


Link to post
Share on other sites

Personally I would 100% avoid the heap replacement features in the Stutter Remover mods. Especially for New Vegas. I value stability above all else. Yes, it could potentially improve performance for some, but at the cost of greatly destabilizing your game. I'd rather remove some demanding mods and/or turn down graphic settings for more FPS rather than rely on something unstable like that. Perhaps it would be different if Skyranger had spent more time with the plugins and optimized them more, but he seems MIA at the moment, and probably won't likely be coming back. 

 

What's more is that there is a link between the Stutter Remover mods and the latest Windows 10 (Fall Creators Update) update. I am not knowledgeable enough about this kind of thing to understand how the Fall Creators Update plus the Stutter Remover (with bHookCriticalSections set to 1) will cause constant crashes. What's more is that the crashes seem to get worse the larger your save gets. I have now confirmed the Stutter Remover causing crashes by several of my modding friends.

Share this post


Link to post
Share on other sites

I use windows 10 but haven't gotten to the point of testing the Stutter Remover's settings out yet. Will be in a week or so. 

So is consensus, at the moment, that some of the features still work well or none of them?

Share this post


Link to post
Share on other sites

Hey Folks,

I have my windows 10 updated via auto updates up until it's most recent point (checks every day). Just installed Fallout Stutter Remover and the stutter that I previously had is gone and I have no crashes. I use the latest main file of the mod and I apply what Kelmych has in the Clear and Present Danger guide. Would some people (me) miss the Fall Creators Update somehow? I am having no issues with it at all.

Share this post


Link to post
Share on other sites

Check your OS build in: Settings - About. If it is Version 1709 with the OS build of 16299.64 then you are on the absolute latest build. (It may be possible to have 16299.xx and still be classified as the latest. Not entirely sure about the numbers after that decimal place.)

Share this post


Link to post
Share on other sites

So I was curious and had to update my OS. Fall Creators Update. OS Build 16299.64 .... Fallout Stutter Remover works like it always did for me. I ran from Paradise Falls to TennPenny tower without any crashes or oddities (12 minutes real time). No mods only .ini Tweaks.  Version 1709 (it literally says Welcome to Fall Creators Update after you install it). 

Share this post


Link to post
Share on other sites

I recently changed FO3 to use the GOG FO3 GOTY version vs. the Steam GOTY version.  I use Windows 10 and it was updated a little while ago with the Fall Creators Update. I am using INI files based on the values that BethINI sets for FO3, the additions in the FO3 guide, and some of the INI recommendations in the recent GamerPoets video on INI changes. I'm not using ENBoost since ideally I shouldn't need it with the gaming system I am using.

 

I have a problem with FSR. If I leave it out I don't have any stability problems. If I include it I typically get crashes after ten minutes or less playing FO3. I started with the Roy Batty FSR INI file that GamerPoets included in the Fallout 3 My Way Nexus page. I changed iDefaultMode (under Critical Sections) to 1 and I still have the same problems. I tried several different sets of Fallout.ini and FalloutPrefs.ini parameters, running with and without ENBoost, but the stability problem doesn't change.

 

Any suggestions?

Share this post


Link to post
Share on other sites

I just went through this with New Vegas, the only thing that helped was removing NVSR completely.  It appears to be broken with the Creators update - I found a thread or two on Reddit  where people were describing the same issue, and a TTW guide author here, Adonis seems to confirm as well.  As for what to do - play a stuttery game, unfortunately has been my solution.  I've been waiting too long for mod updates that never came, and watching Gopher too much to wait more.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Majorman
      Discussion topic:
      FNVLODGen by zilav
      Wiki Link
    • By FuzzyDuck
      Hoy folks! 
      I'm looking into doing some Oblivion streams in the future, and was looking into mods.
      Wanted to know if there is anywhere some modern\updated guides, and what manager, those whom do oblivion modding use nowadays?
      MO1? MO2? Vortex?

      I know it's an old game, but searching  the only guides i found were from from 7\6 yrs ago! So, anyone could give some help on this front?
    • By sheson
      This is a beta of [FNV|FO3|FO4|FO4VR|TES5|SSE|TES5VR|ENDERAL|ENDERALSE]LODGen/Edit with terrain LOD meshes and textures generation.
      This is for experienced mod authors and users that know how to use xEdit, xLODGen or DynDOLOD already.
      Installation and Setup
      Download
      xLODGen beta 85 - based on 4.1.4
      Unzip into a dedicated folder outside of any game and Steam folders or special Windows folders like Program Files.
      (Pro users can merge with existing xEdit installation. Make sure to overwrite older LODGen.exe/LODGenx64.exe TexConv.exe/TexConvx64.exe in Edit Scripts. All other files with the same filenames are the same as the latest version of xEdit.)
      Rename xLODGen.exe to [game mode]LODGen.exe (TES5LODGen.exe for example) or start with command line parameter -fnv, -fo3, -fo4, -fo4vr, -tes5, tes5vr, -sse, -enderal, -enderalse
      Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder.
      Do not generate into any game or any mod manager folders.
      Requirements
      Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which xLODGen.exe (x86) or xLODGenx64.exe (x64) is used.
      RTFM and Share Results
      See the included Skyrim-Occlusion-Readme.txt for a brief explanation of the Skyrim TVDT Occlusion data generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions or give feedback in the dedicated Skyrim TVDT - Occlusion Data thread.
      See the included Terrain-LOD-Readme.txt for a brief explanation of the settings for terrain LOD generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions about terrain LOD in this thread for a more in-depth explanation if required and share feedback (with screenshots) about results or problems.
      These tools generate LOD meshes and textures "exactly" like CK, but not like the meshes and textures which are shipping with the games (they are often manually edited).
      However, these tools provide more options and higher resolutions (use the x64 version if there are memory errors because you believe you require 4k or higher) and can be updated to add more useful features and options.
      I did some testing in the different games, but finding the best combinations of options and settings requires lots of testing and are a matter of personal opinion and which game is used, the load order, mods, even different worldspaces probably.
      That means, I am only able to give generic guidelines and hints to send you off to find and test for yourself and share your results. My main interested is that generations works correctly and without problems for now.
      Check out the thread xLODGen Terrain Settings Compare. Also refer to any modding guide which has a list of relevant mods close to your load order.
      The object and tree LOD generation is the same as the current versions of xEdit / xLODGen. Refer to their respective descriptions and explanations.
      Obviously, users of Skryim/Enderal/Skyrim SE/Skyrim VR/EnderalSE continue to use the easier and more comprehensive DynDOLOD for drastically improved object and tree LOD generation and only use xLODGen for terrain LOD (and maybe Occlusion) generation.
      First Time
      Here are suggestion to start without going crazy and that should be quick enough to generate:
      Set quality of meshes for LOD4 to 5 and then +5 for each next level. Or just set levels 8/16/32 to 10.
      Check protect cell borders (yes it fixes the ugly terrain drops at outer cell borders that still exist in Fallout 4).
      Use the max vertices setting only if you want to hard limit max file size.
      In Skyrim Special Edition or Skyrim VR, if you notice terrain briefly flickering when new areas are loading in, set [Display] bEnableLandFade=0 in Skyrim.INI
      Set Optimize Unseen to off for LOD4 for first generation. Start experimenting with a value of 550 with a quality setting of 10 or lower for LOD32 (used for map) and compare coastlines and file size to other settings.
      To quickly generate terrain LOD meshes just for the map, check only terrain LOD Meshes, check the Specific Chunk checkbox and set drop down to 32. Leave SW fields empty for complete map or set SW cell coordinates to same values as a *.btr filename to test a specific area with lots of water, river etc.
      Set texture sizes to 512 for a start. Larger sizes and large world spaces will take a considerable time (like 15 to 30 minutes or more easily). Each higher resolution means quadruple the work.
      Use DXT1 for diffuse and 565 (DXT1 if on Windows 7) for normal maps. If generating for Skyrim Special Edition use BC7. Uncheck mipmaps, raise steepness and Bake normal maps.
      For now, leave the Brightness, Contrast and Gamma at 0 and 1.0 respectively. It seems that only Skyrim CK and Skyrim SE CK are manipulating the intensity of the textures to adjust for the noise.dds and the god awful "improved" snow shader of Skyrim SE (just turn that thing off, really). If textures seem too dark in the game, brighten the noise.dds instead or vice versa. That way you can get perfectly matching LOD textures that look just like the textures in the loaded cells. For Skyrim a good average color of the noise texture seems to be around #C0. See below for a couple noise texture downloads.
      If you want to test larger texture sizes, use the chunk option to limit the number of textures that need to be generated. For example, check [x] Specific chunk, leave the drop down empty and set WS to the lower left cell coordinate of an 32x32 area, like 0, 0. It will then generate all textures up to 31,31. Not all worldspaces have their origin at 0,0 so you will have to check already generated meshes/texture filenames for their lower left coordinates.
      Questions and Feedback
      Obliviously anything related to terrain LOD should be posted in this thread.
      Posts related to Occlusion should be made here.
      Recommended Optionals
      TES5-Terrain-Tamriel.esm (Mega), SSE-Terrain-Tamriel.esm (Mega)
      TES5-Terrain-Tamriel-Extend.esm (Mega), SSE-Terrain-Tamriel-Extend.esm (Mega) - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm (Mega) - Entire map from -96,-96 to 95,96 with northern ocean extension. Useful for mod authors.
      Put in game data folder obviously. Adds back terrain for Skyrim (Tamriel worldspace) at the outer edges so there is no missing terrain meshes/textures when generating terrain LOD for Skyrim.
      Load as early with lowest priority as possible, so that any other plugins overwriting or adding land records or cells with the same coordinates take precedence.
      Only required to be loaded when generating terrain LOD. No harm done when loaded in-game but typically the player can not get close to these areas. There are no effects outside the far away added cells.
      Noise
      Single color flat noise, Adjusted vanilla noise, HD Terrain Noise Texture SE
      Examples for Skyrim. Install to game folder like any other texture mod. The noise texture is applied in-game on top of terrain LOD textures, so no effect for LOD generation.
      Only the red channel is used in case the textures is not a grey channel format. MipMaps are ignored. The textures is tiled 3x3 per LOD quad, e.g. for LOD level 4, the noise texture is repeated 3 times to cover 4 cells, for LOD level 8, the noise texture is repeated 3 times to cover 8 cells and so on.
      Test-Terrain-Tamriel.7z
      For testing terrain LOD distances. Plain color terrain LOD textures for Tamriel with coordinates for every LOD quad. Green for LOD 4, yellow for LOD8, blue for LOD 16 and red for LOD 32.
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.