Jump to content
  • 0

DynDOLOD Fails "Waiting for LODGen64.exe" timeout


Barachiel

Question

So i'm trying to get DynDOLOD to work, and am having an unusual issue.  

 

Basically, it runs for about 30 minutes, and everything's fine. it gets to what looks like the end, and it just starts repeated "Waiting for LODGen64.exe to finish" every 20-ish seconds for 15 minutes, until it gives up, saying its timed out waiting for "LODGen_SSE_Tamriel.log" to release, and then it finishes.  If I tell it to save, then it closes, out but a command prompt window stays open.  I was told to have patience, to let it close on its own, and if i do, it just stays there, never changing.  I let it sit for an additional 45 minutes, and it never closed. If I close the window manually (what I did the last time), it reports errors in static lod objects.  

 

Oh, and i've read the aforementioned log, it doesn't report any kind of error, it just... stops, usually mid-line, about generating an object. 

LODGen_SSE_Tamriel_log.txt

Edited by Barachiel
Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

FAQ: LODGen.exe: Runs a long time / The LOD files generated are several GB in size

 
A: The selected configuration options require a lot of work. Do not manually close LODGen.exe. Wait for all processes to complete before closing DynDOLOD.
 
A: If there are more objects with LOD, it takes longer and creates larger files. If there are more triangles in the models used for LOD, it takes longer and creates larger files. If there are more triangles in the terrain meshes, it takes longer. 
 
A: Do not use the experimental TreeFullFallBack setting without understanding what it does and what it is for. 
 
 

Pay attention to the included manual which says specifically not to generate into mod or game folders. Especially while the mod manager is running...

 

Check if if it still uses CPU or not. Check its memory usage.
Let Windows handle the page file / virtual memory.
Make sure antivir or similar crapware does not block anything.
Do not change the load order in the mod manager while processes are running.
Edited by sheson
Link to comment
Share on other sites

  • 0

My other log file is too big to upload, even zipped.  so here are the last lines. 

 

[00:46:50.502]    Waiting for LODGenx64.exe to finish ...
[00:46:55.552]    Waiting for LODGenx64.exe to finish ...
[00:47:00.606]    Waiting for LODGenx64.exe to finish ...
[00:47:05.657]    Waiting for LODGenx64.exe to finish ...
[00:47:10.705]    Waiting for LODGenx64.exe to finish ...
[00:47:15.764]    Waiting for LODGenx64.exe to finish ...
[00:47:20.847]    Gave up waiting for D:\Mod Tools\DynDOLOD\Logs\LODGen_SSE_Tamriel_log.txt to become available.
[00:47:20.910]        Wait for LODGenx64.exe to finish by itself before closing DynDOLOD.exe
[00:47:21.019]    LODGenx64.exe for DLC2SolstheimWorld completed successfully
[00:47:21.085]    LODGenx64.exe for MarkarthWorld completed successfully
[00:47:21.139]    LODGenx64.exe for DLC01SoulCairn completed successfully
[00:47:21.176]    LODGenx64.exe for DLC2ApocryphaWorld completed successfully
[00:47:21.212]    LODGenx64.exe for SkuldafnWorld completed successfully
[00:47:21.246]    LODGenx64.exe for Dimfrost completed successfully
[00:47:21.275]    LODGenx64.exe for Sovngarde completed successfully
[00:47:21.291]    LODGenx64.exe for WyrmstoothWorld completed successfully
[00:47:21.321]    LODGenx64.exe for DeepwoodRedoubtWorld completed successfully
[00:47:21.337]    LODGenx64.exe for mannyGFO completed successfully
[00:47:21.360]    LODGenx64.exe for aaaWereBalokDungeonWorld completed successfully
[00:47:21.377]    LODGenx64.exe for DLC1HunterHQWorld completed successfully
[00:47:21.396]    LODGenx64.exe for Blackreach completed successfully
[00:47:21.409]    LODGenx64.exe for DLC01FalmerValley completed successfully
[00:47:21.425]    LODGenx64.exe for Falskaar completed successfully
[00:47:21.444]    LODGenx64.exe for JaphetsFollyWorld completed successfully
[00:47:21.459]    LODGenx64.exe for PalePass completed successfully
[00:47:21.471]    LODGenx64.exe for TOKMountainPassWorld completed successfully
[00:47:21.488]    LODGenx64.exe for mannyGFL completed successfully
[00:47:21.507]    LODGenx64.exe for mannyGFDesert completed successfully
[00:47:21.520]    
[00:47:21.535]    
[00:47:21.550]    DynDOLOD Worlds completed successfully.
[03:44:22.814]    [45:05] Saving: DynDOLOD.esm
[03:44:27.001]    [45:09] Saving: DynDOLOD.esp
[03:44:32.624]    [45:15] Done saving.

 

Link to comment
Share on other sites

  • 0

I regenerated DynDOLOD with files outside the MO2 file structure.  Reinstalled C++, confirmed windows handles memory page file already, AV disabled. 

 

Problem persists. 

 

EDIT:  It uses about 80% of my memory, at least when its at the "waiting" stage.

The second LODGen_SSE_Tamriel_log.txt shows that object LOD generation completed correctly. The last two lines show

 

Log ended at 2:53:44 PM (8:28)

Code: 0

 

It is normal for DynDOLOD to give up if LODGen takes that long. The FAQ applies. Just wait. You probably have high resolution terrain LOD and full model 3D tree LODs or other full models for LOD that mean a lot of work.

Edited by sheson
  • +1 1
Link to comment
Share on other sites

  • 0

That's the first time that log has ended with that (during this incident), I was hoping it was a good sign.

 

Okay, so there isn't a problem anymore.  Wonderful!  I'd be a teensy bit happier if I knew what fixed it exactly, for the future, but I'll take the win.

 

Thank you for your time.  DynDOLOD is an amazing program.  

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.