DynDOLOD 3.00 Alpha 196

[PurpleYellowRosa]

The process runs for about 42 minutes, then bugs out after finishing Object LOD for Tamriel (and seasons). It's likely from a mod I installed, since the error happens on multiple DynDOLOD versions, I'm just having trouble identifying exactly which mod. My last successful run was two days ago, so potentially I could binary test it, but I'd prefer to try to document the process and actually "solve" what's causing it.

My debug log is about 840 MB, so I'm attaching the final section in hopes that it can help.

Quote

[20:06] [DoObjectLOD] <Debug: Adding mini atlasses 268 616>
[20:06] [SaveAtlasMap] <Debug: Saving C:\DynDOLOD\Edit Scripts\Export\LODGen_SSE_ObjectAtlasMap_DLC2SolstheimWorld.txt>
[20:06] [SaveList] <Debug: Saving C:\DynDOLOD\Edit Scripts\Export\LODGen_SSE_ObjectAtlasMap_DLC2SolstheimWorld.txt>
[21:23] [TwbRender.MakeCurrent] <Debug: Enter MC -268367539 131072>
[21:23] [TwbRender.MakeCurrent] <Debug: Leave MC -268367539 131072>
[21:23] [TwbRender.MakeCurrent] <Debug: Enter MC 0 0>
[21:23] [TwbRender.MakeCurrent] <Debug: Leave MC 0 0>
[21:23] [TwbRender.MakeCurrent] <Debug: Enter MC -268367539 131072>
[21:23] [TwbRender.MakeCurrent] <Debug: Leave MC -268367539 131072>
[21:23] [TwbRender.MakeCurrent] <Debug: Enter MC 0 0>
[21:23] [TwbRender.MakeCurrent] <Debug: Leave MC 0 0>
[21:23] [TwbRender.MakeCurrent] <Debug: Enter MC -268367539 131072>
[21:23] [TwbRender.MakeCurrent] <Debug: Leave MC -268367539 131072>
[21:23] [TwbRender.MakeCurrent] <Debug: Enter MC 0 0>
[21:23] [TwbRender.MakeCurrent] <Debug: Leave MC 0 0>
[21:23] [TwbRender.MakeCurrent] <Debug: Enter MC -268367539 65538>
[21:23] [TwbRender.MakeCurrent] <Debug: Leave MC -268367539 65538>
[21:23] [TwbRender.MakeCurrent] <Debug: Enter MC 0 0>
[21:23] [TwbRender.MakeCurrent] <Debug: Leave MC 0 0>
[20:06] Waiting for LODGenx64.exe generating object LOD for Tamriel AUT.
[36:54] LODGenx64.exe generated object LOD for Tamriel AUT successfully
[36:54] Waiting for LODGenx64.exe generating object LOD for Tamriel SUM.
[42:49] [WriteSummaries] <Debug: "Deleted Reference;https://dyndolod.info/Messages/Deleted-Reference","File Not Found Meshes;https://dyndolod.info/Messages/File-Not-Found-Meshes","File Not Found Scripts;https://dyndolod.info/Messages/File-Not-Found-Scripts","File Not Found Textures;https://dyndolod.info/Messages/File-Not-Found-Textures","Invalid Script;https://dyndolod.info/Messages/Invalid-Script","Large Reference Bugs;https://dyndolod.info/Messages/Large-Reference-Bugs","Potentially Wild Edit Reference;https://dyndolod.info/Messages/Potentially-Wild-Edit-Reference","Property Not Found In Scripts;https://dyndolod.info/Messages/Property-Not-Found-In-Scripts","Root Block;https://dyndolod.info/Messages/Root-Block","Textures Do Not Match;https://dyndolod.info/Messages/Textures-Do-Not-Match">
[42:49] LODGenx64.exe generated object LOD for Tamriel SUM successfully
[42:49] LODGenx64.exe generated object LOD for Tamriel SPR successfully
[42:49] LODGenx64.exe generated object LOD for Tamriel WIN successfully
[42:49] LODGenx64.exe generated object LOD for Tamriel successfully
[42:49] Created a summary of log messages C:\DynDOLOD\Summary\DynDOLOD_Index.html.
[42:52] 00000000 ???                                           
01004267 DynDOLODx64.exe DynDOLODResourceStrings   909 dynMessageDialog
00ffad6a DynDOLODx64.exe xeMainForm              21309 TLODGenThread.Execute
005dda80 DynDOLODx64.exe System.Classes                ThreadProc
0042a465 DynDOLODx64.exe BrainMM                  2540 BrainMMThreadProxy
0041214a DynDOLODx64.exe System                        ThreadWrapper
00511709 DynDOLODx64.exe madExcept                     ThreadExceptFrame
7fface68 KERNEL32.DLL                                  BaseThreadInitThunk
7ffad03e ntdll.dll                                     RtlUserThreadStart
[42:52] [TMessageDialog.Dialog] <Debug: Creating TTaskDialog>
[42:52] [TMessageDialog.Dialog] <Debug: [TMessageDialog.Dialog] Executing TTaskDialog>
Range check error
Error: Range check error.
[44:10] [TMessageDialog.Dialog] <Debug: Gathering>
User says "Exit DynDOLOD"
Forced

 

[sheson]

11 minutes ago, PurpleYellowRosa said:

The process runs for about 42 minutes, then bugs out after finishing Object LOD for Tamriel (and seasons). It's likely from a mod I installed, since the error happens on multiple DynDOLOD versions, I'm just having trouble identifying exactly which mod. My last successful run was two days ago, so potentially I could binary test it, but I'd prefer to try to document the process and actually "solve" what's causing it.

My debug log is about 840 MB, so I'm attaching the final section in hopes that it can help.

 

Moved to the DynDOLOD 3 Alpha thread.

See the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire log for the session, debug log and bugreport.txt to upload and how to zip and use a file service for large files.

As explained at https://dyndolod.info/Messages/Exceptions#Range-check-error, this is a problem that needs to be fixed in the tools.

[Jadeath]

Same Integer Overflow error unfortunately however I notice I am getting it much sooner now, like 3 minutes in.

https://ufile.io/b3oc1czk

https://ufile.io/h3taxvhn

https://ufile.io/hgsykhxy

[sheson]

3 minutes ago, Jadeath said:

Same Integer Overflow error unfortunately however I notice I am getting it much sooner now, like 3 minutes in.

https://ufile.io/b3oc1czk

https://ufile.io/h3taxvhn

https://ufile.io/hgsykhxy

Thank again!

Try this one https://mega.nz/file/1d5TnAIK#2cDWdSG0hFDYawTXUDaqp3wnB9ezbxIZ3vudTvSCHO0

[Jadeath]

Same result I'm afraid:

https://ufile.io/f3czpl0r

https://ufile.io/6oz9cg5f

https://ufile.io/o2cfk3sv

 

[TheDude]

7 hours ago, sheson said:

Child > Parent
"Low" is the old default that just happened automatically.
"Medium" will take care of trees in cities. Vanilla Riften has some aspens that are then visible, so I'd use that.

Parent > Child
Since it replaces the Whiterun and Solitude Exterior patches from older DynDOLOD Resources, enable that check box if you are interested in proper surroundings and used those patches before. Especially helpful for Whiterun, Riften and Solitude if you use mods like Legacy of the Dragenborn where you can actually see outside. Do not use if performance is more important and then just don't peak outside. If large reference bugs workarounds is used, you can disable large references in child worlds from the SkyUI MCM to regain a bit of performance.

Make sure to read https://dyndolod.info/Help/Child-Parent-Worldspace-Copies if controlling things individually for a specific child world is needed.

Hi Sheson, I just tried the new Alpha 130 with the settings above (since I used the Whiterun and Solitude patches from the older Dyndolod resources) but it seems like the new version is giving me huge performance-issues and FPS-drops in comparison to the older version...? In Whiterun for example (which was running at 60 fps before) I get severe stutters in comparison to the older verson so I will try to regenerate my LOD to see if something is wrong on my end...

Or maybe the new child/parent-settings simply are much more performance demanding than the old ones?

[sheson]

8 minutes ago, Jadeath said:

Same result I'm afraid:

https://ufile.io/f3czpl0r

https://ufile.io/6oz9cg5f

https://ufile.io/o2cfk3sv

It actually progressed to a new range check error.

Try this test version https://mega.nz/file/RIwhmT5R#78qJi2XifQvL4IH59gk9wjelRLJbispws4bQ5ei3Yq4

[sheson]

10 minutes ago, TheDude said:

Hi Sheson, I just tried the new Alpha 130 with the settings above (since I used the Whiterun and Solitude patches from the older Dyndolod resources) but it seems like the new version is giving me huge performance-issues and FPS-drops in comparison to the older version...? In Whiterun for example (which was running at 60 fps before) I get severe stutters in comparison to the older verson so I will try to regenerate my LOD to see if something is wrong on my end...

Or maybe the new child/parent-settings simply are much more performance demanding than the old ones?

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

If you have mods that add several hundreds of new references in and around towns then maybe that is to be expected. I tested vanilla game with Capital Whiterun Expansion which adds lots of new stuff around Whiterun and it was fine.

Generating LOD with the same load order and settings is going to have the same results.

[TheDude]

5 minutes ago, sheson said:

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

If you have mods that add several hundreds of new references in and around towns then maybe that is to be expected. I tested vanilla game with Capital Whiterun Expansion which adds lots of new stuff around Whiterun and it was fine.

Generating LOD with the same load order and settings is going to have the same results.

Understood, Ill get back to you the the proper logfiles after Ive redone the LOD-generation.

I also have a minimum of mods in and around town and since the older version (Alpha 128) worked really well the perfomancedrop with the latest version seems weird... The load order is exactly the same btw.

[Jadeath]

Getting completely new error now so I assume making progress:  Error: Range check error

https://ufile.io/4bn9zjqo

https://ufile.io/o7siwurl

https://ufile.io/souwi8am

 

[PurpleYellowRosa]

8 hours ago, sheson said:

Moved to the DynDOLOD 3 Alpha thread.

See the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire log for the session, debug log and bugreport.txt to upload and how to zip and use a file service for large files.

As explained at https://dyndolod.info/Messages/Exceptions#Range-check-error, this is a problem that needs to be fixed in the tools.

Apologies for late follow up on this. I tested two different things: undeleting references to use the new Dyndolod.dll NG (same error) and doing LOD generation with the same parameters but no seasons (success!). So I assume it has something to do with seasons. I'm attaching all the logs from my latest attempt, including the seasonal LODGen logs, as well as the bug report.

https://ufile.io/rv7j6ekj

Edit: It also didn't work with the alpha-131 exe linked by sheson on this thread.
Edit 2: Downgrading to alpha-128 "fixed" the problem. Will wait for more fixes before updating back to current.

Edited August 7, 2023 by PurpleYellowRosa

[MisterMorden]

Also getting range check error sheson, here are my logs:

bugreport: https://ufile.io/vceu2rdm

dyndolod & texgen SSE logs: https://ufile.io/f/xbxm1

dyndolod & texgen debug_logs: https://ufile.io/f/rapl6

[xcal68]

On 5/15/2022 at 2:33 AM, sheson said:

DynDOLOD and Occlusion plugins are created by copying the winning overwrite from the last plugin before them.

Sorry, I know this is old, but I'm having troubles searching.  Can you confirm it is still supposed to work like this?  I'm using the latest release (130), and the occlusion plugin isn't consistently doing this.  I rebuilt from scratch earlier today.  When I started testing/playing, I noticed a water seam.  Looking in xedit, the occlusion plugin had taken an unexpected xcwt-water record 35 times.  Edit - it looks like the occlusion plugin is taking whatever water record dyndolod.esm has, so maybe it's that which is not gathering the correct 'last' record?  Edit - Looks like a few xlcn-location and some editor id records, as well.

Another edit -

Not sure if these are helpful, but here's the plugin and I think the logs you want:  Click (Just realized the plugin will be pointless unless you have the same load order haha...)

Edited August 7, 2023 by xcal68
Added more info - Added files.

[sheson]

@Jadeath @PurpleYellowRosa @MisterMorden

Check if this test versions runs through https://mega.nz/file/YIpnyJ4I#CiKiAQirG2Ix1UCHnfPjIUbDeS7Lee5aeyKGTkCSK-Q

Test if Alpha-131 fixed the issue.

Upload new logs either way.

[sheson]

12 hours ago, xcal68 said:

Sorry, I know this is old, but I'm having troubles searching.  Can you confirm it is still supposed to work like this?  I'm using the latest release (130), and the occlusion plugin isn't consistently doing this.  I rebuilt from scratch earlier today.  When I started testing/playing, I noticed a water seam.  Looking in xedit, the occlusion plugin had taken an unexpected xcwt-water record 35 times.  Edit - it looks like the occlusion plugin is taking whatever water record dyndolod.esm has, so maybe it's that which is not gathering the correct 'last' record?  Edit - Looks like a few xlcn-location and some editor id records, as well.

Another edit -

Not sure if these are helpful, but here's the plugin and I think the logs you want:  Click (Just realized the plugin will be pointless unless you have the same load order haha...)

Of course it is supposed to copy the winning records.

Unfortunately the debug log in the archive is incomplete. Upload the entire debug log.

Upload DynDOLOD.esm and DynDOLOD.esp when uploading Occlusion.esp. I can check them.

Provide screenshot of a record in xEdit. https://dyndolod.info/Official-DynDOLOD-Support-Forum#xEdit-Screenshots

Edit: I was able to reproduce this. It happens when not using scripted dynamic LOD - which the latest DynDOLOD DLL NG does not use anymore.
Should be fixed in Alpha-131