DynDOLOD 3.00 Alpha 182

[floskan]

The latest version of texgen gives me an error telling me that a texture is missing from a completely vanilla Fallout 4 installation, while it works perfectly with earlier versions.

TexGen_FO4_log.txt

TexGen_FO4_Debug_log.txt

Edited February 25, 2023 by floskan

[sheson]

2 hours ago, mrshadoo said:

sorry I missed those out ! https://www.mediafire.com/file/vasqn3kim3kku1y/LODS.rar/file

Everything looks in order with the ultra tree LOD generation.
Double check the generated object LOD meshes in \Meshes\Terrain\Falskaar\Objects\*.bto from the DynDOLOD output are installed, active and not being overwritten by anything else.

[sheson]

2 hours ago, floskan said:

The latest version of texgen gives me an error telling me that a texture is missing from a completely vanilla Fallout 4 installation, while it works perfectly with earlier versions.

TexGen_FO4_log.txt 7.47 kB · 2 downloads

TexGen_FO4_Debug_log.txt 25.7 kB · 0 downloads

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

[AutumnFox94]

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!

[sheson]

58 minutes ago, 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!

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]

10 hours ago, sheson said:

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

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]

2 hours ago, sheson said:

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

Thank you!

[sheson]

2 hours ago, 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.

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]

32 minutes ago, 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.

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.

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]

26 minutes ago, 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.

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]

3 hours ago, 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.

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 2: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.

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