sheson

No log was provided, so assuming xLODGen was setup as explained in the first post and there were no errors. If it goes away when unchecking Bake normal maps, then it is because of bad full landscape normal map textures, like the *_n.dds is not actually a normal map. If it still happens with Bake normal maps unchecked it happens because of bad normal vector data on the LAND record. Next troubleshooting step depends on which it is. A reply should include the log and the information / image of a terrain LOD normal texture generated without Bake normal map option checked so the next troubleshooting step can be determined.

No log was provided, so assuming xLODGen was setup as explained in the first post and there were no errors. If it goes away when unchecking Bake normal maps, then it is because of bad full landscape normal map textures, like the *_n.dds is not actually a normal map. If it still happens with Bake normal maps unchecked it happens because of bad normal vector data on the LAND record. Next troubleshooting step depends on which it is.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log and debug log to upload when making posts. As explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages, read the entire message. It tells you what the problem is and also its solution: Make sure to install the latest DynDOLOD Standalone with the latest matching DynDOLOD Resources SE archive. As explained, make use of the "Click on this link for additional explanations and help for this message" to open https://dyndolod.info/Help/DynDOLOD-Resources for further help and explanations: See Downloads where to acquire the installation archives.

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.

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

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.

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.

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

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.

Read the first post which debug log to also upload when making posts. Also upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt and ..\DynDOLOD\Logs\DynDOLOD_SSE_Tree_Report.txt Also upload ..\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Export_Falskaar.txt

Read the first post which log and debug log to upload when making posts. Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make screenshots with useful information in them. https://dyndolod.info/FAQ "Out of place or floating objects" Wild edit added by a plugin. Get the plugin and reference form ID via the console in the game. Check the DynDOLOD log messages for Potentially wild edit reference with z = 0.0. Look up the form id in xEdit and remove the reference, clean the plugin afterwards. Notify mod author. If the reference is added by a DynDOLOD plugin, follow the "pluginname_formid" information found in the Editor ID of the reference to find the plugin from which this reference originates. Check the log messages for deleted references. Check plugins for errors and clean them from ITMs or deleted references. See xEdit Cleaning and Error Checking. https://dyndolod.info/Messages/Potentially-Wild-Edit-Reference https://dyndolod.info/Messages/Deleted-Reference

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

It is pointless purposefully wasting time making posts that are obviously useless. TexGen 3.0 Alpha-113 x64 - Skyrim Special Edition (SSE) (F8D47B7F) starting session 2023-02-24 22:07:54 [01:27] TexGen completed successfully TexGen 3.0 Alpha-114 x64 - Skyrim Special Edition (SSE) (1BD4AE29) starting session 2023-02-24 22:09:45 [01:18] TexGen completed successfully TexGen 3.0 Alpha-115 x64 - Skyrim Special Edition (SSE) (35D30621) starting session 2023-02-24 22:11:34 [01:19] TexGen completed successfully TexGen 3.0 Alpha-116 x64 - Skyrim Special Edition (SSE) (7D51D698) starting session 2023-02-24 22:13:16 [01:18] TexGen completed successfully TexGen 3.0 Alpha-117 x64 - Skyrim Special Edition (SSE) (2FF632C9) starting session 2023-02-24 22:16:45 [01:18] TexGen completed successfully

Read the first post which log, debug and bugreport.txt (if it exists) to upload when making posts.

Read the first post which log and debug log to upload when making posts. Doublecheck you are really starting DynDOLOD 3 Alpha-116.

Read the first post which log and debug to upload when making posts. Also enable papyrus logging and upload that log. Test with a new game.

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.

Read the first post which log and debug log to upload when making posts. https://dyndolod.info/FAQ Long running time or output several GB in file size The selected configuration options together with the installed mods and assets can require a lot of work. Use sensible settings. Crapware installed with graphics drivers is known to prolong running times. Install only the drivers and not any of the bloatware.

That is great! Thanks for all the testing.

Great. Make the INI default (from Alpha-115) and use this test version https://mega.nz/file/hUBFGD5C#UKoDN3CpIPDrmojYmp8zqn8WLu9VmsFs9FPF4EuFQMg if it also runs through, it should be fixed for good.

Let me know what happens with this test version https://mega.nz/file/AdhjTJhJ#1FFvo5cPHoHgbY3g5IGbgPtnyfEyUAxQTzCZ7JL6-lY

These crashes seem to be all over the place. Check for CPU / main memory problems from overclocking, some kind of boost for example.

Thanks. Can you also do one with MaxTextureIndex=4?

Add MaxTextureIndex=10 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and see if it breaks again. If it does, also test what happens with MaxTextureIndex=2

See what happens with this test version https://mega.nz/file/sQBEQYiA#4x0xGGPisn1rLJNaiHV005p9qWbGl2ZyuXIFSto-P_Q