DynDOLOD 3.00 Alpha 190

[leostevano]

Hi sheson, I just generated output with the new alpha. But it seems dragon's reach lod is bugged out. I didn't get any error except textures doesn't match warnings.

Screenshot : https://pasteboard.co/y5ZkqKJnVW2B.png

Logs : https://ufile.io/q2v18fr5

[sheson]

  On 12/21/2023 at 9:01 AM, PRieST said:

The culprit is this in Skyrimprefs.ini under [General]

uLargeRefLODGridSize=11

Without that line everything looks fine.
But why? This wasn't a problem with earlier alpha versions.
This is from the DynDOLOD_SSE.ini:

; Because Bethesda simply does not comprehend people are modding exterior worldspaces ...
; set to 1 if uLargeRefLODGridSize=5 (value of uGridsToLoad) in SkyrimPrefs.ini, do this if it is certain that the large references system will not be used, so that no DynDOLOD.esm is created
; set to 0 if uLargeRefLODGridSize>5 (value of uGridsToLoad) in SkyrimPrefs.ini
IgnoreLargeReferences=0

Expand  

Removing a setting from the INI, means its default value is used in the game.
You can check it with console getini "uLargeRefLODGridSize:General"
Do not remove the setting, simply leave it at 11. All large references should be shown up to its distance.

The uLargeRefLODGridSize setting does not affect LOD generation. Whatever its setting it should not affect terrain LOD that was also shown missing in your initial screenshots.

Upload a BTO from an area that you believe has issues.

[PRieST]

  On 12/21/2023 at 11:26 AM, sheson said:

You can check it with console getini "uLargeRefLODGridSize:General"

Expand  

(Maybe a dumb question, because I could just have tried both ways) With or without quotation marks? Because with it I just get "unknown type"
https://ibb.co/tbj0kgm
But I checked, if I get the default SkyrimPrefs.ini, what the value is and it is set to 5 (which is working). In my case setting it higher as 5 it breaks somehow the LOD display.

  Quote

The uLargeRefLODGridSize setting does not affect LOD generation.

Expand  

Generation was fine, but the display ingame is the culprit.

  Quote

Upload a BTO from an area that you believe has issues.

Expand  

https://www.file-upload.net/download-15241320/Tamriel.4.4.-8.7z.html

Definetly that one (the same spot jus looking left if you compare it to the screenshots). But as far as I can tell the .bto looks absolutely correct.

Edit:
Comparison between

uLargeRefLODGridSize=5

https://ibb.co/wR6FT1M
https://ibb.co/Bs8cYRd

uLargeRefLODGridSize=7

https://ibb.co/t3hRkbP
https://ibb.co/dpK5Xy4

uLargeRefLODGridSize=9

https://ibb.co/Nr2PX9C
https://ibb.co/0K1tYgh

and

uLargeRefLODGridSize=11

https://ibb.co/kXKDCZV
https://ibb.co/Bcs1jxd

Edited December 21, 2023 by PRieST

[sheson]

  On 12/21/2023 at 11:41 AM, PRieST said:

(Maybe a dumb question, because I could just have tried both ways) With or without quotation marks? Because with it I just get "unknown type"
https://ibb.co/tbj0kgm
But I checked, if I get the default SkyrimPrefs.ini, what the value is and it is set to 5 (which is working). In my case setting it higher as 5 it breaks somehow the LOD display.

Generation was fine, but the display ingame is the culprit.

https://www.file-upload.net/download-15241320/Tamriel.4.4.-8.7z.html

Definetly that one (the same spot jus looking left if you compare it to the screenshots). But as far as I can tell the .bto looks absolutely correct.

Expand  

This should be fixed generating the L:OD patch with Alpha-162.

[PRieST]

Ok, will give it a try, thank you.
What was the issue if I may ask? For me it looks like the display between uLargeRefLODGridSize 5 -> 11 was 'switched' /the wrong way round?

[leostevano]

  On 12/21/2023 at 11:26 AM, sheson said:

Removing a setting from the INI, means its default value is used in the game.
You can check it with console getini "uLargeRefLODGridSize:General"
Do not remove the setting, simply leave it at 11. All large references should be shown up to its distance.

The uLargeRefLODGridSize setting does not affect LOD generation. Whatever its setting it should not affect terrain LOD that was also shown missing in your initial screenshots.

Upload a BTO from an area that you believe has issues.

Expand  

Here you go, from this point Dragon's Reach is missing https://ufile.io/nmqg7wte

Screenshot : https://pasteboard.co/eQ95OQ2dDtXh.bmp

[sheson]

  On 12/21/2023 at 9:02 AM, leostevano said:

Hi sheson, I just generated output with the new alpha. But it seems dragon's reach lod is bugged out. I didn't get any error except textures doesn't match warnings.

Screenshot : https://pasteboard.co/y5ZkqKJnVW2B.png

Logs : https://ufile.io/q2v18fr5

Expand  

This should be fixed in Alpha-162.

[leostevano]

  On 12/21/2023 at 12:19 PM, sheson said:

This should be fixed in Alpha-162.

Expand  

That was fast, many thanks!

[PRieST]

  On 12/21/2023 at 12:15 PM, sheson said:

This should be fixed generating the L:OD patch with Alpha-162.

Expand  

Can confirm, it's fixed, thank you again.

[leostevano]

I just noticed both dyndolod.esp and occlusion.esp doesnt carry over worldspace records. Is this intended?

[PRieST]

Yes, this is of the 'new' 'partial form' flag.
If the worldspace itself doesn't need to be edited (in which case we are here) you can set this flag and so the worldspace data doesn't get overwritten by DynDOLOD.esp/Occlusion.esp. That's why you also see no records inside these two plugins for the worldspaces.
That's a feature which was forever in the engine, but only recently included in xEdit and now DynDOLOD makes also use of it.

Edited December 22, 2023 by PRieST

[sheson]

  On 12/22/2023 at 12:29 PM, leostevano said:

I just noticed both dyndolod.esp and occlusion.esp doesnt carry over worldspace records. Is this intended?

Expand  

If you have questions how/why xEdit displays certain records the way it does, then check its documentation and/or ask on its Discord.
The records are not being overwritten because they have the partial form flag set.

See https://dyndolod.info/Changelog for Alpha-160
DynDOLOD.exe - added support for Partial Form flag
DynDOLOD.exe - added PartialWorldspace and PartialPersistentCell INI settings to set the partial form flag on these overwrite records in the DynDOLOD and occlusion plugins

In the changelog entry, you can hover the term Partial Form Flag for a hint or check https://dyndolod.info/Terminology:
Records that have the Partial Form flag set do not overwrite the data of the record from the plugin loaded before them. Only a few record types support it.

[leostevano]

Sorry I just made a new bashed patch, and usually I manually patch certain things and I remembered those records were forwarded before, I thought I messed up something during my output generation. Thank you for the assistance.

[aufisch]

Range Check Error on a Book Display??? I have just ran into a problem with a range check error on a book display from the mod "Immersive College of Winterhold". This mod hasn't changed in a while and has never in all the year been the cause for a Dyndolod Error. Checking it with xEdit doesn't throw an error either.

I am also slightly irritated as to why DynDOLOD would even process a book-display (static Item)? And I have no Idea as to how I would fix this error, as there doesn't seem to be anything wrong with that item?

DynDOLOD_SSE_log.txtFetching info...

[sheson]

  On 12/22/2023 at 6:38 PM, aufisch said:

Range Check Error on a Book Display??? I have just ran into a problem with a range check error on a book display from the mod "Immersive College of Winterhold". This mod hasn't changed in a while and has never in all the year been the cause for a Dyndolod Error. Checking it with xEdit doesn't throw an error either.

I am also slightly irritated as to why DynDOLOD would even process a book-display (static Item)? And I have no Idea as to how I would fix this error, as there doesn't seem to be anything wrong with that item?

DynDOLOD_SSE_log.txt 2.33 MB · 0 downloads

Expand  

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Posts-Logs which debug log and bugreport.txt if it exists to also upload.

https://dyndolod.info/Messages/Exceptions#Range-check-error
This is a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

Do not install newer versions over older versions. See https://dyndolod.info/Installation-Instructions
Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\.

https://dyndolod.info/Updating#New-DynDOLOD-Version

How do you suppose a human or program knows what the STAT base record with the form ID 5C227B42 is and where it is used without loading and checking the record?