leostevano Posted December 21, 2023 Posted December 21, 2023 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 Posted December 21, 2023 Author Posted December 21, 2023 Just now, 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 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 Posted December 21, 2023 Posted December 21, 2023 (edited) 31 minutes ago, sheson said: You can check it with console getini "uLargeRefLODGridSize:General" (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. Generation was fine, but the display ingame is the culprit. Quote Upload a BTO from an area that you believe has issues. 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 Posted December 21, 2023 Author Posted December 21, 2023 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.
PRieST Posted December 21, 2023 Posted December 21, 2023 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 Posted December 21, 2023 Posted December 21, 2023 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
sheson Posted December 21, 2023 Author Posted December 21, 2023 Just now, 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 This should be fixed in Alpha-162.
leostevano Posted December 21, 2023 Posted December 21, 2023 Just now, sheson said: This should be fixed in Alpha-162. That was fast, many thanks!
PRieST Posted December 21, 2023 Posted December 21, 2023 40 minutes ago, sheson said: This should be fixed generating the L:OD patch with Alpha-162. Can confirm, it's fixed, thank you again.
leostevano Posted December 22, 2023 Posted December 22, 2023 I just noticed both dyndolod.esp and occlusion.esp doesnt carry over worldspace records. Is this intended?
PRieST Posted December 22, 2023 Posted December 22, 2023 (edited) 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 Posted December 22, 2023 Author Posted December 22, 2023 53 minutes ago, leostevano said: I just noticed both dyndolod.esp and occlusion.esp doesnt carry over worldspace records. Is this intended? 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 Posted December 22, 2023 Posted December 22, 2023 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 Posted December 22, 2023 Posted December 22, 2023 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
sheson Posted December 22, 2023 Author Posted December 22, 2023 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?
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now