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]

11 minutes ago, m1sf1t711 said:

Hi 

I'm not sure that my PC is the problem as I am not getting any crashes just a failure to generate some of the lod, usually Tamriel Aut and Tamriel Sum but sometimes the other seasons when trying the test versions you've shared.  I also haven't changed anything with my hardware since I was able to successfully run DynDOLOD Alpha 182 when it was first publised. However I will still try to look into this as I appreciate something might have been changed by something in the background that I'm unaware of, thank you.

There might be changes to the load order that increased CPU, memory demand to higher levels than before and you were just lucky so far.

Other reasons might be OS update, drivers, loose cables, BIOS settings resetting to default, hardware going bad, cooling being affected because of dust (dead mouse not unheard of) etc. It is possible the issue is storage/disk related.

[m1sf1t711]

Just now, sheson said:

There might be changes to the load order that increased CPU, memory demand to higher levels than before and were just lucky.

Other reasons might be OS update, drivers, loose cables, BIOS settings resetting to default, hardware going bad etc. It is possible the issue is storage/disk related.

I understand thank you

I'll try to find out what I can.

[m1sf1t711]

3 hours ago, sheson said:

There might be changes to the load order that increased CPU, memory demand to higher levels than before and you were just lucky so far.

Other reasons might be OS update, drivers, loose cables, BIOS settings resetting to default, hardware going bad, cooling being affected because of dust (dead mouse not unheard of) etc. It is possible the issue is storage/disk related.

Hi

Just in case this is of any value to know, I have just tried running the original Alpha 182 again having tried reducing my mod list a little incase it made any difference (I will be looking at the CPU testing tomorrow when I am less tired and can apply a fresher brain). I opened up task manager while it was running and at no point did CPU use go above 59% or memory above 66%. I was also checking to see if I had anything else running in the background at the same time which might have been interfering but there was nothing making active use of the CPU or Memory.

 

If I get any progress out of checking all the possible reasons on your list tomorrow I'll provide an update, just in case anything I find out proves helpful in any way.

 

Thanks again

[m1sf1t711]

20 hours ago, sheson said:

There might be changes to the load order that increased CPU, memory demand to higher levels than before and you were just lucky so far.

Other reasons might be OS update, drivers, loose cables, BIOS settings resetting to default, hardware going bad, cooling being affected because of dust (dead mouse not unheard of) etc. It is possible the issue is storage/disk related.

Just a quick update whilst I'm still investigating things.

Stress testing CPU+RAM using OCCT Personal gives thousands of errors but testing just CPU gives none and testing just memory gives none. So now I'm trying to find out what to look at to understand these errors and solve any problems.

 

In the meantime could you clarify something for me? If I only have  "failed to generate object LOD for Tamriel SPR", so I use the Execute LODGen button on just the Tamriel (Seasons) worldspace, and it then manages to generate Tamriel SPR but fails on, say, Tamriel AUT, would the end result be that I had now got an Output folder with all the necessary object lod included or would the Execute LODGen process have undone any of the object lod generated in the original process? I guess I mean, does Execute LODGen just fill in the missing object lod so that if over several attempts I get a successful generation for each season I'd end up with everything I need?

Edited October 27, 2024 by m1sf1t711

[sheson]

2 hours ago, m1sf1t711 said:

Just a quick update whilst I'm still investigating things.

Stress testing CPU+RAM using OCCT Personal gives thousands of errors but testing just CPU gives none and testing just memory gives none. So now I'm trying to find out what to look at to understand these errors and solve any problems.

 

In the meantime could you clarify something for me? If I only have  "failed to generate object LOD for Tamriel SPR", so I use the Execute LODGen button on just the Tamriel (Seasons) worldspace, and it then manages to generate Tamriel SPR but fails on, say, Tamriel AUT, would the end result be that I had now got an Output folder with all the necessary object lod included or would the Execute LODGen process have undone any of the object lod generated in the original process? I guess I mean, does Execute LODGen just fill in the missing object lod so that if over several attempts I get a successful generation for each season I'd end up with everything I need?

Only select the worldspaces and seasons that failed before clicking Execute LODGen. You can repeat that as often as needed with different selections until it completed all world spaces successfully.
Do not Execute LODGen again for worldspaces and seasons that already completed successfully.

You can also copy/move already completed worldspaces and seasons *.BTO to whereever to make sure they are not accidently overwritten with incomplete generations that get interrupted.

IN the end you can merge all the *.BTOs that generated successfully into one complete output.

[m1sf1t711]

13 minutes ago, sheson said:

Only select the worldspaces and seasons that failed before clicking Execute LODGen. You can repeat that as often as needed with different selections until it completed all world spaces successfully.
Do not Execute LODGen again for worldspaces and seasons that already completed successfully.

You can also copy/move already completed worldspaces and seasons *.BTO to whereever to make sure they are not accidently overwritten with incomplete generations that get interrupted.

IN the end you can merge all the *.BTOs that generated successfully into one complete output.

Ah thank you!  I'm not sure how I can seperate out the individual seasons for the Tamriel worldspace when Execute LODGen is used. The list of worldspaces just has one option for Tamriel (Seasons) so do I uncheck the seasons in the Seasons checklist that I don't want to repeat?

(Sorry if I'm asking ignorant questions :-/ )

[sheson]

3 hours ago, m1sf1t711 said:

Ah thank you!  I'm not sure how I can seperate out the individual seasons for the Tamriel worldspace when Execute LODGen is used. The list of worldspaces just has one option for Tamriel (Seasons) so do I uncheck the seasons in the Seasons checklist that I don't want to repeat?

(Sorry if I'm asking ignorant questions :-/ )

You can select a single worldspace and select a single or more seasons and then Execute LODGen and wait for it to complete. Then select another worldspace and check different seasons and click Execute LODGen again.

[HadToMakeAnAccount]

Reposting to a different part of the forum, as suggested.

LODGen produced 160 logs and I read through them, but this is all the info I have:

LODGen_SSE_SkuldafnWorld_log.txt (Skyrim.esm) says
"Error accessing D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\Meshes\Terrain\SkuldafnWorld\SkuldafnWorld.4.48.-5.btr Unable to read beyond the end of the stream."

and LODGen_SSE_DLC2SolstheimWorld_log.txt  (Dragonborn.esm) says
"Error accessing D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\Meshes\Terrain\DLC2SolstheimWorld\DLC2SolstheimWorld.4.-96.-8.btr Unable to read beyond the end of the stream."

In the meantime, I'm going to disable them in DynDOLOD and continue on.

[sheson]

32 minutes ago, HadToMakeAnAccount said:

Reposting to a different part of the forum, as suggested.

LODGen produced 160 logs and I read through them, but this is all the info I have:

LODGen_SSE_SkuldafnWorld_log.txt (Skyrim.esm) says
"Error accessing D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\Meshes\Terrain\SkuldafnWorld\SkuldafnWorld.4.48.-5.btr Unable to read beyond the end of the stream."

and LODGen_SSE_DLC2SolstheimWorld_log.txt  (Dragonborn.esm) says
"Error accessing D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\Meshes\Terrain\DLC2SolstheimWorld\DLC2SolstheimWorld.4.-96.-8.btr Unable to read beyond the end of the stream."

In the meantime, I'm going to disable them in DynDOLOD and continue on.

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

 

Wasn't the original error and DynDOLOD log message like this:
https://stepmodifications.org/forum/topic/19089-lodgenx64exe-failed-to-generate-object-lod-for-tamriel-lodgenx64exe-returned-25b

https://dyndolod.info/Help/LODGen
25B -  Error accessing
There is a problem reading the mentioned *.NIF. ... If the mentioned file is a *.BTR terrain LOD mesh, generate a valid one with xLODGen and follow its instructions to always set a dedicated output folder outside of any game and mod manager folders.

If you followed the instructions of xLODGen to generate the files, it is possible something happened to them or something us interfering with reading them.

[T9A10]

 

Hello, My Dyndolod crashed without any pop-up alerts. When Dyndolod crashed, Lodgen was still running, and the generated logs were not being monitored in real time. I am unable to determine the specific error in the process on my own
This is the latest log of Dyndolod and Lodgen

Dyndolod https://www.mediafire.com/file/rsyi7u52adgr7bd/DynDOLOD_SSE_log.txt/file

Lodgen https://www.mediafire.com/file/86xyy6qqie67i7s/LODGen_SSE_Tamriel_log.txt/file

[sheson]

1 hour ago, T9A10 said:

 

Hello, My Dyndolod crashed without any pop-up alerts. When Dyndolod crashed, Lodgen was still running, and the generated logs were not being monitored in real time. I am unable to determine the specific error in the process on my own
This is the latest log of Dyndolod and Lodgen

Dyndolod https://www.mediafire.com/file/rsyi7u52adgr7bd/DynDOLOD_SSE_log.txt/file

Lodgen https://www.mediafire.com/file/86xyy6qqie67i7s/LODGen_SSE_Tamriel_log.txt/file

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD debug log and bugreport.txt if (it exists) to also upload when making posts.

Moved to an appropriate thread for this error message:
<Error: LODGenx64.exe failed to generate object LOD for Tamriel. LODGenx64.exe returned C0000005. Check E:\iniRePather-Skyrim\DynDOLOD\Logs\LODGen_SSE_Tamriel_log.txt>
Error: LODGenx64.exe failed to generate object LOD for one or more worlds. Check for error messages in the listed LODGen log(s)

See https://dyndolod.info/Help/LODGen:
C0000005 - If happening randomly can be a sign of hardware issues like CPU or memory being unstable.
Reduce memory requirements. See Out of Memory below. See FAQ High Memory Usage / Out of Memory.

Also see https://dyndolod.info/Messages/Exceptions#Access-violation

[T9A10]

Thanks,after adjusting the INI file and restarting Texgen, the issue has been resolved.

However, a new situation has arisen now.

After LODGen_SSE_Tamriel has been outputting for a period of time, LODGen_SSE_DLC2SolstheimWorld is also initiated and starts outputting. However, it seems that LODGen_SSE_DLC2SolstheimWorld did not continue processing files halfway through. It remained in this state for a long period of time, and the help page of lodgen does not mention this scenario. Is this a normal situation? If not, how can we solve this issue and proceed with subsequent output?

photo

https://www.mediafire.com/view/hzcv1b50cbxnsa4/__%7ERSI%29M14YL5%240QXPH7551.png/file

logs

LODGen_SSE_Tamriel https://www.mediafire.com/file/9fsosk80nrr9639/LODGen_SSE_Tamriel_log.txt/file

LODGen_SSE_DLC2SolstheimWorld https://www.mediafire.com/file/vevs2915zgs8k0u/LODGen_SSE_DLC2SolstheimWorld_log.txt/file

The log for dyndolod has not been updated.

[sheson]

3 hours ago, T9A10 said:

Thanks,after adjusting the INI file and restarting Texgen, the issue has been resolved.

However, a new situation has arisen now.

After LODGen_SSE_Tamriel has been outputting for a period of time, LODGen_SSE_DLC2SolstheimWorld is also initiated and starts outputting. However, it seems that LODGen_SSE_DLC2SolstheimWorld did not continue processing files halfway through. It remained in this state for a long period of time, and the help page of lodgen does not mention this scenario. Is this a normal situation? If not, how can we solve this issue and proceed with subsequent output?

photo

https://www.mediafire.com/view/hzcv1b50cbxnsa4/__%7ERSI%29M14YL5%240QXPH7551.png/file

logs

LODGen_SSE_Tamriel https://www.mediafire.com/file/9fsosk80nrr9639/LODGen_SSE_Tamriel_log.txt/file

LODGen_SSE_DLC2SolstheimWorld https://www.mediafire.com/file/vevs2915zgs8k0u/LODGen_SSE_DLC2SolstheimWorld_log.txt/file

The log for dyndolod has not been updated.

Requested debug log and bugreport.txt were not provided.

It is unclear what the relevance of TexGen and its INI is supposed to have when reporting a problem with LODGen/DynDOLOD.

As explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs, the DynDOLOD log and debug log are saved when DynDOLOD is closed. The page also explains how to enable the realtime log for DynDOLOD in case it is prematurely terminated.

See https://dyndolod.info/Messages/Exceptions#Access-violation.

The issue LODGen has is secondary or maybe a result of the former issue. Keep an eye on memory usage.
See answers for LODGen and DynDOLOD for https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory
See https://dyndolod.info/Help/LODGen#Out-of-Memory

Verify with prime95 and OCCT that the system is stable.

[T9A10]

20小时前，谢森说：

请求的调试日志和bugreport.txt未被提供。

目前尚不清楚TexGen及其INI在报告LODGen/DynDOLOD问题时的相关性。

正如 https:// dyndolod.info/Official-DynDOLOD-Support-Forum #Post-Logs 中所述，DynDOLOD 的日志和调试日志在 DynDOLOD 关闭时会被保存。页面还解释了如何在DynDOLOD提前终止时启用实时日志。

参见 https:// dyndolod.info/Messages/Exceptions#Access-violation。

LODGen的问题是次要的，或者可能是前者问题的结果。注意内存使用情况。
请参见 https:// dyndolod.info/FAQ#高内存使用率-内存不足
参见 https:// dyndolod.info/Help/LODGen#内存不足

用prime95和OCCT验证系统是否稳定。

These are the debug log and bugreport generated after I ran dyndolod for the last time tonight and it failed.
I noticed that it seems to be related to memory, but I cannot determine the specific point at which the error occurred.
I will try to find another time to test the stability of the system later.
Another issue is how to correctly apply the output content to subsequent output stages and plugin generation after I regenerate the object using function A.

bugreport https://www.mediafire.com/file/mfo6zgglg1hln62/bugreport.txt/file

dyndolod debug log https://www.mediafire.com/file/5ridxmy7m1uru0j/DynDOLOD_SSE_Debug_log.txt/file
I noticed that it seems to be related to memory, but I cannot determine the specific point at which the error occurred.
I will try to find another time to test the stability of the system later.
Another issue is how to correctly apply the output content to subsequent output stages and plugin generation after I regenerate the object using execute LODGen again.

Edited February 1 by T9A10
not the word...

[sheson]

11 minutes ago, T9A10 said:

These are the debug log and bugreport generated after I ran dyndolod for the last time tonight and it failed.
I noticed that it seems to be related to memory, but I cannot determine the specific point at which the error occurred.
I will try to find another time to test the stability of the system later.
Another issue is how to correctly apply the output content to subsequent output stages and plugin generation after I regenerate the object using function A.

bugreport https://www.mediafire.com/file/mfo6zgglg1hln62/bugreport.txt/file

dyndolod debug log https://www.mediafire.com/file/5ridxmy7m1uru0j/DynDOLOD_SSE_Debug_log.txt/file
I noticed that it seems to be related to memory, but I cannot determine the specific point at which the error occurred.
I will try to find another time to test the stability of the system later.
Another issue is how to correctly apply the output content to subsequent output stages and plugin generation after I regenerate the object using execute LODGen again.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs whicjh normal DynDOLOD log also upload when making posts.

Check the mentioned cell record 31B539F4 from Olenveld.esp with xEdit. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#xEdit-Screenshots

https://dyndolod.info/Help/LODGen#Out-of-Memory
If a LODGen process uses a lot of memory, set LODGenThreadSplit in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI to a higher number. Set to the number of virtual cores for lowest possible memory usage.
Test if setting LODGenThreadSplit=16 or even 32 helps with the C0000005 in LODGen.

The log reports unresolved from IDs and deleted references. These should be fixed regardless.
https://dyndolod.info/Generation-Instructions#Prerequisites
Clean and error check the load order with xEdit.
Also see https://dyndolod.info/Messages/Unresolved-Form-ID and https://dyndolod.info/Messages/Deleted-Reference
I suggest to learn rudimentary modding practice how to build a properly working load order by following a modding guide.