Jump to content

DynDOLOD 3.00 Alpha 180


sheson

Recommended Posts

Just now, 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.

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

Link to comment
Share on other sites

47 minutes ago, 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.

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

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

Link to comment
Share on other sites

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 by PRieST
Link to comment
Share on other sites

53 minutes ago, leostevano said:

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

image.thumb.png.e715b89bd23ed6ca5bad2feb85b09617.png

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.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

1 hour ago, 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

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?

Link to comment
Share on other sites

Sorry if I sounded disrespectful. I don't know how DynDOLOD works, I always assumed it would only process certain pre-defined records, but it makes sense that it would process all of static records. I have since tried again twice, and it went through the third time.

I have uploaded the corresponding bugreport.txt, but I don't have the original debug log anymore as it got overwritten. I uploaded the last debug log (of the successful run) anyway as neither my modlist, nor the load-order has changed since.

debug log: https://ufile.io/a5ixrhqm

Bugreport: https://ufile.io/x5tak6wt

Link to comment
Share on other sites

Thanks for all the effort you put into Dyndolod

Observation: grass lods on the sides of grassy hills (hillside is greater than maybe 35 degree angle) are seen more from the top of the model than the side, especially when you are on a different hill and thus viewing from above.  The effect is obviously "X" - shaped things littered on hillsides that I know are grass lods but don't resemble grass at all from that viewing angle.  This is most egregious in the Reach where there are lots of grassy hills and not so many trees to block the view.  

My suggestion is to have an option to rotate all grass lod models on their axis when rendering Dyndolod so they are always fully upright instead of whatever angle/slant the actual grass plant will be when you enter the active cell: that way the side of the model should always be more visible than the top.

Thanks again!

Link to comment
Share on other sites

5 hours ago, aufisch said:

Sorry if I sounded disrespectful. I don't know how DynDOLOD works, I always assumed it would only process certain pre-defined records, but it makes sense that it would process all of static records. I have since tried again twice, and it went through the third time.

I have uploaded the corresponding bugreport.txt, but I don't have the original debug log anymore as it got overwritten. I uploaded the last debug log (of the successful run) anyway as neither my modlist, nor the load-order has changed since.

debug log: https://ufile.io/a5ixrhqm

Bugreport: https://ufile.io/x5tak6wt

It's probably a race condition. If you come across it again, upload the new debug log and bugreport.txt.

See https://dyndolod.info/DynDOLOD-Reference#3-Scan-base-records. It scans all base records of certain types which might be eligible for LOD.

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.