DynDOLOD 3.00 Alpha 190

[ZoiLATC10]

I have no idea how to allow for more video memory so I set the MaxMultiSamples=4 and halved the texture size and it is running fine now! Hopefully everything comes out looking decent (I'm not really a screenarcher, I just want it for normal gameplay so it should be fine)

Thank you so much for your help!

[Shredxt]

Hi Sheson,

First of all, thank you for the work you put into these awesome tools.

I am having some issues with the Winterhold College LODs, TexGen and .bto outputs seem to be fine, but in-game the college itself doesn't appear until I am extremely close, and then disappears again as I leave.

Logs: https://drive.google.com/drive/folders/1LAC1g0vczcBEASa5nI5NSuD0nZ-U5C9E?usp=sharing

Images: Imgur: The magic of the Internet

Thanks in advance for your help.

[Shredxt]

  On 5/19/2021 at 9:13 PM, Shredxt said:

Hi Sheson,

First of all, thank you for the work you put into these awesome tools.

I am having some issues with the Winterhold College LODs, TexGen and .bto outputs seem to be fine, but in-game the college itself doesn't appear until I am extremely close, and then disappears again as I leave.

Logs: https://drive.google.com/drive/folders/1LAC1g0vczcBEASa5nI5NSuD0nZ-U5C9E?usp=sharing

Images: Imgur: The magic of the Internet

Thanks in advance for your help.

Expand  

Please disregard, after hours of pulling my hair out in xEdit and looking for conflicts, it was ini related.

[sheson]

  On 5/20/2021 at 12:58 AM, Shredxt said:

Please disregard, after hours of pulling my hair out in xEdit and looking for conflicts, it was ini related.

Expand  

I would assume it hat to do with the large reference grid, right?

[Zackmaniac]

Hi gang (and Sheson). I've suffered in silence on this one for a while as I tried to figure out a solution on my own, but I just haven't been able to make any progress because I'm still fairly new to modding.

(My logs are linked here, but I've boiled the issue down as best I can below, in case you don't want to slog through them): DynDOLOD Logs

My problem is that whenever I run DynDOLOD (3.00 Alpha33), I get literally hundreds of warning messages, mostly of two types. I'm hoping someone can tell me in relatively simple terms what these warnings mean.

1) I get hundreds of "Warning: Overwritten large reference in..." messages, mostly relating to environment mods -- JK's Skyrim, The Borders of Skyrim, Realistic Water Two, Depths of Skyrim, and a few others. A couple examples: 

<Warning: Overwritten large reference in JKs Skyrim.esp [REFR:00012DF6] (places Farmhouse02 [STAT:00000846] in GRUP Cell Temporary Children of Riverwood04 [CELL:00009731] (in Tamriel "Skyrim" [WRLD:0000003C] at 5,-12))>

<Warning: Overwritten large reference in tposcthebordersofskyrim.esp [REFR:000EE3F7] (places MountainTrim01_LightSN [STAT:00030204] in GRUP Cell Temporary Children of [CELL:000090B2] (in Tamriel "Skyrim" [WRLD:0000003C] at 25,8))>

2) I also get dozens of "Warning: Initially disabled large reference in..." messages, all related to Realistic Water Two. One example:

<Warning: Initially disabled large reference in RealisticWaterTwo - Resources.esm [REFR:000BB9E9] (places RockCliff02Rocks01 [STAT:0002BABB] in GRUP Cell Temporary Children of [CELL:000090D2] (in Tamriel "Skyrim" [WRLD:0000003C] at 24,7))>

I've been able to successfully generate DynDOLOD output in the past without any issues at all, and I can't figure out what's changed since then. Also, everything *seems* to be working fine in-game -- good LODs, minimal pop-in, nothing out of the ordinary. But clearly there's some sort of error on my part.

Can someone who fully understands DynDOLOD (which I clearly do not) tell me what's happening to generate these warnings, so that I can set about trying to fix them? I feel like it's something really obvious that I'm doing wrong. Many, many thanks!

[Katarsi]

During LOD generation, I had an error, these are the last few lines (the relevant ones) of text on the DynDOLOD screen:

[06:36] [DLC01FalmerValley] Processing 7363 references
[06:37] Access violation at address 000000000041918F in module 'DynDOLODx64.exe'. Read of address 0000000000000000

bugreport.txt attached and the relevant log.

It turned out the mod The Blackest Reaches was the culprit and I had to remove it so I could generate LOD.

DynDOLOD_SSE_log.txtFetching info...

Edited May 20, 2021 by Katarsi
misspelling, adding log, removed bugreport

[sheson]

  On 5/20/2021 at 8:23 AM, Zackmaniac said:

Hi gang (and Sheson). I've suffered in silence on this one for a while as I tried to figure out a solution on my own, but I just haven't been able to make any progress because I'm still fairly new to modding.

(My logs are linked here, but I've boiled the issue down as best I can below, in case you don't want to slog through them): DynDOLOD Logs

My problem is that whenever I run DynDOLOD (3.00 Alpha33), I get literally hundreds of warning messages, mostly of two types. I'm hoping someone can tell me in relatively simple terms what these warnings mean.

1) I get hundreds of "Warning: Overwritten large reference in..." messages, mostly relating to environment mods -- JK's Skyrim, The Borders of Skyrim, Realistic Water Two, Depths of Skyrim, and a few others. A couple examples: 

<Warning: Overwritten large reference in JKs Skyrim.esp [REFR:00012DF6] (places Farmhouse02 [STAT:00000846] in GRUP Cell Temporary Children of Riverwood04 [CELL:00009731] (in Tamriel "Skyrim" [WRLD:0000003C] at 5,-12))>

<Warning: Overwritten large reference in tposcthebordersofskyrim.esp [REFR:000EE3F7] (places MountainTrim01_LightSN [STAT:00030204] in GRUP Cell Temporary Children of [CELL:000090B2] (in Tamriel "Skyrim" [WRLD:0000003C] at 25,8))>

2) I also get dozens of "Warning: Initially disabled large reference in..." messages, all related to Realistic Water Two. One example:

<Warning: Initially disabled large reference in RealisticWaterTwo - Resources.esm [REFR:000BB9E9] (places RockCliff02Rocks01 [STAT:0002BABB] in GRUP Cell Temporary Children of [CELL:000090D2] (in Tamriel "Skyrim" [WRLD:0000003C] at 24,7))>

I've been able to successfully generate DynDOLOD output in the past without any issues at all, and I can't figure out what's changed since then. Also, everything *seems* to be working fine in-game -- good LODs, minimal pop-in, nothing out of the ordinary. But clearly there's some sort of error on my part.

Can someone who fully understands DynDOLOD (which I clearly do not) tell me what's happening to generate these warnings, so that I can set about trying to fix them? I feel like it's something really obvious that I'm doing wrong. Many, many thanks!

Expand  

The large references bugs and the warning messages have been discussed plenty of time before and are not new to DynDOLOD 3 alpha.
The large reference bugs have been documented and explained years ago already in ..\DynDOLOD\Docs\SkyrimSELargeRefGrid\SkyrimSE-LargeRefGrid.html
Since ever DynDOLOD prints the list of overwritten large references that trigger these bugs. The main "fix" is still the same: Only ESM flagged plugins should overwrite large references.

 

[sheson]

  On 5/20/2021 at 9:51 AM, Katarsi said:

During LOD generation, I had an error, these are the last few lines (the relevant ones) of text on the DynDOLOD screen:

[06:36] [DLC01FalmerValley] Processing 7363 references
[06:37] Access violation at address 000000000041918F in module 'DynDOLODx64.exe'. Read of address 0000000000000000

bugreport.txt attached and the relevant log.

It turned out the mod The Blackest Reaches was the culprit and I had to remove it so I could generate LOD.

bugreport.txt 64.24 kB · 1 download

DynDOLOD_SSE_log.txt 128.92 kB · 1 download

Expand  

I could yet not replicate an error with that plugin loaded.

Can you also upload the DynDOLOD_SSE_Debug_log.txt?
You will have to rerun with the plugin active, as the debug is replaced with every session.

[Katarsi]

  On 5/20/2021 at 11:32 AM, sheson said:

I could yet not replicate an error with that plugin loaded.

Can you also upload the DynDOLOD_SSE_Debug_log.txt?
You will have to rerun with the plugin active, as the debug is replaced with every session.

Expand  

Well... This is weird.

I generated LOD again with The Blackest Reaches active and the error didn't reoccur. LOD generation went smoothly.

However, I did something before I generated it again: namely, I followed instructions on Underside Help Doc. I deactivated DVLaSS plugin only and left everything else from that mod in the load order. Then I set TerrainUnderside=1 and uncommented DoubleSidedTextureMask=mountain,mtn.

In the previous run that gave me an error, DVLaSS mod was removed entirely, however I didn't follow instructions from Underside Help.

I'm not sure how this helped, but apparently it did. Here is my new debug log if you still wish to see it, though: https://easyupload.io/mw0sa7

Edited May 20, 2021 by Katarsi

[z929669]

  On 5/20/2021 at 12:28 PM, Katarsi said:

Well... This is weird.

I generated LOD again with The Blackest Reaches active and the error didn't reoccur. LOD generation went smoothly.

However, I did something before I generated it again: namely, I followed instructions on Underside Help Doc. I deactivated DVLaSS plugin only and left everything else from that mod in the load order. Then I set TerrainUnderside=1 and uncommented DoubleSidedTextureMask=mountain,mtn.

In the previous run that gave me an error, DVLaSS mod was removed entirely, however I didn't follow instructions from Underside Help.

I'm not sure how this helped, but apparently it did. Here is my new debug log if you still wish to see it, though: https://easyupload.io/mw0sa7

Expand  

I have always run successfully with DVLaSS  but with the underside deactivated and TerrainUnderside=1 in DynDOLOD

[Katarsi]

  On 5/20/2021 at 1:12 PM, z929669 said:

I have always run successfully with DVLaSS  but with the underside deactivated and TerrainUnderside=1 in DynDOLOD

Expand  

You mean with Tamriel_Underside.nif removed from DVLaSS? But you left the plugin active?

[z929669]

  On 5/20/2021 at 1:25 PM, Katarsi said:

You mean with Tamriel_Underside.nif removed from DVLaSS? But you left the plugin active?

Expand  

Yes, I use DVLaSS, but I do not use the optional underside. I downloaded it, but upon finding that DynDOLOD 3 has it's own underside gen, I reasoned that DVLaSS's was redundant. I have never had issues and have honestly never tried to generate with DVLaSS Underside active. So I cannot speak to the error you had.

Just confirming that this is a viable option for me as well.

[Katarsi]

  On 5/20/2021 at 1:29 PM, z929669 said:

Yes, I use DVLaSS, but I do not use the optional underside. I downloaded it, but upon finding that DynDOLOD 3 has it's own underside gen, I reasoned that DVLaSS's was redundant. I have never had issues and have honestly never tried to generate with DVLaSS Underside active. So I cannot speak to the error you had.

Just confirming that this is a viable option for me as well.

Expand  

Thank you, that worked as well  

[gmahadhika91]

  On 5/12/2021 at 7:48 PM, sheson said:

Terrain is the ground you walk on. It can not really be clicked. Everything else is objects. Looking at the foggy images I probably though we looking at a rocky mountain model.

Rectangular holes in the LOD that appear/disappear when moving form one cell to the next is the broken vanilla occlusion data or outdated occlusion data.

Expand  

Hey Sheson, I've tried regenerating Occlusion but the problem persists. Thoughts? Any other things I should provide?

[sheson]

  On 5/20/2021 at 6:17 PM, gmahadhika91 said:

Hey Sheson, I've tried regenerating Occlusion but the problem persists. Thoughts? Any other things I should provide?

Expand  

Make screenshots and provide details of "the problem".