DynDOLOD 3.00 Alpha 180

[sheson]

17 minutes ago, MitchBandito said:

Hi,

I'm here because I'm a little bit desperate... The new update of No grass in object for AE is amazing, I have beautiful grass LODs but now I have a new problem...

I will try to explain it. You can see grass LOD in the distance but the loaded grass near the player is fading before disappearing completely when walking away. Please watch the video for more details.

May someone help me please, it makes me have nightmares.

DynDOLOD does not do anything to full grass. Set the appropriated settings in NGIO GrassControl.config.txt to control full grass and its max render distance.

https://dyndolod.info/Help/Grass-LOD
With No Grass In Objects full grass can be rendered past the active cells, so Grass LOD can either start right beyond the active exterior cells (uGridsToLoad), which has better for performance - or beyond the large reference distance (uLargeRefLODGridSize). The DynDOLODGrassMode/DynDOLOD-Grass-Mode 1 or 2 setting controls the distance of full grass respectively.
Set the same desired Mode in the advanced mode of DynDOLOD under the Grass LOD checkbox and for DynDOLODGrassMode/DynDOLOD-Grass-Mode in the settings file. While the DynDOLODGrassMode/DynDOLOD-Grass-Mode setting can be changed at any time, the Mode used to generate grass LOD is baked into the object LOD meshes.

If you have problems with full grass and NGIO, you need to ask on the NGIO forum or comments.

[KRZ]

13 hours ago, sheson said:

If you are absolutely sure that the load order did not change after generating the output with alpha 170 let me know for follow up questions/troubleshooting..

Otherwise, generate a LOD patch from scratch with the latest alpha for the current load order, to verify that the crash still happens.
If it does, upload new DynDOLOD log and debug log and new crash log and keep the output around for follow up questions/troubleshooting.

Welp, you were right that my LO had changed - I've been wondering about that cause the RAM address was different in those crash logs. Below I've attached all logs from a new A170 run with identical LO this time (also identical to A169). Sadly the crashes persisted. I've also tested whether crashes would occur in Markarth, Windhelm or Solitude as well and they didn't (or I just haven't found the spot).

DynDOLOD_SSE_Debug: https://mega.nz/file/IGtykIzI#j9kKzjggkK3vStV3a9oIAQIjyyzQurM66J_OjvCuM0M
 

Logs.zip

Edited June 5 by KRZ

[sheson]

55 minutes ago, KRZ said:

Welp, you were right that my LO had changed - I've been wondering about that cause the RAM address was different in those crash logs. Below I've attached all logs from a new A170 run with identical LO this time (also identical to A169). Sadly the crashes persisted. I've also tested whether crashes would occur in Markarth, Windhelm or Solitude as well and they didn't (or I just haven't found the spot).

DynDOLOD_SSE_Debug: https://mega.nz/file/IGtykIzI#j9kKzjggkK3vStV3a9oIAQIjyyzQurM66J_OjvCuM0M

Logs.zip 1.18 MB · 0 downloads

The mentioned records are parent > child copies. There should not be really anything different between the references/base records in Alpha 169 and 170.

Lets just look at one crash log: crash-2024-06-05-08-57-45.log
Base record WRHouseStables01 with form ID 0x000627AA
used by reference 0x130BAEC0 in DynDOLOD.esm

Since you have both outputs, do the following:

Lookup the reference in xEdit by its EditorID in DynDOLOD.esm in both outputs. Enter skyrimesm_099F21_WhiterunWorld_DynDOLOD_PARENT_DynDOLOD_NOLO into the Editor ID field top left of xEdit and hit Enter key and wait for it to find it. Obviously it should find the reference 0x130BAEC0 for the output put from 170. The form ID will different in the DynDOLOD.esm for the output of 169.

Compare the references if there is anything different.
Both should use the same base record 0x000627AA in Skyrim.esm, which seems not to be overwritten by any plugin and define Architecture\WhiteRun\WRBuildings\WRHouseStables01.nif. It (and any textures it uses) should also be identical for both load orders. Let me know in case this is not the vanilla NIF and if it comes from a mod and which.

If so far you haven't found a difference compare, check the Cell 0x00071E94 the reference resides in and compare the overwrites in the DynDOLOD.esm and Occlussion.esp for both output if there is anything different.

Let me know if you can spot anything different or obvious errors or if everything looks the same.

[MitchBandito]

1 hour ago, sheson said:

DynDOLOD does not do anything to full grass. Set the appropriated settings in NGIO GrassControl.config.txt to control full grass and its max render distance.

https://dyndolod.info/Help/Grass-LOD
With No Grass In Objects full grass can be rendered past the active cells, so Grass LOD can either start right beyond the active exterior cells (uGridsToLoad), which has better for performance - or beyond the large reference distance (uLargeRefLODGridSize). The DynDOLODGrassMode/DynDOLOD-Grass-Mode 1 or 2 setting controls the distance of full grass respectively.
Set the same desired Mode in the advanced mode of DynDOLOD under the Grass LOD checkbox and for DynDOLODGrassMode/DynDOLOD-Grass-Mode in the settings file. While the DynDOLODGrassMode/DynDOLOD-Grass-Mode setting can be changed at any time, the Mode used to generate grass LOD is baked into the object LOD meshes.

If you have problems with full grass and NGIO, you need to ask on the NGIO forum or comments.

Thank you so much for your answer 🙏

[KRZ]

3 hours ago, sheson said:

The mentioned records are parent > child copies. There should not be really anything different between the references/base records in Alpha 169 and 170.

Lets just look at one crash log: crash-2024-06-05-08-57-45.log
Base record WRHouseStables01 with form ID 0x000627AA
used by reference 0x130BAEC0 in DynDOLOD.esm

Since you have both outputs, do the following:

Lookup the reference in xEdit by its EditorID in DynDOLOD.esm in both outputs. Enter skyrimesm_099F21_WhiterunWorld_DynDOLOD_PARENT_DynDOLOD_NOLO into the Editor ID field top left of xEdit and hit Enter key and wait for it to find it. Obviously it should find the reference 0x130BAEC0 for the output put from 170. The form ID will different in the DynDOLOD.esm for the output of 169.

Compare the references if there is anything different.
Both should use the same base record 0x000627AA in Skyrim.esm, which seems not to be overwritten by any plugin and define Architecture\WhiteRun\WRBuildings\WRHouseStables01.nif. It (and any textures it uses) should also be identical for both load orders. Let me know in case this is not the vanilla NIF and if it comes from a mod and which.

If so far you haven't found a difference compare, check the Cell 0x00071E94 the reference resides in and compare the overwrites in the DynDOLOD.esm and Occlussion.esp for both output if there is anything different.

Let me know if you can spot anything different or obvious errors or if everything looks the same.

Sorry for taking so long, xEdit reported a patch causing errors, so I replaced it and ran Alpha 170 again to see whether that's been the culprit - it was not. I've included a comparison shot of both entries below (Alpha 169 on the left, Alpha 170 on the right). I can't really spot a difference, however it appears that in Alpha 170's output skyrimesm_099F21_WhiterunWorld_DynDOLOD_PARENT_DynDOLOD_NOLO doesn't actually get referenced by anything opposed to Alpha 169's output, which has exactly one reference.

The WRHouseStables01.nif is from this mod https://www.nexusmods.com/skyrimspecialedition/mods/120159

Edited June 5 by KRZ

[sheson]

1 hour ago, KRZ said:

Sorry for taking so long, xEdit reported a patch causing errors, so I replaced it and ran Alpha 170 again to see whether that's been the culprit - it was not. I've included a comparison shot of both entries below (Alpha 169 on the left, Alpha 170 on the right). I can't really spot a difference, however it appears that in Alpha 170's output skyrimesm_099F21_WhiterunWorld_DynDOLOD_PARENT_DynDOLOD_NOLO doesn't actually get referenced by anything opposed to Alpha 169's output, which has exactly one reference.

The WRHouseStables01.nif is from this mod https://www.nexusmods.com/skyrimspecialedition/mods/120159

Error check the DynDOLOD and Occlusion plugins in xEdit.

To be sure, test without the mod / hide the model so that the vanilla model is used. I do not expect that to make a difference.

Report if anything overwrite the original reference 00099F21.

[KRZ]

43 minutes ago, sheson said:

Error check the DynDOLOD and Occlusion plugins in xEdit.

To be sure, test without the mod / hide the model so that the vanilla model is used. I do not expect that to make a difference.

Report if anything overwrite the original reference 00099F21.

I'm getting a couple of errors with both Alpha 169 and Alpha 170, but it's hard to tell whether that isn't caused by me replacing that one patch and adding 3 more patches which had been chosen by the FOMOD. Should I create a new Output for Alpha 169 as well to maintain consistency or does it not matter? I had to replace the patch or xEdit would have thrown a fit and I couldn't check for errors etc.

I've attached the findings anyways, but if I have to do another round let me know.

 

Launching without the mod/model did nothing.

Nothing touches the original reference 00099F21.

Error check.txt

[sheson]

14 hours ago, KRZ said:

I'm getting a couple of errors with both Alpha 169 and Alpha 170, but it's hard to tell whether that isn't caused by me replacing that one patch and adding 3 more patches which had been chosen by the FOMOD. Should I create a new Output for Alpha 169 as well to maintain consistency or does it not matter? I had to replace the patch or xEdit would have thrown a fit and I couldn't check for errors etc.

I've attached the findings anyways, but if I have to do another round let me know.

 

Launching without the mod/model did nothing.

Nothing touches the original reference 00099F21.

Error check.txt 638.44 kB · 1 download

The Unknown 2 are expected.

The unresolved Form ID are a problem. This should not happen right after patch generation. So if you generate again with 170, check it right after. For troubleshooting I do not need a new 169 for now.

[KRZ]

14 hours ago, sheson said:

The Unknown 2 are expected.

The unresolved Form ID are a problem. This should not happen right after patch generation. So if you generate again with 170, check it right after. For troubleshooting I do not need a new 169 for now.

Once again everything's brand new, including TerrainLOD this time, but the crashes persist.

DynDOLOD_SSE_Debug: https://mega.nz/file/FDlAwDTa#pI9vxOzqgJoBPAB8x5lMWILKdnqLzjxsXwmVdZ6QzQU

 

Fwiw, I've noticed there are a ton of 0D and FE005 FormIDs in xEdit's error report, which are

evgSirenroot.esm https://www.nexusmods.com/skyrimspecialedition/mods/70917 and

Landscape and Water Fixes.esp https://www.nexusmods.com/skyrimspecialedition/mods/26138 in my LO.
I wonder whether that's related somehow.

 

Peculiar, I've done another Alpha 170 output without Sirenroot and Landscape and Water Fixes, but while all the 0D errors are gone, the FE005 have changed. Everything related to this is in Logs 2 & DynDOLOD_SSE_Debug 2.

DynDOLOD_SSE_Debug 2: https://mega.nz/file/9XsBEADa#mMWBomfMs2suBL9rzJLxHOQwFrVpbDRO3ifMmHFhaBs

 

Logs.zip

Logs 2.zip

[Jonado]

17 hours ago, sheson said:

Yes you are correct, both BOS and DynDOLOD also sort the BOS INIs alphabetical. Same issue with the case sensitivity though - that I double checked with the logs. So that will be fixed as well.

I thought as much. Just want to make sure you get it right this time, though. Intuitively I think the order should be _AaBbCc..., not ABC...XYZ_abc... as you claimed it is. At least I think that is the sorting that is used on Windows.

[sheson]

8 hours ago, Jonado said:

I thought as much. Just want to make sure you get it right this time, though. Intuitively I think the order should be _AaBbCc..., not ABC...XYZ_abc... as you claimed it is. At least I think that is the sorting that is used on Windows.

xEdit  ignores the case filenames of assets by default, so I'll change that for when reading these INIs. Windows Explorer sorts case insensitive, too since by default filenames are case insensitive. Sorting is usually based on the ASCII order in programming context. The logs report this:

INI : Data\AB_SWAP.ini
INI : Data\Aa_SWAP.ini
INI : Data\B_SWAP.ini
INI : Data\a_SWAP.ini

INI : Data\Seasons\AB_WIN.ini
INI : Data\Seasons\Aa_WIN.ini
INI : Data\Seasons\B_WIN.ini
INI : Data\Seasons\a_WIN.ini

[sheson]

13 hours ago, KRZ said:

Once again everything's brand new, including TerrainLOD this time, but the crashes persist.

DynDOLOD_SSE_Debug: https://mega.nz/file/FDlAwDTa#pI9vxOzqgJoBPAB8x5lMWILKdnqLzjxsXwmVdZ6QzQU

Fwiw, I've noticed there are a ton of 0D and FE005 FormIDs in xEdit's error report, which are

evgSirenroot.esm https://www.nexusmods.com/skyrimspecialedition/mods/70917 and

Landscape and Water Fixes.esp https://www.nexusmods.com/skyrimspecialedition/mods/26138 in my LO.
I wonder whether that's related somehow.

Peculiar, I've done another Alpha 170 output without Sirenroot and Landscape and Water Fixes, but while all the 0D errors are gone, the FE005 have changed. Everything related to this is in Logs 2 & DynDOLOD_SSE_Debug 2.

DynDOLOD_SSE_Debug 2: https://mega.nz/file/9XsBEADa#mMWBomfMs2suBL9rzJLxHOQwFrVpbDRO3ifMmHFhaBs

Logs.zip 1.21 MB · 1 download

Logs 2.zip 1.15 MB · 1 download

Lets continue with the generation without Sirenroot and Landscape and Water Fixes. Upload that DynDOLOD.esm

In the meantime, if you are so inclined, could you doublecheck no such errors exist after generation with 169?

[KRZ]

1 hour ago, sheson said:

Lets continue with the generation without Sirenroot and Landscape and Water Fixes. Upload that DynDOLOD.esm

In the meantime, if you are so inclined, could you doublecheck no such errors exist after generation with 169?

I'll get back to you once 169 output is generated

DynDOLOD.esm

[KRZ]

2 hours ago, sheson said:

Lets continue with the generation without Sirenroot and Landscape and Water Fixes. Upload that DynDOLOD.esm

In the meantime, if you are so inclined, could you doublecheck no such errors exist after generation with 169?

To keep it short, there's no errors besides the Unknown: 2, which are expected. For sake of completion I've included it regardless.

DynDOLOD_SSE_Debug: https://mega.nz/file/gX1RXL6C#uZKEtw9HJCBm72IbmBkq5LNln1E1j6PDS5Hb675C5EE

 

Edit: It's probably a reach, but I wanna try it anyways: I've deleted a ton of entries from Fabled Forests cause I only wanted the additional tree placement, but never actually cleaned the plugin. I just did and it removed 2000 something identical to master records. I'll try another Alpha 170 and see what's going to happen. Nevermind, nothing's changed
 

Logs Alpha 169 (new 2).zip DynDOLOD.esm

Edited June 6 by KRZ

[sheson]

8 hours ago, KRZ said:

To keep it short, there's no errors besides the Unknown: 2, which are expected. For sake of completion I've included it regardless.

DynDOLOD_SSE_Debug: https://mega.nz/file/gX1RXL6C#uZKEtw9HJCBm72IbmBkq5LNln1E1j6PDS5Hb675C5EE

 

Edit: It's probably a reach, but I wanna try it anyways: I've deleted a ton of entries from Fabled Forests cause I only wanted the additional tree placement, but never actually cleaned the plugin. I just did and it removed 2000 something identical to master records. I'll try another Alpha 170 and see what's going to happen. Nevermind, nothing's changed
 

Logs Alpha 169 (new 2).zip 1.15 MB · 2 downloads DynDOLOD.esm

Let me know if this test version makes a difference https://mega.nz/file/JMhCEbhI#7lnJ2qwh-K00Uk1zIflcQEEEBQNqHHiLXy9V2y78Xf0