DynDOLOD 3.00 Alpha 198

[Fiery]

Hello, tex gen and dyn both keep telling me there's an update, but there is no update. I downloaded and replaced my version 197 folder with alpha 198 on the 6th January but both apps say they are still 197, I've double checked and the zipped folder says its "DynDOLOD 3.00-68518-Alpha-198-1767630909.7z".

I tested again by extracting the 7z folder, deleting the current DynDOLOD folder and copying 198 folder in to my 'game tools' folder, updating the .exes in my mo2 list and opening tex gen through m02 and again, it tells me new version is available. Might be worth checking version numbers. 

[aedhan]

Hi,

Apologies if this is not the correct place to post this question but I think the issue is LOD related (not specifically DynDOLOD) and was hoping some people here would have some insight.

 

When I move across the Whiterun Tundra, the distance will momentarily fail to render (~1 second while it seems to load): 

In the distance there is a flickering black rectangle floating in the sky which cannot be selected in console and disappears when approached:

(the tiny rectangle is just to the right of center)

The console command <TLL> results in bands emanating from the rectangle and also across the screen, and as also filling the background as in the first image (it changes as approached:

  

 

I disabled DynDOLOD and performed a clean save, but the issue didn't go away.

The problem occurs consistently in the Tundra, and sometimes in the northeast, where half the distance view on the screen will sometimes be similarly blanked out (sorry I couldn't get an image and am not sure how to describe it).

Again, I'm not sure if this is specifically LOD related, a bad mesh or a failing video card. I was just hoping someone could point me in the right direction.

 

Thank you.

[sheson]

8 hours ago, Fantasi said:

Just did the tests for the below, and no Papyrus log was generated, is this going to be an issue?

"Rename DynDOLOD_NG_Tamriel.txt to DynDOLOD_NG_Tamriel.bak" - Issue persisted, FPS tanked

"disable Occlusion.esp" - Issue persisted, FPS tanked

"disable DynDOLOD.esp" - Issue persisted, FPS tanked

 

Note that I did the above test in descending order, meaning the name change for DynDOLOD_NG_Tamriel was in affect for the later 2 tests, and Occlusion.esp wasnt enabled for the disabling DynDOLOD.esp test.

The papyrus log not being created might be related.

For now continue with these steps and leave each preceding step in place as you did:
Disable DynDOLOD.esm to see if that makes a difference.
If that made no difference, hide, rename or move the textures folder in the DynDOLOD output.
If that made no difference, hide, rename or move the meshes folder in the DynDOLOD output.
If that made no difference, hide, rename or move the SKSE folder in the DynDOLOD output.
Report results.

[sheson]

3 hours ago, Fiery said:

Hello, tex gen and dyn both keep telling me there's an update, but there is no update. I downloaded and replaced my version 197 folder with alpha 198 on the 6th January but both apps say they are still 197, I've double checked and the zipped folder says its "DynDOLOD 3.00-68518-Alpha-198-1767630909.7z".

I tested again by extracting the 7z folder, deleting the current DynDOLOD folder and copying 198 folder in to my 'game tools' folder, updating the .exes in my mo2 list and opening tex gen through m02 and again, it tells me new version is available. Might be worth checking version numbers. 

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search

https://stepmodifications.org/forum/topic/19903-dyndolod-300-alpha-198/page/720/#findComment-288627

[sheson]

58 minutes ago, aedhan said:

Hi,

Apologies if this is not the correct place to post this question but I think the issue is LOD related (not specifically DynDOLOD) and was hoping some people here would have some insight.

 

When I move across the Whiterun Tundra, the distance will momentarily fail to render (~1 second while it seems to load): 

In the distance there is a flickering black rectangle floating in the sky which cannot be selected in console and disappears when approached:

(the tiny rectangle is just to the right of center)

The console command <TLL> results in bands emanating from the rectangle and also across the screen, and as also filling the background as in the first image (it changes as approached:

  

 

I disabled DynDOLOD and performed a clean save, but the issue didn't go away.

The problem occurs consistently in the Tundra, and sometimes in the northeast, where half the distance view on the screen will sometimes be similarly blanked out (sorry I couldn't get an image and am not sure how to describe it).

Again, I'm not sure if this is specifically LOD related, a bad mesh or a failing video card. I was just hoping someone could point me in the right direction.

 

Thank you.

Generating Occlusion.esp should fix the first issue. See https://dyndolod.info/Help/Occlusion-Data

The second issue might be a broken mesh. To see if it is LOD related toggle LOD off with tll in console.  To see if it tis full grass related toggle off grass with tg in console. Otherwise see if it can be clicked with console open and what more informative console shows. Use the disable command in console or a highlighter mod to see if it was selected and not some cloud, fog etc. in behind or in front of it.

[Fantasi]

37 minutes ago, sheson said:

The papyrus log not being created might be related.

For now continue with these steps and leave each preceding step in place as you did:
Disable DynDOLOD.esm to see if that makes a difference.
If that made no difference, hide, rename or move the textures folder in the DynDOLOD output.
If that made no difference, hide, rename or move the meshes folder in the DynDOLOD output.
If that made no difference, hide, rename or move the SKSE folder in the DynDOLOD output.
Report results.

Hi,

I have done these testings and each was done 3 times on the same save to ensure consistency, I also checked the Papyrus log location and a new one wasnt generated.

each test was also done with the previous changes (name change to the .txt file, disabling both occlusion and dyndolod.esp)

"hide, rename or move the textures folder in the DynDOLOD output" - I removed the texture folder, and the frames seems to have gotten worse, was averaging 40 within whiterun now am getting 20

"hide, rename or move the meshes folder in the DynDOLOD output" - I removed the meshes folder, this actually made the issue go away, was able to get around 110 frames consistently throughout whiterun, and leaving whiterun didnt tank the fps further

"hide, rename or move the SKSE folder in the DynDOLOD output" - I removed the SKSE folder, I actually got an error, see below link, but there is no FPS tanking issue

https://imgur.com/PbEQmMj

Thanks!

[aedhan]

57 minutes ago, sheson said:

Generating Occlusion.esp should fix the first issue. See https://dyndolod.info/Help/Occlusion-Data

The second issue might be a broken mesh. To see if it is LOD related toggle LOD off with tll in console.  To see if it tis full grass related toggle off grass with tg in console. Otherwise see if it can be clicked with console open and what more informative console shows. Use the disable command in console or a highlighter mod to see if it was selected and not some cloud, fog etc. in behind or in front of it.

Hi Sheson,

 

I will do as you suggested. I did already have an Occlusion.esp. I recently updated my LODs and reran Texgen and DynDOLOD (with Occlusion ticked). However, I hadn't rerun xLODGen. Could the issue be due to the older xLODGen Output (terrain only)?

 

Thanks again.