sa547

Ok, I'll have to use a different source.

Clicked on the spoilers. Didn't show anything inside.

Optimially DCE requires having 32gb of memory or more, which makes best use of the mod.

https://www.nexusmods.com/skyrimspecialedition/mods/100975 It's been several weeks ever since Disk Cache Enabler was released not only for Starfield, but also for Fallout 4 and SSE/AE. Prior to DCE, for years I've tried many attempts at improving performance, anything to get rid of stutters, abandoned LE for SSE, and I even saved up and built a new PC specifically for this game and Cities Skylines, but almost everyone knows that modded games must be on a very large SSD, so that there is little to no stuttering, something which is beyond what I could afford on my current salary (sorry, more than half of that salary is for daily needs; at some point in the future I would move my games to an SSD, but then I stick to hard drives because they are easier to recover. There is PrimoCache, but personal complications prevent me from using credit/debit cards just to buy it). Reading the original technical description of the mod for Starfield: Why the author chose to have two versions of the mod for different versions of the game isn't explained in full, did not explain what are the "overheads" which makes the Universal version different from the 1.6 version, but regardless, DCE Universal is working as much as its 1.6 counterpart, as they cut down on I/O operations which translates to little to no micro-stuttering. This far, I've used the FO4 and SSE (the Universal version, instead of the 1.6-only) versions of the mod, and suffice to say that as they made the most of the installed RAM on my PC, loading assets into memory as I go, the mod made those games truly playable even on a hard drive, as I have racked more hours playing both games than without the mods. The mod also encouraged me to weed out scripted mods causing freezes, as I uncovered culprits found with XPMSSE and promptly replaced them with XPMSSE Lite without the scripts. I do have to say that DCE works best if you have 16gb or more of installed memory (my PC has 32gb) and a hand-tuned page file, especially as some of that memory isn't utilized much by those games. That I feel DCE is a great upgrade for free for those specific games, as opposed to Primocache which, while touted as being superior and can be used for almost every application to speed up I/O operations, is a paid program and may not work for everyone. Damn, wish this mod was made many years ago.

Getting rid of the "shrink-wrapped" mountains after enabling the Terrain Underside option, turns out, needs a readjustment of [TerrainManager] settings in SkyrimPrefs.ini -- setting them to Ultra values solved the problem. fBlockLevel0Distance=35000.0000 fBlockLevel1Distance=70000.0000 fBlockMaximumDistance=250000.0000 fSplitDistanceMult=1.5 fTreeLoadDistance=75000.0000

So I finally solved a problem why I had "plastic-wrapped mountains" after enabling the Terrain Underside option before generating -- it's because of Terrain Manager settings that were set too low in Skyrimprefs.ini, especially fBlockMaximumDistance. Previous (I think BethINI did these settings): fBlockLevel0Distance=50000.0000 fBlockLevel1Distance=72500.0000 fBlockMaximumDistance=94000.0000 fSplitDistanceMult=4.0000 fTreeLoadDistance=72500.0000 After setting to vanilla Ultra settings: fBlockLevel0Distance=35000.0000 fBlockLevel1Distance=70000.0000 fBlockMaximumDistance=250000.0000 fSplitDistanceMult=1.5 fTreeLoadDistance=75000.0000 No more "plastic wrap"!

About this mod, the texture pack is visually great. However, I daresay I once went forward to the author politely asking about the overly-bright snow shaders. Unfortunately he seemed to be very defensive in his decision making the shaders too bright at night, especially as I removed the altered shaders from his plugin as a corrective measure and for the sake of consistency and compatibility.

Here's the files as requested: https://mega.nz/folder/7YESWJAJ#h0NHfNrDFSORKb3spUE54A As far as I have seen, 3DNPC modified the cell's navmesh, and Immersive Encounters added an NPC in that same area with the quest in question, but were not included in the occlusion generation. Will try to run the quest sequence again with default values and settings, using the original occlusion plugin, and report my findings, as for all I know it could also been possibly a memory leak during the time it happened until I rebooted the PC later.

After doing the above instructions, marking cell 6FE1 as modified, I ran the scenario to recreate the conditions which caused the CTD, and the game successfully produced a savegame.

Did as directed, removed all records but the affected cell, then ran the quest as usual and was able to make a savegame without crashing. Repeated this sequence but with SSE Fixes savegame option disabled, and again, no CTD. There were no warnings during occlusion generation with either utility. Yes, it's understandable. Been going through the video I recorded for tracking down the problem, and it appeared that a quest in Immersive Encounters, rather than 3DNPC Immersive Encounters.esp (282E8155) \ Quest \ 73A970B4 <SetteBard01> has, beyond my understanding, somehow affected gamesave function and occlusion data specific to that worldspace cell (6FE1). I do also have to note the current version of Immersive Encounters is also a beta release.

Ok, found that removing the TVDT in question from occlusion.esp resolved the savegame problem.

After generating and playtesting, there is a consistent CTD with the occlusion plugin (occlusion.esp) at Tamriel worldspace cell -36,14 (FormID 6FE1), all while trying to make a gamesave. Used DYNDOLOD 3 as directed, with the occlusion option on. Even tried generating the occlusion plugin with xLODGEN and used it. Same CTD. The only mod making changes to this cell is 3DNPC, specifically the navmesh. I may have to test again but without the occlusion plugin, see what I could possibly find. EDIT: may be a problem on 3DNPC's part. CTD happens with a specific quest. Crash_2021_9_15_16-12-14.txt

Run the launcher outside MO2, which should generate plugins.txt with the default ESMs/ESPs on.

RESOLVED: the stutter in question was eliminated after 1 hour of in-game testing. Okay, the conditions for removing the lag: I just got rid of all limiters and anything to do with vsync (.INI files) only ENB's vsync setting was enabled SSE Display Tweaks was disabled completely - this mod/fix actually works only for monitors over 60hz and therefore cannot be used with a 60hz monitor connected to HDMI Havok fix enabled SSE FPS Stabilizer disabled Skyrim Realistic Overhaul disabled (to reduce VRAM consumption as much as possible) I hope these findings should be of help to anyone using a system setup similar to mine.

After some reading elsewhere, I was beginning to realize this may be a software problem, something to do with the refresh rate and/or input lag (as oddly, I thought about 45 min / 60hz = 0.75?). EDIT: did tried your settings. Still the stutter/lag happened as predicted. I'm getting the feeling it has something to do at the hardware level, despite replacing the mouse and using the drivers. However, I do remember initially playing the game at full screen mode and never experienced something this bad, long before I began reworking my modded setup. EDIT 2: Steam Overlay disabled. Am going to disable HPET at the OS level. Also: https://forums.tomshardware.com/threads/games-stuttering-when-moving-mouse.1341451/ EDIT 3: Camera look stuttering still happened even after disabling both Steam Overlay and HPET. Note also that I dropped the mouse polling to 125hz. Happened 45 minutes (again) into the game. EDIT 4: seems USB polling may have to do something with the problem; I moved the G102 to another port, the same as what the XB360 controller is on. Also disabled controller support for SSE on the Steam page. Will report back. EDIT 5: Updated to Win10 v.202H. Problem still occurred. Been thinking if it had to do with SSE Fixes, Display Tweaks, or...? Going back to USB polling issues and/or vsync. I might have to come back tomorrow and try disabling all but only what is actually needed. This is really draining, and I am supposed to be happy with my setup. EDIT 6: a certain SSE Fixes setting concerning about VerticalLookSensitivity; I set this to false, then tested until I went over the 50-minute mark before the stutter struck again. HPET enabled manually through BCDEdit. Gonna try another shot.

Ok, I think I'll disable the display tweaks because I'm not using a 120hz display, and remove certain texture packs because of some significant VRAM consumption. Also, have to check if Papyrus did a stack dump, which means certain mods may have to be removed. Again, I cannot figure out why the controller has smooth camera view but not the mouse, and I'm not playing the game with a controller.

skyrim.ini got processed through BethINI. I don't think the [camera] tweaks are a factor.

As nobody was able to answer my question in Reddit, I think I would try my luck here. A few weeks ago, I got my modded SSE setup finally up and running so that I could make the transition after years of playing LE (and decided to use that LE modded setup for mostly development purposes), but then I've been stumped by a camera pan stutter that shows up after some 45 minutes in-game and it happens every time, forcing me to quit playing. Also inexplicably, when I tried using camera look with the XBox360 controller (I normally use for The Crew 2), it was smoother than what I could use with the mouse, and I don't know how that happened. So far, I've just looked through (and perused some possible diagnostics and fixes from STEP and Phoenix Flavor) skyrimprefs.ini (ran BethINI on it, disabled vsync) enblocal.ini (also disabled vsync) installed SSE Display Tweaks and enabled only vsync with it and added limitations to only 60 FPS, tried Havok Fix and FPS Stabilizer, and these didn't work either configured the GeForce panel for the game (no effect) even bought a new G102 gaming mouse because the poll rate of the office mouse I used for years wasn't good and I thought replacing the mouse would work bought a new secondary monitor and removed all VGA cables and adapters, going for an all-HDMI setup to get the framerate within control (still the stutter happened) unplugged the XB360 controller (didn't work) Here's my current modwatch list, btw, as some of the installs were salvaged from the (Wabbajack) Keizaal setup and included into my setup. Note that I am using Silent Horizons ENB for Dolomite. Here's the current hardware setup: Ryzen 5 3500 @3600Mhz; processor boost disabled 32gb of memory at 3200 Gigabyte GTX1650 Super with 4gb of VRAM The game and the rest of the Steam directory is installed on a hard drive MSI Afterburner set up to run the cooling fans with custom curve One 27" LCD display, another is a 24" LED, both now connected with HDMI cables and run at 60hz; this is by far what I could only afford... Yeah, of course, I went through searching every thread for a possible solution answer, tried and still got this predictable stutter coming out of nowhere. I do not wish to spend any more money on a new but expensive *sync monitor and/or a GPU to solve the problem. I do also have to note that every other game worked fine at good FPS rates, but SSE. ----------------------- Update: may look into disabling hardware acceleration in Discord, which by default had been enabled. Didn't work. Update 2: Tried disabling vsync completely and relied on framerate cap. Didn't work either. Other queries and answers elsewhere said that I'm using too many large texture replacers over 2k in resolution (those also came from Keizaal) and I may have to remove many of them if only to reduce the amount of VRAM consumption. Still another said that I may have a Papyrus stack dump.

A bit late to the discussion, but due to the utter lack of official support for new lands after Mitch did the last for Wyrmstooth, I had to modify extensively the CH scripts so as to make that mod usable, I mean, allow my steed to run on other worldspaces. The scripts and how I described the process of recompiling them, is here and free for further modification: https://www.nexusmods.com/skyrim/mods/99374

Regenerating the LOD worked, as no errors were reported after running the occlusion option.

Ok, tested the utility on my load order. The only error so far is for the LOD meshes within The Gray Cowl of Nocturnal, as I tried generating the data for the mod's desert worldspace. [02:45] [manny_GF_Desert] Generating Pre-Computed Occlusion TVDT [02:46] [manny_GF_Desert] Land height: -2048, Water height: 0 [02:46] [manny_GF_Desert] LODsettings: Level 4 to 32 stride 32 from 0,0 to 0,0 [02:46] [manny_GF_Desert] Gathering CELL records [02:46] [manny_GF_Desert] Building height map from 1024 cell records [02:46] [manny_GF_Desert] Updating height map from terrain LOD meshes [02:46] [manny_GF_Desert] Updating height map from object LOD meshes [02:46] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.8.4.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:46] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.4.8.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:46] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.4.12.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:46] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.4.16.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:46] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.4.20.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:46] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.4.24.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.0.12.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.0.16.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.12.4.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.16.4.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.8.12.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.8.16.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.8.20.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.8.24.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.8.28.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.12.20.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.20.4.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.12.12.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.12.16.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.8.8.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.12.24.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.12.28.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.16.20.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.16.12.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.16.16.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.20.16.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.24.16.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.16.28.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.20.20.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.20.12.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.12.8.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.16.24.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.28.16.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.20.28.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.24.20.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.24.12.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.16.8.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.20.24.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.28.20.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.28.12.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.20.8.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.24.24.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.24.8.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.28.24.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] <Warning: Error when loading "meshes\terrain\manny_GF_Desert\objects\manny_GF_Desert.4.28.8.bto": Error reading NIF block 0 NiHeader: Error in "NiHeader\Export Info\Author": Prefixed string size is negative> [02:47] [Occlusion.esp] Adding master "Gray Fox Cowl.esm" [02:47] [manny_GF_Desert] Calculating occlusion for 906 CELL records. Quality: 2 Adjust: 0 Mode: -Flat +Border

In any case, there ought to be a warning on the use of that setting, especially those who are trying to tweak the game for performance in low-spec PCs (mine's an Athlon II X2 260, with 8gb of system memory, an HD7750 with 1gb of DDR3 VRAM, and three hard drives (1tb, 2 x 500gb).

I tried out this setting once, hoping to improve performance (my Skyrim installation is on a hard drive), but instead I experienced some stuttering so I set it back to 0, the stuttering disappeared and later had a smooth 4-hour playthrough. Later I was told that this setting is to be used only for those who have Skyrim installed onto an SSD drive. https://wiki.step-project.com/Guide:Skyrim_INI/General#bUseHardDriveCache Can anyone try to add an explanation there that this setting is to be used only for SSDs?

I think this thread should be required reading for any modder, as I, like some others, had plopped in skse.ini without realizing that we were missing something very important and thus experienced CTDs/ILS despite the settings.

The specs are higher than what I use, and I think you may have to look into your enblocal.ini (if you're using a preset or ENBoost) and skse.ini (if using SKSE 1.7.1) settings, especially memory allocation and management. enblocal.ini, under [MEMORY]: ExpandSystemMemoryX64=false (if using SKSE 1.7.1 using Sheson's memory patch) ReservedMemorySizeMb=64 (since you have 2gb of VRAM) VideoMemorySizeMb=1920 (subtract 128mb from your total VRAM, as that should be reserved for Windows Aero.) EnableCompression=false (optional, should be if you need to cram in more textures) AutodetectVideoMemorySize=false Check also if you have vsync enabled in the same enblocal.ini skse.ini, under [MEMORY] DefaultHeapInitialAllocMB=768 ScrapHeapSizeMB=256 And make sure that MO has configured skse_loader.exe to have the switch -forcesteamloader included, so that Sheson's patch kicks in. The recommendations were based on what I read here: https://forum.step-project.com/topic/4985-memory-blocks-log-by-sheson/page-2?do=findComment&comment=108728 Using these has somehow given my playthrough a breath of fresh air, adding more FPS, especially when roaming in Solstheim.