Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
On the subject, have you tried changing other settings related to bHookCriticalSections
bHookLightCriticalSections ?
I remember those lines in the ini files. Can't remember doing anything with them though. For the playthrough I was using (then I made this post), I did not edit those lines. I left them at their default values.
Lots of players use the stutter remover and this will save their game.
Glad I could help. More people need to hear about this. It could also help push for a patch in the modding community
bManageFPS = 0
bHookCriticalSections = 1
bHookLightCriticalSections = 0
bHookHashtables = 1
bReplaceHeap = 1
bReplaceGetTickCount = 1
bFastExit = 1
bFlushLog = 1
iSchedulingResolution = 1
bReplaceRandom = 1
bExperimentalStuff = 0
iMainHookPoint = 1
}
Under Heap replacement:
Heap = {
_comment =This section is disabled by default - see Master/bReplaceHeap
_comment =I recommend enabling it however.
_comment = Heap replacement can produce MAJOR improvements in performance on Oblivion at a significant cost in stability
_comment = It crashes instantly on Fallout3 last I remember checking
_comment = It seems to work on Fallout: New Vegas ?
_comment = Algorithms: 1=FastMM4, 2=Microsoft (slow on XP), 3=SimpleHeap1, 4=TBBMalloc, 5=ThreadHeap2, 6=ThreadHeap3, 8=tcmalloc
_comment = Algorithms numbers 1, 4, and 8 require external DLL files in the Data/OBSE/Plugins/ComponentDLLs folder
_comment = Size is in units of megabytes, and only effects algorithms 3, 5, and 6 (other algorithms dynamically determine their own size)
iHeapAlgorithm = 6
bEnableProfiling = 0
iHeapSize = 256
bEnableMessages = 0
bZeroAllocations = 0
I also use an ENB with memory management enabled and NVAC (which is surprisingly compatible with Fallout 3). Coupled with Zans Autopurge (might not be necessary) and increased initial heap size. Along with the standard Fallout.ini fixes (i.e. bUseThreadedAI=1
iNumHWThreads=2). With all of that, my game doesn't crash after about 3 hours of continuous play (that's only because thats all I tested, it still didn't actually crash). With these settings, I also still get the performance advantages with the stutter remover. Even when the FPS drops in a few areas, it maintains relatively smooth gameplay and is very much playable, but its only a few areas.
This was years of testing, but it might be worth a shot if you have similar specs (may not be specifically based off my specs though, except for the memory stuff). I'm on Windows 10. GTX 1080ti, i7-4790k, 16gb RAM.
Before using stutter remover, first make sure you are actually experiencing "stutter". What is stutter? Simply put, it’s any RENDERING anomaly that occurs that causes the time between frames to noticeably vary. Why is this important? Most of the stuttering you experience is actually "pop-in". Pop-in is a performance issue in three-dimensional graphics, causing objects or textures to "pop" suddenly into view as they are loaded, rather than smoothly moving into view.
The effect can be incredibly similar. Both can make the game feel... like it's pausing/ freezing. The issue is stutter remover won't do ♥♥♥♥ for pop-in. Only having a faster drive will. Even on an Adata XPG SX8200 Pro, I still get a bit of pop-in, though it's many times less than what it looks like on my WD 7200 HDD.
Then you also have the instability that stutter remover introduces to the game so even if it fixed anything, it's hell to get it to work. What works for you is not a guarantee that it will work for everyone. Best to avoid that cluster ♥♥♥♥.
Just use the 4GB LAA Patch, FOSE, and your unofficial patch of choice. Plus other required fixes/ patches if you want to mod (archive invalidation, etc.).
I agree that the so-called "stutter" is largely just texture/mesh loading and all assorted pop-in stuffs, but I don't agree that the stutter remover is just a placebo. It definitely has some memory management functions (like heap replacement) that (from my limited understanding), serve to partition more memory (either RAM or video memory) for the purpose of reducing pop-in.
I to have Fallout 3 on an SSD for the same reason as you do (to reduce pop-in). But I've definitely had a noticeable decrease in performance when not using the stutter remover's memory management functions than when I actually use them.
Of course, I also have about 100 HD texture mods (that are something like 20GB of additional textures in size), so maybe the beneficial effects of the stutter remover's memory management (and aforementioned ENB memory management) are more easily visible than by just playing the game with default game textures.
Again, a useless addition of info. I don't use it at all, just tried with 102 plugins, and it doesn't help. Enabled all of the garbage settings and crashed before I could walk. Tweaked it to your settings, still crashes in under 10 seconds. Disabled everything except heap and it works, sort of. Still got a crash after 10 minutes. Uninstalled stutter removed, and reverted to a save before using it. Viola, game runs smooth as usual.
So, maybe I'm an exception, maybe not. I do have 4 different rigs. XP, 7, 8.1, and 10. The stutter remover either makes it worse, or no change at all for all 4.