Jump to content

DynDOLOD 3.00 Alpha 182


sheson

Recommended Posts

This is not a typical issue, but I made a new worldspace and wanted to generate LOD for it. I've done this before successfully but this time I tried it, it failed to work, as can be seen in the picture I attached. I had added new mountain meshes but the only edits I made were to change the texture file paths in nifskope. I made sure in the plugin the correct LOD models were connected to their static records (which are vanilla LOD also with new texture paths). After running DynDOLOD on a completely vanilla profile minus the absolutely necessary files/mods, it added something in the back but nothing else, not even the terrain. Everything ran smoothly and the only error I got was that I needed to clean a deleted record in Dawnguard.esm. Since I've done this for new world spaces before, I believe I did everything correctly (with the .lod file with the name of my worldspace). I do not know if this was on my end or something else?

 

The Elder Scrolls V  Skyrim Special Edition Screenshot 2024.08.18 - 01.21.43.69.png

LODGen_SSE_KR2Deadlands_log.txt DynDOLOD_SSE_TexturesUsed_KR2Deadlands.txt LODGen_SSE_KR2Deadlands_TerrainUnderside_log.txt DynDOLOD_SSE_Debug_log_COPY.docx

Link to comment
Share on other sites

21 minutes ago, kn1ghtradiant said:

This is not a typical issue, but I made a new worldspace and wanted to generate LOD for it. I've done this before successfully but this time I tried it, it failed to work, as can be seen in the picture I attached. I had added new mountain meshes but the only edits I made were to change the texture file paths in nifskope. I made sure in the plugin the correct LOD models were connected to their static records (which are vanilla LOD also with new texture paths). After running DynDOLOD on a completely vanilla profile minus the absolutely necessary files/mods, it added something in the back but nothing else, not even the terrain. Everything ran smoothly and the only error I got was that I needed to clean a deleted record in Dawnguard.esm. Since I've done this for new world spaces before, I believe I did everything correctly (with the .lod file with the name of my worldspace). I do not know if this was on my end or something else?

 

The Elder Scrolls V  Skyrim Special Edition Screenshot 2024.08.18 - 01.21.43.69.png

LODGen_SSE_KR2Deadlands_log.txt 2.25 kB · 0 downloads DynDOLOD_SSE_TexturesUsed_KR2Deadlands.txt 2.74 kB · 0 downloads LODGen_SSE_KR2Deadlands_TerrainUnderside_log.txt 866 B · 0 downloads DynDOLOD_SSE_Debug_log_COPY.docx 992.03 kB · 0 downloads

Do not put txt files into word documents. Zip the debug log or upload it as is.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log to also upload in addition to the debug log.
Also upload F:\NOLVUS2\Tools\DynDOLOD\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt

Make a useful screenshot of the full model that has no object LOD representation with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots

DynDOLOD does not generate terrain LOD. See https://dyndolod.info/Help/xLODGen

Link to comment
Share on other sites

11 minutes ago, sheson said:

Do not put txt files into word documents. Zip the debug log or upload it as is.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log to also upload in addition to the debug log.
Also upload F:\NOLVUS2\Tools\DynDOLOD\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt

Make a useful screenshot of the full model that has no object LOD representation with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots

DynDOLOD does not generate terrain LOD. See https://dyndolod.info/Help/xLODGen

Sorry about that. I'll pay closer attention next time. But, this can be disregarded: I had forgotten to uncheck the option to make the worldspace a fixed size. Thanks for the hardwork.

Link to comment
Share on other sites

  • sheson changed the title to DynDOLOD 3.00 Alpha 178

Incredible program, fantastic LOD results! Maybe minor, but may as well mention it: there's a spelling mistake under Grid on line Full.

Screenshot 2024-08-21 164918.png

Edited by DWM19
Fixed mistake
Link to comment
Share on other sites

43 minutes ago, DWM19 said:

Incredible program, fantastic LOD results! Maybe minor, but may as well mention it: there's a spelling mistake under Grid on line Full.

Screenshot 2024-08-21 164918.png

Thanks. Will be fixed next version.

Link to comment
Share on other sites

Latest version Alpha 178:

I have fBlockLevel0Distance=53248.0000 set in SkyrimPrefs.ini (which I have set as read-only). However, in game when I check in the DynDOLOD MCM, it shows as set to fBlockLevel0Distance=100000. I do not have any other inis that might overwite the settings (that I can find anyway).

Curious if anyone has any idea what might be causing this.

Link to comment
Share on other sites

4 minutes ago, dionysist said:

Latest version Alpha 178:

I have fBlockLevel0Distance=53248.0000 set in SkyrimPrefs.ini (which I have set as read-only). However, in game when I check in the DynDOLOD MCM, it shows as set to fBlockLevel0Distance=100000. I do not have any other inis that might overwite the settings (that I can find anyway).

Curious if anyone has any idea what might be causing this.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making post. Also upload the papyrus log.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting

What does console getini "fBlockLevel0Distance:TerrainManager" report when checking on main menu after launching the game?

Link to comment
Share on other sites

6 minutes ago, dionysist said:

logs: https://ufile.io/f/d2vq3

I have bEnableLogging=1 in the skyrim.ini, but no papyrus log is being generated.

getini "fBlockLevel0Distance:TerrainManager" shows the value as 100000

That explains why the DynDOLOD SkyUI MCM Settings page reports that number, since that is what the INI setting is set to.

Seems likely you are not editing the correct INIs on both those accounts.
Since you are starting from MO2, make sure to use its build-in INI Editor under menu Tools. Tools Plugin, INI Editor which should edit the correct INIs, typically in the profile folder.

Link to comment
Share on other sites

Thank you.

The MO2 built-in ini editor shows the following values:

[TerrainManager]

bShowLODInEditor=1

fBlockLevel0Distance=53248

fBlockLevel1Distance=114688

fBlockMaximumDistance=262144

fSplitDistanceMult=1.0

fTreeLoadDistance=0

Edited by dionysist
Link to comment
Share on other sites

48 minutes ago, dionysist said:

Thank you.

The MO2 built-in ini editor shows the following values:

[TerrainManager]

bShowLODInEditor=1

fBlockLevel0Distance=53248

fBlockLevel1Distance=114688

fBlockMaximumDistance=262144

fSplitDistanceMult=1.0

fTreeLoadDistance=0

Double check for SkyrimCustom.ini etc.

Maybe there is an issue with MO2 or the general setup of the game. I would enable its debug log and check it for the requests to *.INI.

Link to comment
Share on other sites

1 hour ago, sheson said:

Double check for SkyrimCustom.ini etc.

Maybe there is an issue with MO2 or the general setup of the game. I would enable its debug log and check it for the requests to *.INI.

I couldn't find anything useful in the MO2 debug log.

I changed the setting to use profile specific ini files. I then deleted the terrain manager settings. The DynDOLOD MCM still shows those same values. I can't for the life of me figure out where they are pulling from.

Link to comment
Share on other sites

4 hours ago, dionysist said:

I couldn't find anything useful in the MO2 debug log.

I changed the setting to use profile specific ini files. I then deleted the terrain manager settings. The DynDOLOD MCM still shows those same values. I can't for the life of me figure out where they are pulling from.

They are coming from the MO profile:

image.png

As mentioned, check that SkyrimCustom.ini does not have the persistent values set.

image.png

Otherwise, they could be coming from some mod you have installed that thinks setting [Terrainmanager] settings is a good idea. In that mod you will find an INI file named the same as the plugin.

image.png

Link to comment
Share on other sites

7 hours ago, dionysist said:

I couldn't find anything useful in the MO2 debug log.

I changed the setting to use profile specific ini files. I then deleted the terrain manager settings. The DynDOLOD MCM still shows those same values. I can't for the life of me figure out where they are pulling from.

DynDOLOD shows the same value as the game has stored which you have verified with the console command.
The console command shows the same value regardless of DynDOLOD being active in the load order or not, correct?

Link to comment
Share on other sites

A quick thank you to sheson and z929669 for the assistance.

First of all, it is not DynDOLOD. After disabling that and running getini, the value was the same 100,000. I then disabled all mods that I have installed since my last play through, as well as deleting all three of the ini files so they would be recreated. The issue persisted!

I then created a new profile, just base game no mods. The getini command showed the correct value of 53248! So yes, it is some mod. I have search within text files enabled on my PC and searched for "fblocklevel0distance" in all files, still couldn't find the culprit.

I'll keep working to figure this out.

Again, huge thank you and my apologies for taking your time. I thought it might be something with the latest version of DynDOLOD since I had just upgraded before seeing the issue.

Edited by dionysist
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.