sheson

Run this test version and upload new logs https://mega.nz/file/MdoURCqY#RnWafgx8ToZvqArPuNApIovT_MKe2xwcda6iY-ZUh8A What mod are the grass full models like ..\Meshes\landscape\grass\reachgrassobj01.nif from?

Test if it works if you move DynDOLOD to a path that does not have non-alphanumeric characters, like E:\Mods\DynDOLOD\ for example.

Check what happens with this test version https://mega.nz/file/pAoX0TjD#td7VDPGKxts2kpLCmOvPVChGScDq1oKMWeJO29gEiko Delete old logs first again. If problem persists, run eat least twice to verify the error is exactly the same or not.

Check what happens with this test version https://mega.nz/file/YNxmQKID#VAuMFuBJEvE1J97LuPsb9DV-H11EYeonpcWdO5zdG3k Delete old bugreport.txt and logs before running the test version and upload new ones if there is still an issue.

Moved to the appropriate thread. Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. Copying the short message text into the message, allows searching for it. [Main Instruction] Unresolved FormID [FE04B096] [Content] Laundry.esp might be the wrong version. Error in JKs Markarth Outskirts - Immersive Laundry patch.esp [REFR:FE04BEBD] (places [FE04B096] <Error: Could not be resolved 1 >NAME - Base in GRUP Cell Persistent Children of [CELL:00000D74] (in Tamriel "Skyrim" [WRLD:0000003C]) at -41,0) Click on this link for additional explanations and help for this message https://dyndolod.info/Messages/Unresolved-Form-ID Unresolved Form ID errors signify records that try to use non-existing records in the same or master plugins. ... Clean and error check the load order with xEdit to find and fix unresolved form ID errors before generating LOD. ... Check the load order for errors with xEdit before generating LOD. Fix all errors. See this video for help (ignore the old cleaning instructions as that was already done). Following proper modding practice and error checking with xEdit finds and fixes unresolved Form ID errors long before using tools that require an error free load order. Fixing these errors in the load order means a more stable and better working game and mods. As explained, cleaning and error checking are two different things. 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, 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. The original Laundry.esp is a full plugin and not a light plugin. So this probably means something went wrong when it was converted to a light plugin.

https://dyndolod.info Participating in the alpha test requires to report any problems to the official DynDOLOD support forum. Too bad the request to upload the DynDOLOD log and debug log was ignored as it could have help to figure out why some systems do not open HTML links and maybe make the tools more resilient and it could have helped to being able to replicate the problem to improve the message and error handling. It is too late now that the logs have been replaced. At least it might be possible to still report/link the the mod in question how it happened that a plugin had such errors.

Read the first post and//or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts. Use the Copy message to clipboard and paste the message as text instead of making a screenshot as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text

I have no idea yet how that happened, hence the request for the screenshot so I can try to replicate. Replacing the esp with an empty dummy plugin, then error checking in xEdit for any unresolved form ID errors. I suggest to pay some attention to the warning and error messages and read their explanations and address some of the issues.

It means there is a line with the same key. Keys for things need to be unique. If help is required, properly report the problem by providing common sense information, like logs, screenshots, load order etc.

Load the entire load order pre DynDOLOD generation (e.g. without the DynDOLOD output enabled) into xEdit. Enter the form ID 00009ABE into the FormID field top left and press Enter to load up the cell record. Upload screenshot(s) that show the entire record from left to right and top to bottom (does not show the entirely empty rows at the bottom). You can then load DynDOLOD.esm into xEdit and just delete that cell from it, clean masters and it and everything should work.

The link asks me to login. Also upload the DynDOLOD debug log as explained in the first post and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

The latest release version of DynDOLOD DLL NG is Alpha-31. Always use the latest version. Install Crash logger. Disable the Framework crash log by setting Debug.CrashLog.Enabled = 0 in NetScriptFramework.config.txt. If the problem persists with Alpha-31 or the test version, upload new crash logger log. In the DynDOLOD output edit ..\skse\plugins\DynDOLOD_Data\DynDOLOD_NG_Worlds.txt and set debug=true Upload c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\DynDOLOD.log

Moved to the DynDOLOD DLL thread. https://dyndolod.info Always use the latest versions. ... Using the latest version and providing feedback or reporting problems is a requirement to participate in the alpha test. ... Participating in the alpha test requires to report any problems to the official DynDOLOD support forum. I suggest to ignore useless posts on reddit from people that do not troubleshoot and do not report the issue and then use DynDOLOD DLL SE instead of DynDOLOD DLL NG to simply ignore the issue. This is not how things are solved and done. The crash log seems to indicate an issue with animation, OpenAnimationReplacer.dll, maybe TrueDirectionalMovement.dll and the PlayerCharacter. The crash log only lists that a DynDOLOD DLL is loaded. There is no other mention of DynDOLOD at all, not even a DynDOLOD.esm, or DynDOLOD.esp are being loaded. In that state the DLL alone is not really doing much. Install Crash logger. Disable the Framework crash log by setting Debug.CrashLog.Enabled = 0 in NetScriptFramework.config.txt. Install this test version of DynDOLOD DLL NG. https://mega.nz/file/EMIzDZhS#0I1Rc1K5bJo86E1s2Gz4IJB3rIoJlQhZ6kqbXpfJIZA If problem persists, upload new crash logger log. In the DynDOLOD output edit ..\skse\plugins\DynDOLOD_Data\DynDOLOD_NG_Worlds.txt and set debug=true Upload c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\DynDOLOD.log

Download this version of DynDOLOD DLL NG and test if it works with this one. https://mega.nz/file/EMIzDZhS#0I1Rc1K5bJo86E1s2Gz4IJB3rIoJlQhZ6kqbXpfJIZA Do some fast travel and load doors in the solitude area and anywhere else to test if it really does not crash anymore. Otherwise upload a new crash log.

Use crash logger as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs to produce a better and more useful crash log and upload that.

That is great. Thanks for letting us know.

Yes, for DynDOLOD to list the worldspace, the persistent cell needs to be added by the same plugin that also adds the worldspace.

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#In-Game-Screenshots how to make close up screenshots in the LOD area with tlc. Test if something is actually "grass" by toggeling all grass off/on with tg in console. See https://dyndolod.info/Help/Grass-LOD#Not-all-grass-types-have-LOD-grass-LOD-billboards and https://dyndolod.info/Help/Grass-LOD#No-Grass-LOD-Check-List

You can add it manually via xEdit. As soon as you start adding references, markers and whatnot, especially once they are properties of scripts for example, CK will set them persistent and create the persistent cell.

The attached archvie contains a new dynamic LOD mesh for that water plane, which you can merge with the existing DynDOLOD Resoures SE 3 installation for example (it will be included in its next version) 2fmwater.zip Once installed, generate new DynDOLOD output, which should hopefully then not try to use the full model for LOD anymore causing issues. If the issue persists upload new crash log, DynDOLOD_SSE_Object_Report.txt, DynDOLOD log and debug log.

The first two links are the TexGen log and debug log, also upload the DynDOLOD log and debug. What mod is Meshes\water\2fmwater1024.nif from?

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. Also upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt

The worldspace Hweitwik "Hweitwik" [WRLD:xxCC169D] does not have a persistent cell, which is required for generating LOD with DynDOLOD. https://dyndolod.info/FAQ#Not-seeing-all-worldspaces-in-the-selection-box Only worldspaces that have a persistent cell are shown. If you have a problem with xLODGen generating terrain LOD, upload the SSELODGen_log.txt

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. If I understand correctly, the custom worldspace shows in SSELODGen? SSELODGen means the latest version of xLODGen from https://stepmodifications.org/forum/topic/13451-xlodgen-terrain-lod-beta-115-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal-enderalse?

What tool is it that you have a problem with? I assume the game is Skyrim Special Edition.