z929669

All the info is there. Click the link in the error for detailed instructions or simply remove that plugin, since it is redundant it seems.

Nice. I had submitted a bur report for them on this, and it looks like the implemented this fix.

I am interested. If you can, please create mod topics using the change tool in the editor, and I will tag them later when I have time. I'm very interested in picking up these NG mods as alternatives to enhance future compatibility of game/runtime mods and to speed up resolution of updates with game versions. Hope to see even more of these.

Agree. You will usually want to forward conflicting lighting records where a plugin you are patching is forwarding a corresponding vanilla lighting record.

Thanks. Please use the editor tool to create mod topics:

Load all plugins(including Step patches), and look at Torch Arrows and Bolts in xEdit to see what it conflicts with and forward changes you want into your own patch. You will need to merge some things (like patches) if you are hitting the plugin limit. Do it manually though and then disable plugins that you merge.

Some of the problems seem to be terrain (ground and paths/roads look wrong). Redo terrain LOD, and make sure to enable terrain LOD mods while doing so and disable when finished. What landscape mod(s) are you using?

The Steam instructions indicate to install Steam outside of UAC-controlled paths. C:\Games is a suggestion for game paths. It's independent of C:\Modding\* ... which is also a suggestion for modding-related paths. The point is that the path doesn't matter as long as it's organized and intuitive. Edit:I removed the reference to 'above', which is probably why you are asking.

I posted this one in hopes that others running Step would do the same to validate. It should be a drop-in replacement for the original, and we will be moving to this version next guide update (barring anything unexpected turns up in testing the drop-in replacement)

Make sure all of your runtime mods (SKSE and SKSE-dependent mods) are updated to correct version for the game version you are running, and disable those that are not.

That's for terrain LODGen only. Enable this mod only when generating terrain and disable when finished with that. Nothing to do with DynDOLOD. Note that if you use Worldspace Transition Tweaks, the tamriel terrain resource mod is redundant and not needed. WTT remains active during and after terrain LODGen. PS: I just know some stuff and am not the expert. sheson's advice overrides mine where they conflict.

Any number of things can change output size, so if your mod install order and plugin LO change, this can change. If those things aren't changed, then it's likely your mesh rules changed. Find ideal DynDOLOD mesh rules and save those settings to prevent unexpected diffs between runs (mistakes clicking worldpaces, buttons, checkboxes, etc.). We (Step, not necessarily sheson) recommend the following mod install order (not plugin LO): USSEP Particle Patch DynDOLOD Resources Mesh improvement mods LOD resource mods ... xLODGen output TexGen output DynDOLOD output TexGen and DynDOLOD logs tell you if errors, but you can load up any of the BTO meshes in NifSkope (in DynDOLOD output /meshes/terrain/{worldspace}/objects) and look directly at the tree components.

CommonLib is exciting. I wonder if NGIO and other relevant mods could/will switch to this.

Discussion topic: Yes Im Sure NG by VersuchDrei Wiki Link Alternative to Yes Im Sure, since that MA is combative about updating his mods. I'd like to see more of these alternatives.

Weather lighting has similar impact relative to Direct/Ambient, but these settings DO impact grass brightness/detail (independently of complexgrass top/bottom settings in DynDOLOD_SSE.ini). As I mentioned, we have suggestions for all of these settings earlier in this topic or in the Step guide I linked. It's trial and error, so establish a baseline (defaults for TexGen and DynDOLOD_SSE.ini or the settings we recommend specifically for CL complex grass). Save this output as a 'baseline' mod. Then make singular changes to any one setting (suggest changing Direct OR Ambient in TexGen by +/- 50 OR top/bottom brightness in DynDOLOD_SSE.ini by +/- 0.25 in order to see obvious impact). Save as "{setting change}" mod. Then get screen compares from a several save games with good viewing angles (PoV north or south suggested so view angle is perpendicular to path of sun) of grass in various locations and at varying ToD (suggest getting dawn/dusk/noon). Once you find the diffs that seem to be in the direction needed, use that info to produce new outputs/screens. It's not unusual to produce upwards of 10 TexGen/DynDOLOD outputs before finding your ideal settings, but establishing a 'good' baseline and incremental changes algorithm to zero in on ideal can drastically minimize how many outputs are needed. Also keep in mind that ENB-CG settings also impact all of this (FakeLight should be 0.0 or very low for all ToD, and SSS should be around 0.3-0.8 for all ToD ... you can set these to different ToD values once DynDOLOD settings are optimized). Obviously, this takes time, patience, and a methodical approach. My approach is to set all DynDOLOD_SSE.ini to identical values for all Top/Bottom brightness (0.5). This allows LOD grass to use native, unbiased tint for a baseline, so if tint/hue problems are present, you know it's ENB or weather lighting causing it and not DynDOLOD settings or textures.

Testing LOD changes means regenerating LOD --all LOD or using what algorithms are mentioned for specific parts. Either way, it takes time to prepare the LOD. I usually generate my LOD output for compares into separate mods and load each independently for screens. This works fine, since the DynDOLOD plugins are identical with iterative LODGen runs. There is no fast way to do it like with changing ENB or game settings. We regen LOD many times for testing in such situations.

Try setting UseOriginalPostProcessing=false in enbseries.ini. Then set in: \Steam\steamapps\common\Skyrim Special Edition\enbseries\enbeffect.fx.ini Test things in the GUI in game to see how things work ... it's quite complex to get things looking right, but lots of the more complex ENBs (e.g., Truth) configure ENB this way to open up another universe of configuration options. We don't do it, because we want to retain the vanilla colors and image space lighting (and it very complicated as I mentioned with many more additional degrees of freedom).

\Steam\steamapps\common\Skyrim Special Edition\enbseries\enbeffect.fx.ini

You can try settings for TexGen and DynDOLOD_SSE.ini in a post I made earlier in this topic or the DynDOLOD settings in the Step Guide. As sheson mentions, it's trial and error. The settings in the guide work well for Cathedral, but may or may not get you close for your grass mods/weathers/ENB.

Looks like there is no dependency on skse_steam_loader.dll is all, so no difference to the end user AFAIK. On upgrade, you should remove this file from previous version.

See the forum rules and OP for how to post and what to include. It isn't useful to paste large amounts of text into a post.

It sounds like an xLODGen error during initialization. What terrain mod are you running?

Hash won't work either for same reason. Additionally, hash has special meaning to the wiki parser. I think the current format should be fine for copy/paste now. It only applies to the sampe config file (best practice to avoid overwriting configs on mod updates).

The spaces in the example config are removed where comments don't exist. The semicolon is screwing with the wiki parser when at start of line.