sheson

That save seems to contain data from DynDOLOD output that wasn't made for DynDOLOD DLL NG? Didn't you start a new game with the output made for DynDOLOD DLL NG? The current DynDOLOD.esp does not contain a form ID xx00F9FA (replace xx with the load ID of the DynDOLOD.esp) for example, correct?

Use this test version of DynDOLOD https://mega.nz/file/oIhEQaCZ#d1FvBGM9fFFHqOGHHVTd6X0BaI4TBCpp_Uj6pnklA1M Unpack the DynDOLOD_SSE_completesolitudeesp_tamriel.patch from DynDOLOD_SSE_completesolitudeesp_tamriel.7z into the I:\Mod List Installs\Skyrim\Modding\MO2\LOD Generation Tools\DynDOLOD\Edit Scripts\DynDOLOD\Rules\ directory. Then generate a new LOD patch. That should fix the wrong position of the windmill fan. https://dyndolod.info/Installation-Instructions Use 7-Zip to unpack the entire DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\. Ensure that the directory structure is preserved. See Updating how to update existing installation and save games.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to use the default weather 15e and how to use tcl to get closer to LOD when making screenshots. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting and report/screenshot what happens with LOD turned off in via the console command. You seem to be loading an outdated save that was made with a different version of DynDOLOD output. See https://dyndolod.info/Help/Snow-Ash-LOD-Shader.

Load the entire load order into xEdit and enter the form ID 28A and if it can find that record post a screenshot of it. If you can not find it, upload the save you have been loading.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search how to search the forum for a particular message to find already existing answers. For example, searching for https://stepmodifications.org/forum/search/?q="Property not found in scripts" finds this thread: https://stepmodifications.org/forum/topic/20485-property-not-found-in-scripts See https://dyndolod.info/Messages and https://dyndolod.info/Help/Summary-Of-Messages. See https://dyndolod.info/Messages/Property-Not-Found-In-Scripts, https://dyndolod.info/Messages/LOD-Model-Contains-Controller-Block, https://dyndolod.info/Messages/File-Not-Found-Textures, https://dyndolod.info/Messages/Textures-Do-Not-Match, https://dyndolod.info/Messages/Duplicate-Reference https://dyndolod.info/Messages/Deleted-Reference for explanations and hints for each meassage. For example https://dyndolod.info/Messages/Property-Not-Found-In-Scripts explains: In case the error occurs with paid mods from CreationClub, consider using the Unofficial Skyrim Creation Club Content Patches. If help with a specific message is required, then ask a specific question.

Lets remove the references that use that script to make sure and so they do not clutter up the logs. Make a backup of DynDOLOD.esp. Open it in xEdit and remove these references: DynDOLOD.esp xx02061A DynDOLOD.esp xx01F135 DynDOLOD.esp xx02050C DynDOLOD.esp xx02045B DynDOLOD.esp xx020459 DynDOLOD.esp xx020647 DynDOLOD.esp xx0208B3 DynDOLOD.esp xx0205DB Replace xx with the load order of the DynDOLOD.esp. Enter the form IDs in to the field FormID top left, hit enter. Right click the found record in the left tree view, select remove. Continue testing with that plugin for now.

Moved to the appropriate thread for the message. See posts above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search. https://stepmodifications.org/forum/search/?&q="update.esm might be the wrong version" Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. Use the Copy message to clipboard link in the message to copy and paste the message text instead of a screenshot as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Unresolved FormID 10003165 Update.esm might be the wrong version for Snazzy Black Briar Lodge.esp or vice versa. Click on the Click on this link for additional explanations and help for this message link as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Messages/Unresolved-Form-ID: In case the message mentions that a plugin might be the wrong version, double check it is the correct version for the game version and for any other plugins using it as a master and vice versa. For example, do not use plugins or paid mods from the Creation Club Anniversary Edition with outdated vanilla game plugins from before the Anniversary update (only downgrade the executable of the game, not the plugins). Update the required plugins and use matching versions. Also, after game updates, do not forget to update the cleaned versions of Update.esm, Dawnguard.esm, HearthFires.esm, Dragonborn.esm etc. which might be installed as a mod. For example, patch plugins might need updating in case any of the plugins they are patching changed. For example, when compacting form IDs to convert a plugin to a light plugin (ESL), all other plugins using the converted plugin as a master need to be loaded/updated as well so they are also use the new form IDs. You are using a mod that was made for a newer version of the game plugins. You should update the game plugins to the latest version if you want to use mods that require them.

Shrink ..\textures\DynDOLOD\LOD\DynDOLOD_Tamriel.dds and \textures\DynDOLOD\LOD\DynDOLOD_Tamriel_n.dds If that makes a difference, set MaxTextureSize=8192 in C:\MO2 - SSE\SSEModTools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and generate new output.

Do not test with existing saves. Use coc riverwood from main menu, then enable markers with tmm 1 in console, then fast travel. To test if the size of the object LOD meshes/textures are an issue, hide the meshes\terrain\tamriel\objects\ folder. If that has an affect, unhide the folder, and then test shrining the object LOD texture atlas .dds and n_.dds. You can use https://github.com/microsoft/DirectXTex/wiki/Texconv to shrink textures on the command prompt for example. The problem sounds like it might be related to the ENB dynamic cubemaps. Test disabling that effect. Also make sure ApplyDynamicCubemapEverywhere is not checked.

Also upload the DynDOLOD.log and the papyrus log. Test what happens if you turn off dynamic LOD by deactivating DynDOLOD from its SkyUI MCM before fast travel. Test what happens if you only deactivate DynDOLOD.esp but keep the DynDOLOD.esm. [Tamriel] Creating texture atlas C:\MO2 - SSE\SSEModTools\DynDOLOD\DynDOLOD_Output\textures\DynDOLOD\LOD\DynDOLOD_Tamriel.dds 16384 x 16384 The object LOD texture atlas is 16k x 16k. if above tests did not change anything, test shrinking it and its *_n.dds to 8k x 8k with a texture tool. Meshes\dyndolod\lod\trees\pine_common_big03_summer_9545d40fpassthru_lod.nif used 4310 times, ~ 1005.04 MB Note that the combined object LOD for this one tree alone is 1GB.

No. Continue with what you have. Just remove the script from all possible sources so it is really not in the load order.

Moved to the appropriate thread for the reported problem. See posts above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search See all answers for https://dyndolod.info/FAQ#Entire-LOD-missing. The log shows you are using ACMOS and did not set Level32=1 to generate object LOD level 32. So this is most likely thee cause. Make sure to follow the instructions of ACMOS correctly. Also see https://dyndolod.info/FAQ#Checking-DynDOLOD-plugins-for-errors-with-xEdit I suggest to remove the reported reference 0x3D2354BF. The next Alpha will include an updated configs file for the latest version of LOTD.

You did generate new LOD for this load order right? IN that case upload the new DynDOLOD log and debug log as well. The crash log indicates NGIO-NG.DLL. But just for now lets assume its fine unless the same crash is reported again. Lets try this first based on where we were last: Hide all SHESON_DynDOLOD_ObjectEnabler.pex from both DynDOLOD DLL and DynDOLOD Resources SE in the load order, so the script is not available at all.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which bugreport.txt to upload if it exists and how to enable the realtimelog in case the tool is being terminated prematurely. Also check the Windows Event log for related entries as explained.

That test version is not fully functional. It would be best if for now you continue with the release version. Once there there is an, upload new logs. Then we continue testing with the fully function test version that has the changes based on our earlier troubleshooting.

No logs were provided. The last logs showed that only DLC2SolstheimWorld had an error. <Error: LODGenx64Win.exe failed to generate object LOD for DLC2SolstheimWorld. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_DLC2SolstheimWorld_log.txt> Hence, the instruction to only select DLC2SolstheimWorld and clicking Execute LODGen in expert mode to only rerun that generation again. "LODGenx64.exe generated object LOD for DLC2SolstheimWorld successfully" is the expected result and means that this time the object LOD meshes were generated without error. You can now install the output as usual. Then start DynDOLOD one more time to generate Occlusion.esp only. Uncheck everything else - Object LOD, Ultra and Dynamic LOD, Terrain Underside. Only check Occlusion data and its Plugin checkbox in the advanced or expert mode. https://dyndolod.info/Help/Occlusion-Data#Generation

Test the stability of the PC with prime95 and OCCT. https://prime95.net and https://www.ocbase.com/occt/personal Read https://dyndolod.info/Help/Expert-Mode#Execute-LODGen and https://dyndolod.info/Help/LODGen: To restart LODGen generation for a worldspace in case there is no LODGen_[GAME MODE]_[WORLDSPACE]_log.txt or it does not contain a useful error message, start DynDOLOD in expert mode, select the desired worldspace and click Execute LODGen. Use the expert mode to re-run LODGen for DLC2SolstheimWorld only to generate its object LOD meshes without having to do redo everything else that had no problem. If it runs through without error, then you have complete output for all worldspace. For a test, rename C:\DynDOLOD\Edit Scripts\LODGenx64Win.exe to C:\DynDOLOD\Edit Scripts\LODGenx64Win.bak so that C:\DynDOLOD\Edit Scripts\LODGenx64.exe is used instead. See https://dyndolod.info/Help/LODGen.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which bugreport.txt to upload if it exists. Click on the link Click on this link for additional explanations and help for this message in the message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Messages/Exceptions. https://dyndolod.info/Messages/Exceptions#Access-violation Always use the latest version of DynDOLOD/TexGen as explained above. This could be caused by invalid or corrupt assets. This could be caused by invalid or corrupt plugins. Check the DynDOLOD log for unresolved form ID and Ignoring Cell error messages in particular. Clean and error check the load order with xEdit. Fix all unresolved form ID errors in particular. This could be low or out of memory problems. Check memory usage in Windows Task Manager. Let the OS handle page file / virtual memory automatically. Check FAQ answers for High memory usage. This could be unstable hardware, like CPU, memory, cooling or overclocking etc. This could be caused by the OS or antivir interfering with file access. This can be a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum. Make sure the hardware, especially CPU and memory is stable, for example doublecheck BIOS settings, cooling. Test stability with prime95/OCCT. https://dyndolod.info/Help/LODGen To restart LODGen generation for a worldspace in case there is no LODGen_[GAME MODE]_[WORLDSPACE]_log.txt or it does not contain a useful error message, start DynDOLOD in expert mode, select the desired worldspace and click Execute LODGen. Use the expert mode to only run a single LODGen process for Tamriel to see if that makes a difference.

The debug log shows the settings MaxTextureSize=16384 and MaxLODGen=0 instead of the suggested ones. https://dyndolod.info/Help/LODGen C0000005/80131506 - If happening randomly can be a sign of hardware issues like CPU or memory being unstable. Reduce memory requirements. See Out of Memory below. See FAQ High Memory Usage / Out of Memory. Test hiding LODGenx64Win.exe, so LODGenx64.exe is used instead. Make sure the hardware, especially CPU and memory is stable, for example doublecheck BIOS settings, cooling. Test with prime95/OCCT. https://dyndolod.info/Help/LODGen To restart LODGen generation for a worldspace in case there is no LODGen_[GAME MODE]_[WORLDSPACE]_log.txt or it does not contain a useful error message, start DynDOLOD in expert mode, select the desired worldspace and click Execute LODGen. Use the expert mode to only run a single LODGen process for Tamriel to see if that makes a difference.

The crown brightness increase of the vertex colors caused a byte overflow because a float to byte conversion was not properly clamped at 1.0. Simplified, an ("illegal") vertex color value of 1.1 was stored as 0.1 instead of 1.0.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log to also upload when making posts. Neither the LODGen log for Tamriel nor Solstheim were uploaded. As the message suggest, check them for hints. They probably just stop in the middle of things. It is not clear what it is you have been trying for several days. https://dyndolod.info/Help/LODGen C0000005/80131506 - If happening randomly can be a sign of hardware issues like CPU or memory being unstable. Reduce memory requirements. See Out of Memory below. See FAQ High Memory Usage / Out of Memory. The DynDOLOD debug log shows that not all suggest settings from the LODGen out of memory section and FAQ answers are applied: For example: MaxTextureSize=8192, MaxLODGen=1 Test hiding LODGenx64Win.exe, so LODGenx64.exe is used instead. Make sure the hardware, especially CPU and memory is stable, for example doublecheck BIOS settings, cooling. Test with prime95/OCCT. https://dyndolod.info/Help/LODGen To restart LODGen generation for a worldspace in case there is no LODGen_[GAME MODE]_[WORLDSPACE]_log.txt or it does not contain a useful error message, start DynDOLOD in expert mode, select the desired worldspace and click Execute LODGen. Use the expert mode as explained to simply run LODGen for Tamriel only to see if that runs through.

Great. Thanks for letting us know.

Moved to an appropriate thread for the problem. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search and posts above. Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD debug log to also upload when making posts. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Do not post screenshots of the tools, unless it is about visual issues with the user interface. If necessary, convey the information in text form. The debug log as explained below typically contains most of the selected settings and options already. What are the screenshots showing, that you haven't already explained in text? Read the message under the box. If click the the Help as it tells you to, it opens https://dyndolod.info/Help/Wizard-Mode. Read everything under "Select Worldspaces" See answers for https://dyndolod.info/FAQ#Not-seeing-all-worldspaces-in-the-selection-box

If you want to be extra sure, you could also add like your/mod initials to the filename. In particular when you use something common like 'fall' or 'snow'. Try to do a cross check with other mods - the game typically does not use a _ separator but of course check with it, too. In that case no CRC32 is needed, since filename collisions are very unlikely.

If you use a mod that changes the mountain full textures like moutainslab01.dds and mountainslab02.dds, then the mod should also contain updated LOD textures to replace the vanilla rendered object LOD textures like Mtn*LOD.dds used by the far away mountain LOD models. TexGen can not update them yet.