LODGenx64.exe failed to generate object LOD for one or more worlds

[nolbear]

Hello again, I'm trying to use DynDOLOD 3.00 (Alpha 14) to generate LOD for my game and I keep running into this error: "LODGenx64.exe failed to generate object LOD for one or more worlds." It seems to run into the error when trying to generate object LOD for the Tamriel worldspace. I've searched all over but can't find anyone else who has encountered this error. Any ideas what might be causing the problem? Here's a picture of the error message. Please let me know if you have any ideas. Thanks!

[sheson]

2 hours ago, DarthVitrial said:

We got an actual log this time!

The only mod I have modifying those trees is Seasonal Aspen Trees (w/ patches for shrubs of snow and turn of the seasons): https://www.nexusmods.com/skyrimspecialedition/mods/63641?tab=files

 

full logs: https://mega.nz/file/xk1D1ARZ#6sd9jJJ1EXHTild6gCoO5_oCYKN1AchBZfSpk1amQlM

LODGen_SSE_Tamriel_SPR_log.txt 336 kB · 3 downloads

I keep testing with that mod and 3D models without problem. Can you start DynDOLOD in expert mode and just execute LODGen for that season again to see if the same error happens with the same NIF consistently?

With the trace I can start looking into the 3rd party code that optimizes triangles/vertices order to see whats up tomorrow.

[DarthVitrial]

52 minutes ago, sheson said:

I keep testing with that mod and 3D models without problem. Can you start DynDOLOD in expert mode and just execute LODGen for that season again to see if the same error happens with the same NIF consistently?

With the trace I can start looking into the 3rd party code that optimizes triangles/vertices order to see whats up tomorrow.

here you go https://mega.nz/file/A58n0BDb#RS4-dc8d8LgS_gvdWJxj83-fp7q694wTdbaxN5NH7Do

[sheson]

14 hours ago, DarthVitrial said:

here you go https://mega.nz/file/A58n0BDb#RS4-dc8d8LgS_gvdWJxj83-fp7q694wTdbaxN5NH7Do

Have you ever tested  the hardware with something like prime95 blend test? Just wondering.

Run with this version of LODGen https://mega.nz/file/AVQHETyI#uc3iBydpHCx0rWp2sX2tvHaW3ZHFC7Sbq1FHqbIhA4A and upload the logs for whichever worldspace/season failed.

[DarthVitrial]

11 hours ago, sheson said:

Have you ever tested  the hardware with something like prime95 blend test? Just wondering.

Run with this version of LODGen https://mega.nz/file/AVQHETyI#uc3iBydpHCx0rWp2sX2tvHaW3ZHFC7Sbq1FHqbIhA4A and upload the logs for whichever worldspace/season failed.

I have, but not recently. Logs attached.

LODGen_SSE_Tamriel_WIN_log.txt LODGen_SSE_Tamriel_log.txt DynDOLOD_SSE_log.txt

[sheson]

13 hours ago, DarthVitrial said:

I have, but not recently. Logs attached.

LODGen_SSE_Tamriel_WIN_log.txt 796 kB · 3 downloads LODGen_SSE_Tamriel_log.txt 151.01 kB · 2 downloads DynDOLOD_SSE_log.txt 817.73 kB · 2 downloads

You have the .Net event log for that with the trace?

Can you generate without Season Aspen Trees to rule out that there is a problem with the assets? I am pretty sure they are not the problem since I have no issues despite the 3D tree LOD models containing orphaned blocks and left over collision. That's all ignored anyways.

[DarthVitrial]

11 hours ago, sheson said:

You have the .Net event log for that with the trace?

Can you generate without Season Aspen Trees to rule out that there is a problem with the assets? I am pretty sure they are not the problem since I have no issues despite the 3D tree LOD models containing orphaned blocks and left over collision. That's all ignored anyways.

Application: LODGenx64.exe

Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at LODGenerator.Geometry.RemoveDuplicate(Boolean)
   at LODGenerator.LODApp.RemoveUnseenFaces(LODGenerator.QuadDesc, LODGenerator.ShapeDesc)
   at LODGenerator.LODApp.TransformShape(LODGenerator.QuadDesc, LODGenerator.StaticDesc, LODGenerator.NiFile, LODGenerator.NifMain.NiTriBasedGeom, LODGenerator.Common.Matrix44, Single, Int32)
   at LODGenerator.LODApp.IterateNodes(LODGenerator.QuadDesc, LODGenerator.StaticDesc, Int32, LODGenerator.NiFile, LODGenerator.NifMain.NiNode, LODGenerator.Common.Matrix44, Single, Int32 ByRef)
   at LODGenerator.LODApp.ParseNif(LODGenerator.QuadDesc, LODGenerator.StaticDesc, Int32)
   at LODGenerator.LODApp+<>c__DisplayClass84_0.<DoLOD>b__0(Int32)
   at System.Threading.Tasks.Parallel+<>c__DisplayClass17_0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(System.Threading.Tasks.Task)
   at System.Threading.Tasks.Task+<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
   at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
   at System.Threading.Tasks.ThreadPoolTaskScheduler.TryExecuteTaskInline(System.Threading.Tasks.Task, Boolean)
   at System.Threading.Tasks.TaskScheduler.TryRunInline(System.Threading.Tasks.Task, Boolean)
   at System.Threading.Tasks.Task.InternalRunSynchronously(System.Threading.Tasks.TaskScheduler, Boolean)
   at System.Threading.Tasks.Parallel.ForWorker[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Int32, Int32, System.Threading.Tasks.ParallelOptions, System.Action`1<Int32>, System.Action`2<Int32,System.Threading.Tasks.ParallelLoopState>, System.Func`4<Int32,System.Threading.Tasks.ParallelLoopState,System.__Canon,System.__Canon>, System.Func`1<System.__Canon>, System.Action`1<System.__Canon>)
   at System.Threading.Tasks.Parallel.For(Int32, Int32, System.Threading.Tasks.ParallelOptions, System.Action`1<Int32>)
   at LODGenerator.LODApp.DoLOD(LODGenerator.QuadDesc, Boolean)
   at LODGenerator.LODApp.<GenerateLOD>b__85_0(LODGenerator.QuadDesc)
   at System.Threading.Tasks.Parallel+<>c__DisplayClass31_0`2[[LODGenerator.QuadDesc, LODGenx64, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForEachWorker>b__0(Int32)
   at System.Threading.Tasks.Parallel+<>c__DisplayClass17_0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].<ForWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(System.Threading.Tasks.Task)
   at System.Threading.Tasks.Task+<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(System.Object)
   at System.Threading.Tasks.Task.Execute()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
   at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

I'll try it without when I get some time

[DarthVitrial]

On 4/21/2022 at 1:48 AM, sheson said:

You have the .Net event log for that with the trace?

Can you generate without Season Aspen Trees to rule out that there is a problem with the assets? I am pretty sure they are not the problem since I have no issues despite the 3D tree LOD models containing orphaned blocks and left over collision. That's all ignored anyways.

I disabled seasonal aspen trees and it worked perfectly. Do you want the logs?

[sheson]

On 4/23/2022 at 11:45 PM, DarthVitrial said:

I disabled seasonal aspen trees and it worked perfectly. Do you want the logs?

Can you zip the files of the mod as you have it installed right now and upload them for me to test with?

[DarthVitrial]

11 hours ago, sheson said:

 

Can you zip the files of the mod as you have it installed right now and upload them for me to test with?

 

Here:https://mega.nz/file/d8EWgRjK#1A-uihbvU_S99sjHooxkxhQx9Y0SFB4qP_aGCVHJ8Ok

I also have the patches for Shrubs of Snow and Turn of the Seasons installed.

[Zahkrii]

Hi its my first time writing on here but I've been using DynDOLOD for a while now for and it has become an essential thing to setup for any of my modlists for SSE. But, I'm definitely still learning how to use it optimally. Whenever I had problems with the generation I'd find a way to fix it by looking at previous posts, troubleshooting guides or tutorials.

But now it seems I've run into a wall that I can't quite figure out how to fix on my own. I apologize if it was a lack of more effort in my part.

Basically the problem lies at the DynDOLODx64 generation. At the end of the generation, it would show "Error: LODGenx64.exe failed to generate object LOD for one or more worlds.". The problem is I can't really pinpoint what is at fault from the logs provided as it seems to cut-off while generating without showing me what happened. Sometimes nothing would be in the logs at all. The object LODs worldspaces that fail to generate almost always includes Tamriel with a random 3-4 worlds. I say random because everytime I try to run it again, it wouldn't be the same set of 3-4 worldspaces that failed to generate. For example, I tried to exclude the worldspaces that previously caused problems but it just found another 4 mods to report the failed generation. Even if I exclude all modded worldspaces, it will fail to generate, say Soul Cairn.

This also causes the program to not create occlusion.esp. "<Error: Occlusion generation aborted due to LODGen error>"

Additionally, I tried to start DynDOLOD with only Tamriel checked. It worked with and even created the occlusion esp. But once I start to add other worldspaces, it repeats the problem above.

Attached are the logs for worldspaces that failed to generate. They either have incomplete or empty text. Any help would be appreciated.

DynDOLOD_SSE_log.txt LODGen_SSE_Tamriel_log.txt LODGen_SSE_XJKislandWorld2_log.txt LODGen_SSE_zGHDunmerCampWorld_log.txt LODGen_SSE_mannyGFO_log.txt

[sheson]

3 hours ago, Zahkrii said:

Hi its my first time writing on here but I've been using DynDOLOD for a while now for and it has become an essential thing to setup for any of my modlists for SSE. But, I'm definitely still learning how to use it optimally. Whenever I had problems with the generation I'd find a way to fix it by looking at previous posts, troubleshooting guides or tutorials.

But now it seems I've run into a wall that I can't quite figure out how to fix on my own. I apologize if it was a lack of more effort in my part.

Basically the problem lies at the DynDOLODx64 generation. At the end of the generation, it would show "Error: LODGenx64.exe failed to generate object LOD for one or more worlds.". The problem is I can't really pinpoint what is at fault from the logs provided as it seems to cut-off while generating without showing me what happened. Sometimes nothing would be in the logs at all. The object LODs worldspaces that fail to generate almost always includes Tamriel with a random 3-4 worlds. I say random because everytime I try to run it again, it wouldn't be the same set of 3-4 worldspaces that failed to generate. For example, I tried to exclude the worldspaces that previously caused problems but it just found another 4 mods to report the failed generation. Even if I exclude all modded worldspaces, it will fail to generate, say Soul Cairn.

This also causes the program to not create occlusion.esp. "<Error: Occlusion generation aborted due to LODGen error>"

Additionally, I tried to start DynDOLOD with only Tamriel checked. It worked with and even created the occlusion esp. But once I start to add other worldspaces, it repeats the problem above.

Attached are the logs for worldspaces that failed to generate. They either have incomplete or empty text. Any help would be appreciated.

DynDOLOD_SSE_log.txt 372.65 kB · 5 downloads LODGen_SSE_Tamriel_log.txt 4 kB · 2 downloads LODGen_SSE_XJKislandWorld2_log.txt 0 B · 2 downloads LODGen_SSE_zGHDunmerCampWorld_log.txt 0 B · 1 download LODGen_SSE_mannyGFO_log.txt 1.84 kB · 1 download

Start DynDOLOD in expert mode, select one of the worldspaces that failed and then click the Execute LODGen button. If that worked, next time you run DynDOLOD for everything, set MaxLODGen=1 in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini to see if it helps. You can merge the successfully generated object LOD meshes with the existing output you already have.

If there is still an error, overwrite the LODGenx64 files from https://mega.nz/file/AVQHETyI#uc3iBydpHCx0rWp2sX2tvHaW3ZHFC7Sbq1FHqbIhA4A into the Edit Scripts folder. See if it prints more information to the log. Also check the Windows Event log for messages.

[sheson]

18 hours ago, DarthVitrial said:

Here:https://mega.nz/file/d8EWgRjK#1A-uihbvU_S99sjHooxkxhQx9Y0SFB4qP_aGCVHJ8Ok

I also have the patches for Shrubs of Snow and Turn of the Seasons installed.

I ran LODGen for Tamriel and all seasons a couple dozen times with those installed and nothing ever happened. Really mysterious.

Activate the mod again and then test with setting LODGenThreadSplit=24 in ..\DynDOLOD3\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and then generate LOD. If you just want to use Execute LODGen in expert mode, edit the line ThreadSplit=0 in all the export files like LODGen_SSE_Export_Tamriel_WIN.txt etc.

If error still happen set MaxLODGen=1 in DynDOLOD_SSE.ini to if running only one at a time makes a difference.

[Zahkrii]

5 hours ago, sheson said:

Start DynDOLOD in expert mode, select one of the worldspaces that failed and then click the Execute LODGen button. If that worked, next time you run DynDOLOD for everything, set MaxLODGen=1 in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini to see if it helps. You can merge the successfully generated object LOD meshes with the existing output you already have.

If there is still an error, overwrite the LODGenx64 files from https://mega.nz/file/AVQHETyI#uc3iBydpHCx0rWp2sX2tvHaW3ZHFC7Sbq1FHqbIhA4A into the Edit Scripts folder. See if it prints more information to the log. Also check the Windows Event log for messages.

Hi, thanks for replying. I think I might have found the issue.

So I replaced LODGenx64, launched DynDOLOD in expert mode and clicked execute LODGen for one of the failed worldspaces as you suggested. It failed to generate the object LODs in the same manner, unfortunately. But I tried it again for the 2nd time and it worked! I thought that something in my system must have been the culprit since the results for DynDOLOD alone were inconsistent.

I also changed the setting for MaxLODGen to 1 and tried generating for everything. With this method, I found that there were more errors. DynDOLOD_SSE_log.txt

I did the LODGen for one of the worlds that had errors to merge it. Before the CMD closed while generating object LODs, I took a screenshot of the error.

See attached "LODGenx64 - Object LOD XJKislandWorld - screenshot.png". 

I have a vague idea about what it means but that seems to be causing the CMD to close rapidly and create empty logs. I tried turning off windows defender's anti-virus features for the time being to test if that was causing the issue but it was still failing to generate, so I don't think that is a factor. Thank you for helping me with this.

[sheson]

48 minutes ago, Zahkrii said:

Hi, thanks for replying. I think I might have found the issue.

So I replaced LODGenx64, launched DynDOLOD in expert mode and clicked execute LODGen for one of the failed worldspaces as you suggested. It failed to generate the object LODs in the same manner, unfortunately. But I tried it again for the 2nd time and it worked! I thought that something in my system must have been the culprit since the results for DynDOLOD alone were inconsistent.

I also changed the setting for MaxLODGen to 1 and tried generating for everything. With this method, I found that there were more errors. DynDOLOD_SSE_log.txt

I did the LODGen for one of the worlds that had errors to merge it. Before the CMD closed while generating object LODs, I took a screenshot of the error.

See attached "LODGenx64 - Object LOD XJKislandWorld - screenshot.png". 

I have a vague idea about what it means but that seems to be causing the CMD to close rapidly and create empty logs. I tried turning off windows defender's anti-virus features for the time being to test if that was causing the issue but it was still failing to generate, so I don't think that is a factor. Thank you for helping me with this.

Great. See if there is anything different when using this version https://mega.nz/file/gNBDhbgY#lxoZCLypS2ISXl45-MfyEPdMkjWkL82BkCtSfFKvPh4
Also check the Windows Event Log for entries. Check c:\Users\[username]\AppData\Local\CrashDumps\LODGen.exe.*.dmp upload them if there are any using this new version.

Test what happens if you set LODGenThreadSplit=same number as cores of the CPU  in ..\DynDOLOD3\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and then generate LOD.
If you just want to use Execute LODGen in expert mode, edit the line ThreadSplit= in all the export files for the worldspaces like..\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Export_Tamriel.txt

If you could do a quick memory test and/or prime95 blend test verify system stability that would be great.

[DarthVitrial]

7 hours ago, sheson said:

I ran LODGen for Tamriel and all seasons a couple dozen times with those installed and nothing ever happened. Really mysterious.

Activate the mod again and then test with setting LODGenThreadSplit=24 in ..\DynDOLOD3\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and then generate LOD. If you just want to use Execute LODGen in expert mode, edit the line ThreadSplit=0 in all the export files like LODGen_SSE_Export_Tamriel_WIN.txt etc.

If error still happen set MaxLODGen=1 in DynDOLOD_SSE.ini to if running only one at a time makes a difference.

Tried both, still getting out of range errors during winter season even with both LODGenThreadSplit=24 and MaxLODGen=1

LODGen_SSE_Tamriel_WIN_log.txt