sheson

Install this test version https://mega.nz/file/JVhjDaYL#OhASF8Tgn6OpcJ90QeEcNM83f9aJ-PLXH0fbC69Tguo Start game. Upload the new SKSE64.log. Check if it created a new DynDOLOD.log in same folder and upload that as well. If it happens starts without error, test things in a full game a bit.

Since occlusion can not be generated when object LOD meshes generation fails, there are no out of memory message while generating occlusion and changing the OcclusionMaxThreadsObjectLOD setting is irrelevant. It does not change anything about LODGen. The INI setting are already documented in the DynDOLOD_SSE_debug_log.txt, there is not need to upload DynDOLOD_SSE.ini. Sounds like high memory usage is not the cause. Check the Windows Event log for related messages. Stress testing the system with tools overlockers use, like xorecycler using prime95, ycruncher or occt etc. could be useful. 21.9GB is an odd number for main memory. It should be closer to a power of 2 number, since you typically have 2 or 4 memory modules a 8GB, 16GB etc. Test if using the Framework version LODGenx64.exe works better by hiding the ..\DynDOLOD\Edit Scripts\LODGenx64Win.exe. Just use expert mode and Execute LODGen for the worldspaces and seasons that failed.

Install this test version https://mega.nz/file/dFRkWLjb#fQpueaGuoKFJjRMSpdB3qB9obvWxJIkOCwsG7v_6H-s Start game. Upload the new SKSE64.log. Check if it created a new DynDOLOD.log in same folder and upload that as well. There is not need to generate the LOD patch with DynDOLOD or to upload the the DynDOLOD_SSE_log.txt

https://dyndolod.info/FAQ#Older-versions If you have a problem with the latest version - like the insinuated CTD - post a problem report as explained in the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum

The latest version of Flying Crows seem to work fine in Skyrim VR just as it does in Skyrim SE using the latest versions DynDOLOD, Resources and DynDOLOD DLL NG. Make sure to use the Low, Medium or High button so the mesh rules included in the mod are loaded. If any problem persists upload the DynDOLOD log and debug log.

Install this https://mega.nz/file/BBom3C5R#kSZHRjFvS2W-ZJBPL6Ee4MnxJ291pfSsvDUTvqsKM0Y which contains 3 DLLs numbered 1 to 3. Start the game. SKSE will try to load all 3 DLLs. Upload the new SKSE64.log which should list them all. In case a DynDOLOD.log is created upload that, too.

See 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. Expert mode does not change being able to add or change rules in advanced mode already. See https://dyndolod.info/Help/Expert-Mode

Test if adding RenderBillboardsSingleThread=1 under [TexGen] in C:\Games\DynDOLOD 3.0\Edit Scripts\DynDOLOD\TexGen_SSE.ini makes a difference.

Install this test version https://mega.nz/file/YcBzwDgK#zU9cmz39LsfuyhjccUftsmu9RK3ewp4G9ZpN5_uCbGI Start game. Upload the new SKSE64.log. Check if it created a new DynDOLOD.log in same folder and upload that as well. Also upload I:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\skse.ini if it exists.

No bugreport.txt? xEdit Background Loader: [JewelryCollection.esp] File loaded (CRC32:787E7818) xEdit Background Loader: Fatal: <EAssertionFailed: Assertion failure (E:\Delphi\Projects\DynDOLOD3\Core\wbImplementation.pas, line 19269)> The error happens while the xEdit background loader is loading plugins. Do you see a similar error with xEdit? Test if it loads after disabling JewelryCollection.esp. If it does, it means there is a problem with that plugin. Maybe loading and saving it with CK can fix that.

Install this test version https://mega.nz/file/lBoEBQqI#mbBNSHGlm6hsUue-kaSh1-kOraac__V9fdzouybczV0 Start game to see if it works or not. Upload the new SKSE64.log.

OP reported "the textures ARE in their respective BSA". I suggest to report a mod having missing assets depending on their version or install options to author of the mod so they can fix it. OPs primary problem is not really missing textures.

Deactivate/Backup the working DynDOLOD DLL NG and Script test and install this version https://mega.nz/file/8NZ12TgY#wrsnm87qNrN5vC31fELxZ5ycFXx9PCqcVJeLnT-tgiQ Start game to see if it works or not. Upload the new SKSE64.log. If it still works, this will be the last test version for now.

Deactivate/Backup the working DynDOLOD DLL NG and Script test and install this version https://mega.nz/file/EcJBgaCS#530sEu4TjrL7EB1xgAn-3bqjoVvxthS0-SlebH4WHtU Start game to see if it works or not. Upload the new SKSE64.log.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Check-the-FAQ -> https://dyndolod.info/FAQ#ILS-or-CTD It is very unlikely for Occlusion.esp to cause crashes by itself. It is created by copying worldspace and cell records from the winning plugins before it, then update the TVDT Occlusion data which itself can not rally cause crashes. The DynDOLOD and Occlusion plugins might show up in crash logs a lot, since they are typically the plugins last to overwrite worldspace and cell records, so careful reading and interpretation of the stacks and registers etc. might be required to identify the actual cause of the problem. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Ignore random people that clearly have no clue what they are talking about as you already realized. DynDOLOD does not affect NPCs/Characters or Armors.

Moved to the DynDOLOD 3 Alpha thread. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD lo, debug log and bugreport.txt to upload when making posts. Use the "Copy this message to clipboard" link shown in the message window to copy/paste messages in stead of posting a screenshot as explained in the first and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text Use the link "Click on this link for additional explanations and help for this message" link shown in the message window to open https://dyndolod.info/Messages/Exceptions#Assertion-failure as explained in the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages: Always use the latest version of DynDOLOD/TexGen as explained above. If the assertion failure is a 100% repeatable, it might be caused by a broken plugin. Clean and error check the load order with xEdit before generating LOD as explained above. If the assertion failure is not 100% repeatable or no error can be found in plugins, it could 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.

Remove all old DLLs and Scripts. Install this test version https://mega.nz/file/cExTWQDR#swWZHRoRKSpBBrPc6NwHB7sIRbQe9aewrsz-nY7rwew Start game to see if it works or not. Upload the new SKSE64.log.

Deactivate whatever DynDOLOD DLL NG and Script you have active in the load order. install this https://mega.nz/file/hAJj1aIZ#7FkB1S5m9HFwuf_kN51E5x7I-1_mSFLj88vCXvvynGk which contains 4 DLLs numbered 1 to 4. Start the game. SKSE will try to load all 4 DLLs. Upload the new SKSE64.log which should list them all.

None of the links has the SKSE64.log. There is only a skse64_loader.log Check if the OS, UAC or antivir is interfering. Check the Windows Event log for hints.

https://dyndolod.info/Official-DynDOLOD-Support-Forum Try not to make posts that only promise more information, logs, results etc. in the future. If it takes time to first gather information, logs, results etc. it is fine to just take it and then post when ready.

The debug log shows that both RenderSingle and RenderTexturesSingleThread are set to 0 in D:\Modding Tools\Dyndolod\Edit Scripts\DynDOLOD\TexGen_SSE.ini Problems with OpenGL are not caused by mods.

The debug log only contains the last session, which shows TexGen completing without error. I would rather be interested in the debug log that shows the error. In any case, run the test version from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/?do=findComment&comment=282545

Delete all old logs and bugreport.txt. Restore to the default TexGen_SSE.INI if there were any changes made to it and check what happens with this test version https://mega.nz/file/kYRQSKia#7fOkTxEn8gj_o4kS8hRmi2tx5E66mb1cJbSF-5uyLi8 If it complains about Texconvx64.exe, download this version https://mega.nz/file/QV4w1YRY#vHCnSwg69AOLZOB1BpErWV2Tki7wDaq_UH7xDM4WfIY and replace it in the Edit Scripts folder. If there still is a problem with the default settings, add GLDebug=1 to TexGen_SSE.ini and run again. Upload new TexGen log, debug log and bugreport.txt if it exists. Then test if adding RenderSingle=1 under [TexGen] in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini makes a difference. If not test if adding RenderTextureSingleThread=1 makes a difference. If not test if adding RenderBillboardsSingleThread=1 makes a difference. Do one change/check at a time. Report results no matter the outcome. The links in this post are updated once in a while as troubleshooting progresses. So redownload if you have issues with a version from a few days ago. See end of the thread posts.

This test version should fix the path issue https://mega.nz/file/UBgTHJja#F5MxXAUf6hwLKq5AnRL0gtsjR9p8X-HPxX6rb_guyR8

Test what happens with this version https://mega.nz/file/AdYXUBJA#T4Gq4gAJQpxNiENd4KmKchqGkAsGGh0FLCX2Fs8DhNg Install/Replace older version, then start the game.