z929669
-
Posts
13,028 -
Joined
-
Last visited
Everything posted by z929669
-
Can You Mod With MO2 With SSE From GOG?
z929669 replied to mooit's question in Mod Organizer Support
MO2 can mod against GOG. -
Here's the gist on bake specular:
-
ENB is graphical post-processing, so it has no impact on the mod build or LOD other than performance. If you have a 4k setup, chances are you have a fairly powerful PC that can handle it.
-
What you are seeing is an artifact of having a true 4k setup. Does the issue go away when you disable ENB (Shift+F12)? If memory serves, I had this issue with snowy grasses and resolved by making the following changes under [ENVIRONMENT] in enbseries.ini: SamplingQuality=0 UseComplexAmbientOcclusion=true EnableComplexFilter=true Let us know what you find.
-
Try toggling sky via console ( ` ts `) off and back on again.
-
Moved to DynDOLOD support, as it's likely an issue with NAT-ENB.esp (core issue) that is in turn associated with the LOD patch. I assume you generated DynDOLOD after properly sorting your LO and including NAT-ENB.esp. Provide all of those DynDOLOD logs for analysis.
-
It's very likely a mod that modifies a CW dependency or overrides a CW weather or image space record. I'll wager that if you disable all additional mods aside from those in the Step guide and test on a new game, you will not be able to reproduce your issue. Then at least you will know that it's an interaction/conflict with a mod you have added, which might help you to resolve the problem.
-
It's likely one of the other mods you installed over the guide. Check for something that replaces sky meshes. Maybe some volumetric fog mod. We only support the Step guide and associated mods, because that's what is in our dev installations. Additional mods add new variables into the mix.
-
Those two shots are taken from different vantages. See what happens when you disable EVLaS.
-
You need to have a consistent weather system when testing LOD. If you are running Step, install all the mods, including CW.
-
Yes, make sure you set everything as described in both links. I assume you are running the 2.3 guide, so be sure you have all the correct mods installed and plugins activated/sorted. If you are using ENB, then settings are different. Regenerate TexGen into TexGen-2.4 Output. Enable it, and then generate DynDOLOD per the instructions noting all details into DynDOLOD-2.4 Output. If you want to test lower TexGen 'Ambient' settings for grass (with ENB-CG, Direct should be zero), or lower DynDOLOD grass brightness, you can regenerate TexGen and DynDOLOD into different-named outputs. If you generate Occlusion with 'Plugin' option as recommended, keep it in a separate output mod to be reused with any of the different TexGen/DynDOLOD outputs. As long as LO hasn't changed, Occlusion won't change either. Occlusion is really not even necessary when testing LOD anyway. Complex grass will never match full grass everywhere at all ToD, so focus on the tundra or any other areas where you see a lot of LOD grass in the distance to find the best compromise for most weathers and times.
-
The TexGen Direct/Ambient is likely too high. Try using the DynDOLOD settings recommended in the upcoming 2.4 guide (still in development).
-
\ is the fallback for objects not matched above. You should not modify this. It's set by DynDOLOD or ACMoS (LOD32 is the map) if you follow the procedure in the image.
-
Moving the mod via MO left pane isn't necessary. You should not see this warning at all. Revising installation instructions for Simple Children and TK Children. You may not be hiding all the files or maybe using the wrong version of one of these.
-
Are you using ENB? If so, try Shift+F12 to disable it and see if it goes away. If you use a sky mesh replacer or 'fog' mod, you could try disabling those.
-
Outfit colors washed out outdoors with ENB
z929669 replied to TomForStep's topic in General Skyrim SE Discussion & Support
Yes, it can be fixed. It's likely related to the shaders on those outfits and weather-ENB interaction. Post on the ENB Discord for quick advice, or ask Rudy et. al. on his mod page. -
Test if our new settings recommendations fix this. Regen TexGen/DynDOLOD. If you still have issues, then it's likely your visual distance settings.
-
Instead of disabling FaECL, try installing the Enhanced Lights and FX Patch from that mod. Let us know if it resolves you issues.
-
Repeat your DynDOLOD generation with CL enabled. Change values of TexGen Direct/Ambient to change the brightness. Try the 2.4 dev guide rendition of these setting recommendations for improved fidelity.
-
In the Performance Examples table, it says to change the 'tree' mesh rule accordingly for each of the performance options. The DynDOLOD GUI images show the 'Optimal' mesh rule settings for 'tree' and '/' as mentioned in the corresponding yellow text. Also, the GUI image shows 'plugin' ticked in the Occlusion settings, which generates that plugin separate from the others. Just move it into a different mod adjacent to the rest of the DynDOLOD outputs. Untick "Occlusion data" box for subsequent generations to avoid regenerating it again redundantly.
-
The updated BethINI Pie GUI is represented in the SkyrimSE:2.4 dev guide. We haven't moved it into the 2.3 guide yet. I've added instruction to use 0.4 of More Lights for ENB - Blood Spatter Fix for now. The mod name in our mod list is identical to the Nexus. The user can always choose a name for a mod being installed if it's not consistent with the name of the mod. Brightness/darkness is subjective and largely dependent upon system hardware/software. We've made all the adjustments in ENB to raise brightness a bit, so it's up to each user to tweak their system to make changes if it's too dark/bright for their taste. Use the latest Step ENB to get the most updated results.
-
If you are using the crash log we recommend in the guide list, it's not the issue. It should output a full crash log. Check the next time you CTD.
-
Some issues not addressed by the guide
z929669 replied to Whitestar127's topic in Step Skyrim SE Guide
Not sure about #1. It sounds like you are a lefty. Did you try customizing the key bindings in the game options? Swap J for A for example. You can use ` set timescale to 1 ` in the console (not sure if you can set to 0). This freezes time. Not sure what ` tfc 1 ` does. ` tfc ` toggles the flying camera. -
If you are getting CTDs, it seems like it's a bug related to a quest or quest item, since it never happened previously and suddenly it does. Either that, or you have an artifact in your save. A full crashlog would possibly help diagnose.
-
The MO dev team likely fixed the issue. I will need to test to confirm. TBD
