DynDOLOD 3.00 Alpha 182

[sheson]

45 minutes ago, NoCleverness said:

I did upload the logs. They're in a ufile link above. Please read them. If you mean the papyrus log, here are a few.

Papyrus.0.log 2.13 kB · 1 download Papyrus.1.log 247.78 kB · 0 downloads

The also requsted DynDOLOD.log from DynDOLOD.DLL was not provided.
Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to uplaod the DynDOLOD.log from the DynDOLOD.DLL.
If a DynDOLOD.DLL is being used or installed, also upload the entire DynDOLOD.log:
c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log.

The linked logs only contain a DynDOLOD_SSE_Debug_log.txt  and DynDOLOD_SSE_log_truncated.txt. So I also requsted the papyrus log and DynDOLOD.log from DynDOLOD.DLL afterwards. That request was ignored. I checked the uploaded logs from the DynDOLOD generation as I wrote: The uploaded DynDOLOD logs show that DynDOLOD output was generated with DynDOLOD DLL NG and Scripts installed.

Still not clear if an existing save game or new game was started when those message shows.
The Papyrus.0.log does not show much seems like main menu only, no message related to DynDOLOD.
The Papyrus.1.log looks like what happens when a save that is not cleaned is being loaded.

Load whatever save that needs cleaning without any DynDOLOD output, Resources, DLLs etc. files whatsoever active in the load oder. Go into an interior if not in one. Save the game. Make a backup. Use the Clean option Remove unattached instances and Remove undefined elements for Scripts and Script Instances starting with #SHESON_DynDOLOD_* with Resaver from FallrimTools - Script cleaner and more on that save. Then load that save and save again. Then enable DynDOLOD Resources, DynDOLOD DLL NG and Scripts and the DynODLOD output make for it. Load the last save.

[NoCleverness]

46 minutes ago, sheson said:

The also requsted DynDOLOD.log from DynDOLOD.DLL was not provided.
Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to uplaod the DynDOLOD.log from the DynDOLOD.DLL.
If a DynDOLOD.DLL is being used or installed, also upload the entire DynDOLOD.log:
c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log.

The linked logs only contain a DynDOLOD_SSE_Debug_log.txt  and DynDOLOD_SSE_log_truncated.txt. So I also requsted the papyrus log and DynDOLOD.log from DynDOLOD.DLL afterwards. That request was ignored. I checked the uploaded logs from the DynDOLOD generation as I wrote: The uploaded DynDOLOD logs show that DynDOLOD output was generated with DynDOLOD DLL NG and Scripts installed.

Still not clear if an existing save game or new game was started when those message shows.
The Papyrus.0.log does not show much seems like main menu only, no message related to DynDOLOD.
The Papyrus.1.log looks like what happens when a save that is not cleaned is being loaded.

Load whatever save that needs cleaning without any DynDOLOD output, Resources, DLLs etc. files whatsoever active in the load oder. Go into an interior if not in one. Save the game. Make a backup. Use the Clean option Remove unattached instances and Remove undefined elements for Scripts and Script Instances starting with #SHESON_DynDOLOD_* with Resaver from FallrimTools - Script cleaner and more on that save. Then load that save and save again. Then enable DynDOLOD Resources, DynDOLOD DLL NG and Scripts and the DynODLOD output make for it. Load the last save.

Sorry about that, here's the log. I'm not particularly attached to the save file, which got corrupted anyway when the Xbox game overlay decided to freeze my computer. I'll start a new game later today to see if that works.

DynDOLOD.log

[sheson]

30 minutes ago, NoCleverness said:

Sorry about that, here's the log. I'm not particularly attached to the save file, which got corrupted anyway when the Xbox game overlay decided to freeze my computer. I'll start a new game later today to see if that works.

DynDOLOD.log 327 B · 0 downloads

The DynDOLOD.log shows what happens when starting the game to the main menu only. The one that is recorded with whatever was done to produce Papyrus.1.log above would be of intertest.

If you do not care about the save, then test what happens when starting a new game (from main menu with coc riverwood for example) and in case there are issues, upload the corresponding Papyrus log and DynDOLOD.log from DynDOLOD.DLL.

[NoCleverness]

8 hours ago, sheson said:

The DynDOLOD.log shows what happens when starting the game to the main menu only. The one that is recorded with whatever was done to produce Papyrus.1.log above would be of intertest.

If you do not care about the save, then test what happens when starting a new game (from main menu with coc riverwood for example) and in case there are issues, upload the corresponding Papyrus log and DynDOLOD.log from DynDOLOD.DLL.

Having completely restarted the game, there seems to be no issues beyond the extra bumpiness of the initial carriage ride caused by having a bunch of mods initializing at once. Guess there really was something screwy with the original installation. Thank you for your patience.

[captainlei1993]

No water in white river when seen from Whiterunworldspace

Screenshots: No water bug

Logs: Related Logs

 

[sheson]

2 hours ago, captainlei1993 said:

No water in white river when seen from Whiterunworldspace

Screenshots: No water bug

Logs: Related Logs

Load everything in xEdit

Load cell records with FormID 0x0001A279 and 0x00009639 and post screenshots of them that show all plugins/overwrite and all records, especially the XCLW Waterheight.

[captainlei1993]

6 hours ago, sheson said:

Load everything in xEdit

Load cell records with FormID 0x0001A279 and 0x00009639 and post screenshots of them that show all plugins/overwrite and all records, especially the XCLW Waterheight.

Here you go. Even if I changed the water height of 1A279 in Occlusion to -4700, the bug persists.

[sheson]

9 hours ago, captainlei1993 said:

Here you go. Even if I changed the water height of 1A279 in Occlusion to -4700, the bug persists.

There will be more than one cell having the same problem.

Generate LOD / Occlusion.esp with this DynDOLOD test version https://mega.nz/file/BQZT1IIA#50PA6b--RUG3WL3VrE1CJ3sbjWWJ1g5ROXECOyqoPdI as it should properly forward the Parent->Child cell updates.

[captainlei1993]

7 hours ago, sheson said:

There will be more than one cell having the same problem.

Generate LOD / Occlusion.esp with this DynDOLOD test version https://mega.nz/file/BQZT1IIA#50PA6b--RUG3WL3VrE1CJ3sbjWWJ1g5ROXECOyqoPdI as it should properly forward the Parent->Child cell updates.

Using the test version you provided produced this error on startup.

Logs.7z

[sheson]

14 minutes ago, captainlei1993 said:

Using the test version you provided produced this error on startup.

Logs.7z 15 kB · 0 downloads

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text
Copy and paste text instead of making screenshots of text. Text can be indexed and searched so posts can be found more easily.
If the option Copy message to clipboard is available on a message prompt, use it to copy and paste the text.
Screenshots of text means it can not be searched, copied or pasted. Screenshots of text means the text can not be read by screen readers. Screenshots of text makes it hard to read on small screens. Text needs less space compared to images. Copy pasting text is easier to do than taking screenshots and uploading images.

Download this test version https://mega.nz/file/hZpkTQIb#1citFVdLgiaQcWzfVQxZZpp3Clw6gC25mRDqhHuU8QU

[captainlei1993]

Another error occurred in the middle of LOD generation: Logs

[sheson]

7 hours ago, captainlei1993 said:

Another error occurred in the middle of LOD generation: Logs

Try with this test version https://mega.nz/file/dEJDSY7S#06hp-aoTY6VJLJatn_qK3x491l8AABYaHENwiV2oyPc

[captainlei1993]

2 hours ago, sheson said:

Try with this test version https://mega.nz/file/dEJDSY7S#06hp-aoTY6VJLJatn_qK3x491l8AABYaHENwiV2oyPc

The time works perfectly, thank you!

[sheson]

50 minutes ago, captainlei1993 said:

The time works perfectly, thank you!

Great! Thanks for letting us know.

[Xanny]

Hi Guys, thanks for your works.

I got same problem on my two different modlist:

Access violation at address 00000000014E5F82 in module 'DynDOLODx64.exe' (offset F05F82). Read of address 0000000000000000.

Don't know if you discussed yet about this problem, i tried in many ways, xediting, reinstalling different modlist... so now i'm here

bugreport.txt:

https://paste.ee/p/wPmly#section0

DynDOLOD_SSE_Debug_log.txt:

https://paste.ee/p/zW3Em#section0

DynDOLOD_SSE_log.txt:

https://paste.ee/p/P41Wf#section0

LODGen_SSE_Tamriel_log.txt

https://paste.ee/p/d38yh#section0

I hope i provided enough info's.

Thanks

Xanny