DynDOLOD 3.00 Alpha 196

[DWM19]

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

Edited August 21, 2024 by DWM19
Fixed mistake

[sheson]

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.

Thanks. Will be fixed next version.

[dionysist]

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.

[sheson]

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?

[dionysist]

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

[sheson]

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.

[dionysist]

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 August 21, 2024 by dionysist

[sheson]

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.

[dionysist]

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.

[z929669]

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:

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

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.

[sheson]

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?

[dionysist]

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 August 22, 2024 by dionysist

[aljoxo]

Alpha 178 consistently gets stuck and stalls on "exporting terrain height data" step. These logs are from me having let the program sit for ~20-30 minutes without any activity before closing the process.

I have tried doing a clean reinstall of DynDOLOD, restarting my PC, and redoing my Antivirus exceptions (Windows Defender). However, I am not quite sure what else I should be doing to try and troubleshoot this. If anyone has any thought or advice I would love to hear it.

 

Debug Log 1: https://drive.google.com/file/d/1ipqJGMscVJn_81En3AI8Tr6t1qAE06kQ/view?usp=sharing

Debug Log 2: https://drive.google.com/file/d/1RQCUuzLbnX404yeLTCP3vD7IsUryRJ_v/view?usp=sharing

DynDOLOD_SSE_log.txt DynDOLOD_SSE_log.txt

[sheson]

1 hour ago, aljoxo said:

Alpha 178 consistently gets stuck and stalls on "exporting terrain height data" step. These logs are from me having let the program sit for ~20-30 minutes without any activity before closing the process.

I have tried doing a clean reinstall of DynDOLOD, restarting my PC, and redoing my Antivirus exceptions (Windows Defender). However, I am not quite sure what else I should be doing to try and troubleshoot this. If anyone has any thought or advice I would love to hear it.

 

Debug Log 1: https://drive.google.com/file/d/1ipqJGMscVJn_81En3AI8Tr6t1qAE06kQ/view?usp=sharing

Debug Log 2: https://drive.google.com/file/d/1RQCUuzLbnX404yeLTCP3vD7IsUryRJ_v/view?usp=sharing

DynDOLOD_SSE_log.txt 1.44 MB · 1 download DynDOLOD_SSE_log.txt 735.37 kB · 1 download

Delete log folder and run this test version https://mega.nz/file/1YBEnIhC#aMSqSq3y89SvUl4vLICxWh6sLPYkEqTgGIx5w-n89ds

Upload new DynDOLOD log and debug log if issue persists.

[aljoxo]

6 hours ago, sheson said:

Delete log folder and run this test version https://mega.nz/file/1YBEnIhC#aMSqSq3y89SvUl4vLICxWh6sLPYkEqTgGIx5w-n89ds

Upload new DynDOLOD log and debug log if issue persists.

Seems the issue is still persisting. DynDOLOD is still using Memory, but the CPU usage drops down to like 1/4th to 1/5th the usage prior to the step (this is consistent with the way it was behaving on 178 as well).

Debug Log: https://drive.google.com/file/d/1MAxSqLX5BcxHnSFwfCkmygUGof-TVKGJ/view?usp=sharing

DynDOLOD_SSE_log.txt

 

Edit: tested alpha 173 and it seems to at least be making progress on the "exporting terrain height" step that 178/179test were stuck on, successfully moving on to creating texture atlases and generating tree LOD + dynamic LOD. Should note I am using the x64 version on Alpha 173.

Edit 2: alpha 173 blue screened my PC

Edit 3: successfully generated LODs on alpha 177

Edited August 23, 2024 by aljoxo
added information regarding running a test on alpha173 and alpha177