DynDOLOD 3.00 Alpha 182

[Kattmandu]

Not quite sure where to post this.  Please point me to the correct thread if this is not it.  After starting a new game using "I own property in one of the holds" in AS-LAL, I noticed a horse stable (just outside of the Hearthfire home I was spawned into) was flickering and blurry.  The vertical posts on the horse stable become blurry and flicker as soon as the "DynDOLOD successfully initialized" message pops up on the screen after exiting the Hearthfire home for the first time.  Before the DynDOLOD message appears, they look fine.  LOOT shows no files requiring cleaning.  And uGridsToLoad is 5 and uLargeRefLODGridSize is 11.  So I re-ran DynDOLD setup and started another new game.  Same thing happened.

DynDOLOD.log

DynDOLOD_SSE_log.txt

TexGen_SSE_log.txt

 

 

 

Edited February 3, 2023 by Kattmandu

[sheson]

9 minutes ago, Kattmandu said:

Not quite sure where to post this.  Please point me to the correct thread if this is not it.  After starting a new game using "I own property in one of the holds" in AS-LAL, I noticed a horse stable (just outside of the Hearthfire home I was spawned into) was flickering and blurry.  The vertical posts on the horse stable become blurry and flicker as soon as the "DynDOLOD successfully initialized" message pops up on the screen after exiting the Hearthfire home for the first time.  Before the DynDOLOD message appears, they look fine.  LOOT shows no files requiring cleaning.  And uGridsToLoad is 5 and uLargeRefLODGridSize is 11.  So I re-ran DynDOLD setup and started another new game.  Same thing happened.

Read the first post which DynDOLOD log and debug log to upload when making posts.

[Rozen]

1 hour ago, sheson said:

Let me know what happens with this test version https://mega.nz/file/UdRFDRBD#jeSA6FBQyzoJKPmfvMHU_IrOF_wV34kXKsIocBdfguQ

No getting stuck or locking up on run 1, here is the logs> https://ufile.io/f/xdm39

Also just letting you know, i do not have my new video card in yet, so still on the same one.

[Kattmandu]

1 hour ago, sheson said:

Read the first post which DynDOLOD log and debug log to upload when making posts.

I think I've got the correct log files added to my post now.  Sorry, new to all this.

[sheson]

1 hour ago, Kattmandu said:

I think I've got the correct log files added to my post now.  Sorry, new to all this.

Read the first post which DynDOLOD debug log to also upload when making posts.

However, judging by the DynDOLOD log, you started DynDOLOD and quit it again with generating LOD, which will have replaced the debug from the generation in question, which is unfortunate.

Install the latest version of DynDOLOD NG and scripts from https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds
If problem persists, also enable and check/upload papyrus log and all files from DynDOLOD Output ..\skse\plugins\DynDOLOD_Data\

[sheson]

1 hour ago, Rozen said:

No getting stuck or locking up on run 1, here is the logs> https://ufile.io/f/xdm39

Also just letting you know, i do not have my new video card in yet, so still on the same one.

Random success or not is the question...

[Kattmandu]

39 minutes ago, sheson said:

Read the first post which DynDOLOD debug log to also upload when making posts.

However, judging by the DynDOLOD log, you started DynDOLOD and quit it again with generating LOD, which will have replaced the debug from the generation in question, which is unfortunate.

Install the latest version of DynDOLOD NG and scripts from https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds
If problem persists, also enable and check/upload papyrus log and all files from DynDOLOD Output ..\skse\plugins\DynDOLOD_Data\

Ah, so that's why I couldn't find the debug log.  I did run the DynDOLOD program to confirm the following line was appearing...

Large reference bugs workarounds: enabled (DynDOLOD.DLL: NG, Scripts: NG, Deleted references: no)

 

I'll regenerate my DynDOLOD with the setting below (as per the Step guide) and post the debug log.

Edited February 3, 2023 by Kattmandu

[Rozen]

21 minutes ago, sheson said:

Random success or not is the question...

I will run again sense i am still waiting on my video card.

[sheson]

23 minutes ago, Kattmandu said:

Ah, so that's why I couldn't find the debug log.  I did run the DynDOLOD program to confirm the following line was appearing...

Large reference bugs workarounds: enabled (DynDOLOD.DLL: NG, Scripts: NG, Deleted references: no)

 

I'll regenerate my DynDOLOD with the setting below (as per the Step guide) and post the debug log.

Update DynDOLOD DLL NG and Scripts to the latest version

From your log:
DynDOLOD DLL: F:\Games\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD.dll, Version: 3.0.1.0, Game Version: SE/AE 1.5.x/1.6.x, VR 1.4.15, Date: 2023-01-06 21:00:00

Latest version of the DLL is Version: 3.0.2.0

[Rozen]

Rub 2 no getting stuck or crash, here is the logs> https://ufile.io/f/eypgr

[LordIceWolf]

On 2/2/2023 at 3:06 AM, sheson said:

Always use the latest alpha version. Do not waste time using older versions or reporting problems with older versions.

Go through every step of the No Grass LOD Check List and not only mention the outcome/result of a couple.

Good afternoon

I documented all the checklist as best I could. Added it to a text file so I dont post a text wall. Let me know if you need anything else.

Thanks

DynDOLOD Troubleshooting.txt

Edited February 4, 2023 by LordIceWolf

[Kattmandu]

1 hour ago, sheson said:

Update DynDOLOD DLL NG and Scripts to the latest version

From your log:
DynDOLOD DLL: F:\Games\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD.dll, Version: 3.0.1.0, Game Version: SE/AE 1.5.x/1.6.x, VR 1.4.15, Date: 2023-01-06 21:00:00

Latest version of the DLL is Version: 3.0.2.0

The Step guide specifically points to an archived version...

EDIT: Ah, okay, Step recently changed their link to point to Alpah-3.  I have Alpha-2.

Edited February 3, 2023 by Kattmandu

[Kattmandu]

1 hour ago, sheson said:

Update DynDOLOD DLL NG and Scripts to the latest version

From your log:
DynDOLOD DLL: F:\Games\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD.dll, Version: 3.0.1.0, Game Version: SE/AE 1.5.x/1.6.x, VR 1.4.15, Date: 2023-01-06 21:00:00

Latest version of the DLL is Version: 3.0.2.0

 

DynDOLOD_SSE_Debug_log.txt

https://ufile.io/crw1idbd (generated using DynDOLOD DLL NG Alpha-2)

Currently regenerating using Alpha-3

 

Edited February 3, 2023 by Kattmandu

[sheson]

1 hour ago, Kattmandu said:

The Step guide specifically points to an archived version...

EDIT: Ah, okay, Step recently changed their link to point to Alpah-3.  I have Alpha-2.

Third party guides are categorically outdated, especially when it comes to ALPHA version and experimental features. Read and use the official documentation that I already linked instead.  https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

1 hour ago, Kattmandu said:

DynDOLOD_SSE_Debug_log.txt

https://ufile.io/crw1idbd (generated using DynDOLOD DLL NG Alpha-2)

Currently regenerating using Alpha-3

The updated DynDOLOD DLL NG version does not affect LOD generation, though.

As I already wrote, if problem persists, also enable and check/upload papyrus log and also upload all files from DynDOLOD Output ..\skse\plugins\DynDOLOD_Data\

[sheson]

1 hour ago, LordIceWolf said:

Good afternoon

I document all the checklist as best I could. Added it to a text file so I dont post a text wall. Let me know if you need anything else.

Thanks

DynDOLOD Troubleshooting.txt 30.92 kB · 1 download

This does not show if the latest alpha-111 was used or not. Upload the accompanying TexGen/DynDOLOD logs and debug logs for which the checks have been done.

"Grass mapping not found" means that those grasses found in the cgid will not have grass LOD. This is expected for underwater grasses and grasses that do not have billboards generated.

If some BTOs have no grass LOD, it means there should be corresponding no "mapping not found" or "no grass data" messages. The first tells you which grass LOD billboards are missing, which you can then double check for creation in the ..\textures\terrain\lodgen\TexGen_[GAME MODE]_[Tree|Grass]_Billboards.txt log file as explained at  https://dyndolod.info/Help/TexGen-Configuration#Tree-Grass-LOD-Billboards.

Use expert mode to only generate a specific BTO again, so you only have log message for those 16 cells it covers. https://dyndolod.info/Help/Expert-Mode#Specific-Chunk

Use the DynDOLOD SkyUI MCM - You Are Here to know the coordinates for a BTO.