sheson

That either means you just installed DynDOLOD Standalone or last time DynDOLOD was run generating static object LOD was not checked or something went wrong with the static object LOD generation. In the last case the message window saved to DynDOLOD\Logs\DynDOLOD_SSE_log.txt should error or warning messages.

Plugins causing exceptions are not incompatible or break DynDOLOD/xEdit. Such plugins are broken or contain invalid data that will also cause trouble in the game. The xEdit error check only scans for a limited number of known issues typically caused by CK or careless modding practices. I suggest to carefully read the messages above and below the exception and follow the suggestions.

Sorry, I copied/pasted an incorrect path. Check the file DynDOLOD\Edit Scripts\Export\LODGen_SSE_Tamriel.txt

Check if DynDOLOD\Edit Scripts\Export\LODGen_SSE_Tamriel.txt contains the lines 00033DCB 00010400 110513.625000 79564.023437 2285.708740 357.2630 359.1538 157.1023 1.0 PROM_ShrineOfAzura01Snow_Only 00000000 Snow-LargeRef meshes\prometheus\architecture\statuessnow\azurastatuesnow_only.nif meshes\lod\clutter\azurastatue_lod_0.nif meshes\lod\clutter\azurastatue_lod_2.nif meshes\lod\clutter\azurastatue_lod_2.nif and 0806EBD3 00010400 110513.625000 79564.023437 2285.708740 357.2630 359.1538 157.1023 1.0 ShrineOfAzura01 00000000 Snow meshes\clutter\statues\shrineofazura01.nif meshes\lod\clutter\shrineofazura01_lod_0.nif meshes\lod\clutter\shrineofazura01_lod_2.nif meshes\lod\clutter\shrineofazura01_lod_2.nif

Doing the suggest search finds older posts with the same error, so I merged your post. See above for the answer which mod causes the missing model.

This is the same error message as above, though The reason was never found as the user redid the entire load order from scratch. Obviously the same troubleshooting steps I already suggested back then apply, so just follow them through and report back. From the DynDOLOD Standalone archive copy the content of the 'DynDOLOD' folder, which contains the files DynDOLOD.exe, TexGen.exe, DynDOLOD_QuickStart.html and the sub folders 'Docs' and 'Edit Scripts' with all their content into a new 'DynDOLOD' folder outside of special OS folders like 'Programs Files' or 'Program Files (x86)', the SteamApps or game folders and Mod Organizers virtual file structure.

Which plugins overwrite the base record [sTAT:00033DCA] that is used by the reference REFR:0806EBD3? What is the path/to/model.nif defined on the last plugin to win?

Does the DynDOLOD log contain a log entry similar to Disabled NeverFade, replaced by static LOD for Unofficial Skyrim Special Edition Patch.esp [REFR:00033DCB] (places ShrineOfAzura01 [sTAT:00033DCA] in GRUP Cell Persistent Children of [CELL:00000D74] (in Tamriel "Skyrim" [WRLD:0000003C]) at 26,19) Which plugins overwrite the base record [sTAT:00033DCA] that is used by the reference REFR:00033DCB?

That is all correct. But which is the last plugin to modify the base record that defines the NIF.

Also check if the base record is changed by a plugin. You can CTRL+left mouse click on the record entry in the Base - NAME row.

If the texture does not match, it is because it is the wrong one for the bto, e.g. different generation. Start NifSkope from within MO while with no other Nifskope started from outside MO being active.

Great to hear. Enjoy.

It's probably running out of memory. Use the x64 version. From the DynDOLOD Standalone archive copy the content of the 'DynDOLOD' folder, which contains the files DynDOLOD.exe, TexGen.exe, DynDOLOD_QuickStart.html and the sub folders 'Docs' and 'Edit Scripts' with all their content into a new 'DynDOLOD' folder outside of special OS folders like 'Programs Files' or 'Program Files (x86)', the SteamApps or game folders and Mod Organizers virtual file structure. Do not mix with old versions or xEdit installation. If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum http://forum.step-pr...ndolod-support/ Truncate the log to the last generation. Use pastebin or a file service.

So which plugins other than unofficial patch is modifying the statue? Check the reference 00033DCB (confirm in game that is the reference of the statue when loaded) and its used base record in xEdit.

Q1 So the blue part at the top is not Sky but LOD water in existing BTR terrain LOD meshes? LOD water uses the LOD water type defined by the NAM3 - LOD Water Type on the WRLD record. Make it the same as NAM2 - Water which is used by default in the loaded cells if the CELL record does not define its own XCWT - Water. Q2 xLODGen ignores the NAM4 - LOD Water Height value on the WRLD record and uses the value from DNAM - Land Data \ Default Water Height instead. If a CELL records defines anything but "Default" for its XCLW - Water Height, that value will be used instead for that cell. You can always write an xEdit script to mass update records.

You did not say which worldspace that is. Is it a mod? Picture 1 looks like this is the edge of world. LOD is only generated for quads for which at least one CELL records exist. The coordinates and dimension of the discovered area are shown in the log. Picture 2 seems to show that either the CELL records have no Has Water flag, No LOD water flag or the default water height defined on the world record is lower than the terrain. The used default water height is shown in the log.

A ESP plugin is probably modifying the Azura statue - which is a large reference. See if setting the ESM flag on the plugin before generating solves the issue. Alternatively, test if removing the overwrite from the plugin before generating helps. Might be AzuraShrineExtra.esp. Let me know which mod that is from.

You need to tell NifSkope where to find the correct texture for the BTO/NIF.

Exception in unit userscript line 350: Executing TexConv returned error C0000135: "D:\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -y -f BC7_UNORM -bcquick -o "D:\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD" "D:\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_Tamriel00.dds" Install/Update Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which DynDOLOD.exe/TexGen.exe (x86) or DynDOLODx64.exe/TexGenx64.exe (x64) is used. LODGen.exe will print an explanatory message in case it is missing. Texconv.exe will fail with error C0000135.

DynDOLOD does not change how the engine works. Things load/unload on a cell by cell basis, not based on buffers. The flickering happens in the loaded cells (toggle them with tll)? If it is outside the loaded cells, it is large reference bugs. It sounds like the object LOD models do not unload after the full models loaded, only once you move to the next cell? See FAQ: Game: Out of place objects / floating objects / flickering full models for all answers. A: If the problems is stuck object LOD in Whiterun after fast travel, change Distant Object Detail on the View Distance tab of the Advanced options of the games launcher from Ultra to High. Alternatively try just slightly changing the value fBlockLevel0Distance=60000 in SkyrimPrefs.ini to 57000. A: Flickering textures (full and LOD model showing at the same time) in Skyrim Special Edition and Skyrim VR are caused by plugins triggering the large reference bugs as explained in ..DynDOLOD\Docs\DynDOLOD_Manual_SSE.html. Verify if the problem goes away by setting uLargeRefLODGridSize=5 in SkyrimPrefs.ini. It might be possible that the much larger object LOD bto files that now also have lots of BSMultiBoodNode/BSSubIndexTriShapes overwhelm the engine. See what happens if you remove most of the LOD level 4 files and all of the LOD level 8/16 files to test if this might be a resource issue. Then test in the area where there are the remaining couple LOD 4 files.

DynDOLOD/xEdit does not need to be adapted to mod managers. Plugins need to be free of errors and not contain invalid data.

Exception in unit prepare line 581: Can not copy [REFR:06100D63] (places USLEEP_ShipLargeKatariah02_LOD [sTAT:06200D62] in GRUP Cell Persistent Children of [CELL:00000D74] (in Tamriel "Skyrim" [WRLD:0000003C]) at -12,26) from Unofficial Skyrim Legendary Edition Patch.esp into DynDOLOD.esp Assertion failure (C:\Delphi\projects\DynDOLOD\wbImplementation.pas, line 14062) Check log lines above the exception for additional hints. Check the FAQ and search official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/ for those errors. Following the suggestions of the error message to check the FAQ find this answer: FAQ: DynDOLOD.exe: Can not copy xxxx from xxxx.esp into xxx.espA: Often caused by a broken bashed patch. Use a newer Wrye Bash version to create the patch or do not use the merge patches option. A: There is a plugin in the load order with errors. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help. If removing the bashed patch lets the process run through, it means that the bashed patch is broken and needs to be generated again with a newer version of Wrye Bash Following the suggestions of the error message to search the official forum finds these related threads:https://forum.step-project.com/topic/14301-can-not-copyhttps://forum.step-project.com/topic/14127-can-not-copyhttps://forum.step-project.com/topic/14136-can-not-copyhttps://forum.step-project.com/topic/14025-can-not-copyhttps://forum.step-project.com/topic/14140-can-not-copyhttps://forum.step-project.com/topic/14205-can-not-copyhttps://forum.step-project.com/topic/14256-can-not-copy

Do that with latest xEdit, report it, then maybe it gets fixed if important enough.

Thanks. With that extra information I was able to replicate the issue. Will be fixed in DynDOLOD 2.76.

I can not replicate that with just the mod. Upload the DynDOLOD log for that generation and the DynDOLOD.esm. Make sure DynDOLOD.esm is not a master in Solitude Docks.esp.