DynDOLOD 3.00 Alpha 190

[sheson]

  On 2/25/2023 at 4:19 PM, AutumnFox94 said:

Hello! I am trying DynDOLOD for the first time for a few season mods that I want to add to my Skyrim SE mod list. I've watched the step-by-step videos, and installed everything correctly (to my knowledge) and I am getting a lot of Warning messages when I run DynDOLOD. I don't when running TexGen, which make my think I'm doing something wrong... The warning messages are for different mods that I have installed and all start with "Overwritten large reference in [name of mod]". Is this normal or am I doing something wrong? It's all mods that add new textures to the game, but I want to make sure I'm running this correctly so I don't super mess up my mod list. 

 

Any advice would be much appreciated!

Expand  

Moved to the DynDOLOD 3 Alpha thread. Read the first post which log and debug log to upload when making posts.

Check https://dyndolod.info/Messages for the explanations of log messages, warning and errors and the severity and if they require action. For example https://dyndolod.info/Messages/Overwritten-Large-Reference

Check the summary (..\DynDOLOD\Summary\DynDOLOD_Index.html) which consolidates many of the same log messages into an easier to browse format with the explanations. https://dyndolod.info/Help/Summary-Of-Messages

The well known large reference bugs caused by plugins are explained at https://dyndolod.info/Help/Large-References, including explanations for mod authors how to make plugins that do not cause the bugs (ignored by some mod authors for over half a decade) and a link to the experimental workarounds https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

If further explanations for a problem or how to solve them are needed, ask specific questions and provide the logs as explained in the first post.

[ethqnm]

  On 2/25/2023 at 7:55 AM, sheson said:

You installed the Majestic Mountains DynDOLOD V3.0 LOD Pack (all versions), right? Are any of them being overwritten by other mods?

Expand  

That works but it's a band-aid fix for I'm trying to do. I have some of the meshes painted white (R=1,B=1,G=1) but DynDOLOD appears to delete them with the generated .btos, which throws out the vertex color alphas as well.

[floskan]

  On 2/25/2023 at 3:57 PM, sheson said:

It should be using FlatWhite01_d.DDS instead. Will be fixed next version.

Expand  

Thank you!

[sheson]

  On 2/25/2023 at 6:04 PM, ethqnm said:

That works but it's a band-aid fix for I'm trying to do. I have some of the meshes painted white (R=1,B=1,G=1) but DynDOLOD appears to delete them with the generated .btos, which throws out the vertex color alphas as well.

Expand  

Why is using the LOD models included in the Majestic Mountains DynDOLOD V3.0 LOD Pack (all versions) a band-aid fix? Why are they being overwritten or changed? There is something you are not telling us.

If the vertex RGB colors of a combined supermesh are all > 0.9 they are optimized away by LODGen. So far regardless of alpha channel values, since LOD models using the HD snow/ash shader always have vertex colors with at least one color channel less than 0.9.

[tugsthen]

Howdy, I use DynDOLOD for a long time and never had any issues, yesterday I've changed my combination of textures (Replaced many with Parallax versions) and generated a new output from DynDOLOD, since then all games saved with this new output causes a crash on loading the save. Here is the crash log (It has the call stack and load order afterwards):

https://pastebin.com/y44VhsTQ

It is a very strange issue, because I can load or start any games without a problem, the LODS are working amazingly, and even if I make the save inside a small cell where there are no LODs, I still get the crash issue when loading it. When I turn off my new DynDOLOD output, I can save and reload without an issue.

The new output was generated using the exact same parameters as my previous output.

[sheson]

  On 2/25/2023 at 8:19 PM, tugsthen said:

Howdy, I use DynDOLOD for a long time and never had any issues, yesterday I've changed my combination of textures (Replaced many with Parallax versions) and generated a new output from DynDOLOD, since then all games saved with this new output causes a crash on loading the save. Here is the crash log (It has the call stack and load order afterwards):

https://pastebin.com/y44VhsTQ

It is a very strange issue, because I can load or start any games without a problem, the LODS are working amazingly, and even if I make the save inside a small cell where there are no LODs, I still get the crash issue when loading it. When I turn off my new DynDOLOD output, I can save and reload without an issue.

The new output was generated using the exact same parameters as my previous output.

Expand  

Read the first post which log and debug log to upload when making posts.

There might be a problem with MuJointFix.dll from Mu Joint Fix (Knee Fix dll edition). Test without the mod/dll/esp.

https://dyndolod.info/FAQ "ILS or CTD"
If there are problems loading saves, make sure the clean save procedure was followed correctly when updating from scratch.

Make a clean save as explained at https://dyndolod.info/Help/Clean-Save and https://dyndolod.info/Updating

[tugsthen]

Thanks for your answer Sheson, doing a clean save solved the issue for me. It just didn't come to mind, since I never had to do a clean save to update my DynDOLOD output, even when I used to use open cities.

Have a great weekend

[DannyDeVito]

  On 2/24/2023 at 9:14 PM, sheson said:

It is pointless purposefully wasting time making posts that are obviously useless.

Expand  

You're right. But taking Texgen over 1 hr instead of 5 mins couldn't be a Texgen problem. The logs where all good. I found the issue: the AMD GPU driver. I reverted back to version 22.5.2 and Texgen was fast again.

Maybe this helps someone else with the same problem.

Edited February 25, 2023 by DannyDeVito

[sheson]

  On 2/25/2023 at 9:27 PM, DannyDeVito said:

You're right. But taking Texgen over 1 hr instead of 5 mins couldn't be a Texgen problem. The logs where all good. I found the issue: the AMD GPU driver. I reverted back to version 22.5.2 and Texgen was fast again.

Maybe this helps anyone else with the same problem.

Expand  

Read the first post which log and debug log to upload when making posts.

The debug log contains the graphics card driver information.
We already know since a very long time that newer drivers with rewritten OpenGL support can be problematic. Using older drivers is a troubleshooting step and not a fix.
You are purposefully withholding logs that could help with this being looked into, analysed, despite several requests. 

[ethqnm]

  On 2/25/2023 at 7:50 PM, sheson said:

Why is using the LOD models included in the Majestic Mountains DynDOLOD V3.0 LOD Pack (all versions) a band-aid fix? Why are they being overwritten or changed? There is something you are not telling us.

If the vertex RGB colors of a combined supermesh are all > 0.9 they are optimized away by LODGen. So far regardless of alpha channel values, since LOD models using the HD snow/ash shader always have vertex colors with at least one color channel less than 0.9.

Expand  

That explains it. Thanks!

I'm trying to remove the fake ambient occlusion effect on some of the mountain LOD meshes because they can sometimes look out of place with my setup.

[Rakz]

  On 2/24/2023 at 7:54 AM, sheson said:

Check the Windows Event log for related entries.

Add RealTimeLog=1 under [TexGen] to ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI run again and upload that log.

Expand  

Hi,

I tried what you asked:

• No logs in Event Viewer related to TexGen
• Managed to get a successful run with version 118
• Then, TexGen started closing again without apparent reason (real time logs attached).

Thanks!

TexGen_SSE_realtime_log-BaseSize256-HDTreeDisabled.txtFetching info...

[sheson]

  On 2/27/2023 at 12:05 AM, Rakz said:

Hi,

I tried what you asked:

• No logs in Event Viewer related to TexGen
• Managed to get a successful run with version 118
• Then, TexGen started closing again without apparent reason (real time logs attached).

Thanks!

TexGen_SSE_realtime_log-BaseSize256-HDTreeDisabled.txt 2.19 MB · 0 downloads

Expand  

If there are no normal log, debug log written it means TexGen is being terminated without going through its exception handler and shutdown procedures.

If there is really no Windows Event log, look into things like hardware trouble, for example CPU overclocking/cooling, BIOS settings, memory timings etc. 

See what happens by adding TextureCache=10 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI
Then test what happens setting RenderThreads=1

[heheloveer]

I'm not sure if this is the right place to ask this, but why does the complex grass billboard (that is, the DynDOLOD_flat_4x2alt_lod.nif file) need to have a Back_Lighting flag? I noticed in my Skyrim the color seam between full grass and grass lods wasn't too prominent during daytime and nighttime, but when it's dawn or dusk some parts of the grass lods lit up like crazy while the full grass nearby are all dark. I later found out it's because both sides of the grass lods lit up when the sunlight was coming from one side. If you look towards the direction the sun is facing, full grass and grass lods would all light up and color seam would be minimal, but when you look towards the sun only the grass lods would light up. This resulted in a massive color difference and the effect in itself was also quite jarring to see. I experimented a little with DynDOLOD_flat_4x2alt_lod.nif and found out removing the Back_Lighting flag from the mesh makes complex grass lods generated with it react to sunlight normally. I'm not a Nifskope expert and there's always a possibility that only I encountered this strange phenomenon, so I came here to ask. FYI, I use Qw's Grass Patch (and its complex grass retexture, of course), Rudy Cathedral Zangdar ENB preset and EVLAS. Both DynDOLOD and ENB are at their latest versions.

[sheson]

  On 3/1/2023 at 2:49 PM, heheloveer said:

I'm not sure if this is the right place to ask this, but why does the complex grass billboard (that is, the DynDOLOD_flat_4x2alt_lod.nif file) need to have a Back_Lighting flag? I noticed in my Skyrim the color seam between full grass and grass lods wasn't too prominent during daytime and nighttime, but when it's dawn or dusk some parts of the grass lods lit up like crazy while the full grass nearby are all dark. I later found out it's because both sides of the grass lods lit up when the sunlight was coming from one side. If you look towards the direction the sun is facing, full grass and grass lods would all light up and color seam would be minimal, but when you look towards the sun only the grass lods would light up. This resulted in a massive color difference and the effect in itself was also quite jarring to see. I experimented a little with DynDOLOD_flat_4x2alt_lod.nif and found out removing the Back_Lighting flag from the mesh makes complex grass lods generated with it react to sunlight normally. I'm not a Nifskope expert and there's always a possibility that only I encountered this strange phenomenon, so I came here to ask. FYI, I use Qw's Grass Patch (and its complex grass retexture, of course), Rudy Cathedral Zangdar ENB preset and EVLAS. Both DynDOLOD and ENB are at their latest versions.

Expand  

The complex grass shader in ENB makes full grass be lit from both sides by flipping its normal vector (or something similar to that effect). The backlight flag mimics that behavior.

Either you do not have complex grass effect enabled or the way it works changed in newer ENB versions or maybe it has to do with the full grass models being different than the vanilla full grass models.

The defaults are for Vanilla complex grass for ENB grass LOD test:

[heheloveer]

  On 3/1/2023 at 3:08 PM, sheson said:

The complex grass shader in ENB makes full grass be lit from both sides by flipping its normal vector (or something similar to that effect). The backlight flag mimics that behavior.

Either you do not have complex grass effect enabled or the way it works changed in newer ENB versions.

Expand  

I'm sure I have complex grass effect enabled in ENB, have installed complex grass textures and have used DynDOLOD_flat_4x2alt_lod.nif as grass billboard, though it will have to wait for some time before I can produce some before/after screenshots to prove my claim. Do you plan to verify this yourself at some point?

Edit: I see you uploaded a video and if that's a full day-night cycle the vanilla grass lod does seem to behave normally. Indeed, it probably have something to do with the grass mod I'm using. Would you look further into this problem? Many people use modded grass so I think they could use some official support regarding this matter.

Edited March 1, 2023 by heheloveer