trackho

So I've installed the group of CS mods in preparation of testing it with minimal edits to my currently ENB load order. From the looks of it; before I enable the CS mods, the ENB stuff that should be disabled/renamed-for-disabling/hidden are: d3d11.dll, d3dcompiler_46e.dll, enblocal.ini, enbseries.ini and the ENB Helper mod. Is that about right?

Surprisingly, while I was testing out my modlist with the Thanedom/Hamlet series , I kept CTDing when I entered some of the buildings in the mod. It took a while for me to realise that the navAI-planner-something crashes was caused by the Don't Push Me Around mod's navcut of the navmesh of the narrow interiors of the Thanedom/Hamlet mod-added buildings, especially when entering interiors that had NPCs (which automatically greeted and cause a CTD). I also disabled "I'm walking here NG" just to be safe, as NPC bumping isn't as frequent or annoying to me.

Does anyone have a good guide/list on how to use Community Shaders based on STEP? Especially making sure no incompatibilities/downright-bork from ENB-options mods in the STEP guide, as well as recommended CS mods to adhere to STEP-vision (Cathedral Weathers, etc.). I'm thinking of testing out CS but keeping my ENB stuff intact/disabled to revert as needed. Given the myriad of stuff CS and the mods that require it has, it's less straightforward from the relatively plug-and-play ENB and even with ENB, I don't run around with ENB activated all the time. Though from the looks of PBR-sorcery, the need for patching seems to put me off from that feature. The Light Limit Fix intrigues me.

So other than having some landscape seams in the meantime, it'll be okay to drop SLfSR until VLC updates to the desired state?

Do we actually need to keep the mod enabled after grass precaching is done? With the exception for those who want Extended-grass-distance, the grass generation cache already solved grass in objects per load order right?

Rudy fix for Splashes of Storms and ENB is listed in changelog but not in the "21-Post-Processing" part of the guide. Detailed instructions also yet to be available for FOMOD choices.

Dragons Shout with Voice Update - SSE appear to be mistakenly listed under "13-Gameplay-Immersion" in the guide rather than "07-Sounds and Music" indicated in the changelog.

Snowy Landscapes in Snowy Regions still in the guide despite Vanilla Landscape Corrections?

It took me sometime to realise it, but MO2 hiding the STEP - Conflict Resolution . bsa which contains the grass .gid files aren't enough, but the included .ini file as well needed to be hidden, or else you'll wind up not having grass rendering at all. And probably as important if trying to NGIO generate a grass cache on your own mod list. Led me to a 'd'oh!' moment when I didn't get anything out of my cache generation attempt.

With the update to STEP including the Worldspace Transition Tweak, are there any updates needed to this line of instruction on making paper maps work with STEP Dyndolod?

What of patches for Oakwood and Helarchen, or the other Arthmoor location mods? The older LoS SE MCM doesn't seem to indicate patches for them.

Can someone explain why LoS SE - MCM is suddenly the one preferred to LoS II ?

After upgrading my computer, changing from Windows 7 to 10, I decided that with the likelihood that STEP 3.0 LE (& obviously SSE) likely to be depending on MO2, I decided to prepare to migrate from MO1 to MO2. Looking at https://www.youtube.com/watch?v=utNBS4LflIc ,from the video I'm grateful that it looks to be quite a hassle-free migration from my MO1 folder backup. The real question that pops up is on the issue of dummy plugins that are optional-ed (therefore unchecked), reading up on MO2's description page explains the reasoning, but my concern is does the dummy esps have to be loaded in the same order of their original installation?

Can we have the https://wiki.step-project.com/Dynamic_Distant_Objects_LOD#Recommendations instructions clearly state the steps with the dummy plugins and BSA archive into the numbered list? I don't know what effect forgetting to do all that is but would appreciate the clarity.

Haven't retried Skyrim yet after the defrag and some re-check of the ini's. On the question of my HDDs health, Defraggler doesn't show any trouble (didn't do HD Tune) with any drives. In fact, in the Radeon 280X troubles, my primary HDD (where Skyrim was located) had a SMART failure, but the real culprit was only the graphics card (the HDD theoretically is still functional, though I have removed it from my rig). Chipset drivers have already been updated to the most recent (Imade a format, clean install and updates after the switch from 280X to R9 380). As for memtest, never really checked it out. Currently, I've DDUed AMD drivers to update to the new one (not the hotfixes option), so let's see how it goes.

After a long time with my heavily modded STEP build, chugging along only with ENBoost, I decided to jump into the full ENB world after hearing a hyperbolic MxR review comment on Tetrachromatic ENB. Quickly switching over to Vividian (due to STEP considerations), I also updated my STEP build to reflect new individual STEP mod updates, as well as re-learning Dyndolod as it moves from 1.xx to 2.xx . As I added new mods to my modlist, and TES5Edit checked them, I started out a new game. While all went well, with the rate and occasion of CTDs acceptable to me (if it isn't repeatable in one particular location or frequent action), after a lengthy travel on a Touring Carriages, as I was about to load into Riften [for the first time in that playthrough], after the load screen was finished, I unceremoniously stared at this type of screen (I Googled this example): It was no game freeze that I could Ctrl+Alt+Del out of. It required me to use the reset button, and I had a nervous time when the BIOS at first didn't load up the HDD the first time around. I re-checked my ENB settings for anything that I missed, looking at both Vividian and STEP ENB guides (Steam overlay is now off). I then went to see if loading up Riften was an ENB problem or other mod problem or not, so I decided to coc to Riften Stables and retry again. It loaded Riften up fine. Now, after another run, after playing sometime, the crash came again at Rorikstead despite already being there (as in already loaded). Previously, on my ENBoost-ed game some months ago, I also suffered such a devastating crash on my old AMD Radeon 280X, but it was the card dying out to the level it was only loadable up to Safe Mode (no ATI drivers). Since this is a relatively new R9 380 card (I update drivers by doing the DDU routine), and ENB is the newest graphical addition, I strongly suspect my ENB machinations are not up to par. I tried one runthrough with Shift-F12 disabling the ENB, and had a BlueSOD restart instead when I was fighting a group of Populated Forts bandits (those same bandits were killed with no trouble during the Rorikstead crash that had ENB ON). After that one I decided to Defraggler my HDD (never really got down to this), and have yet to re-play Skyrim. The only thing that I can conclude from the two full system-video freezes is that it takes time to get to that point. I await any advice: My specs: My enblocal.ini: My modlist is 475 long (not all are enabled or plugin-enabled of course).

I noticed something weird when I went from Dyndolod 1.46 to 1.49. Finishing DynDOLOD Worlds, TES5Edit says script done its work, but LODGen hasn't yet finished (the command prompt window is still working). Although I exited TES5Edit and saved the .esp, MO is still locked until LODGEn finishes. Is this okay?

Hmmm. I think I'll pop in to revive this thread to share an opinion on the ELE and Relighting Skyrim inclusion. While it does a good job in making me use Candlelight (I'm not a very magic-prone player) in interior dungeon cells, the unfortunate side effect is that Hjerim (I tried both vanilla and the TNF mod) is in near-pitch black conditions. Although I don't particularly use Hjerim that much, it does seem awkward to find this player home majorly enveloped in darkness. That said I'll stick to ELE and Relighting, until the masters of STEP find or think of something better.