DynDOLOD is being terminated prematurely, suddenly closes

[VulKun]

I can use 2.98 but i cant use 3 alphax. Still doesnt work for me. Just closing itself and there is no bugreport or something. I tried everything but nothing change 

[sheson]

50 minutes ago, VulKun said:

I'll check but you know me..I can use 2.98 but i cant use 3 alphax. Still doesnt work for me. Just closing itself and there is no bugreport or something. I tried everything but nothing change 

The xEdit/xLODGen/DynDOLOD message window is a text window in which text can be marked with the mouse and copied with the usual key command CTRL+C.

If xEdit/xLODGen/DynDOLOD closes, it writes its message log to the log file.

If the OS terminates the program prematurely it can not do that. In that case check the Windows message log for hints.

[VulKun]

12 minutes ago, sheson said:

The xEdit/xLODGen/DynDOLOD message window is a text window in which text can be marked with the mouse and copied with the usual key command CTRL+C.

If xEdit/xLODGen/DynDOLOD closes, it writes its message log to the log file.

If the OS terminates the program prematurely it can not do that. In that case check the Windows message log for hints.

I checked windows message log and there error
 D:\DynDOLOD 3.0\Edit Scripts\Texconvx64.exe
D:\mod organizer 2\usvfs_x64.dll

[sheson]

On 2/10/2022 at 1:53 PM, VulKun said:

I checked windows message log and there error
 D:\DynDOLOD 3.0\Edit Scripts\Texconvx64.exe
D:\mod organizer 2\usvfs_x64.dll

If that is all the information you are willing to surrender, I suggest you start investigating what is interfering with MO2 virtual file system or TexConv reading/writing.

Update MO2 to the latest version. Another cause could be because LOD is being generated into MO2 folders or game folders. Another cause would be the usual UAC, antivir problems.

[MaarMalur]

Hello, I have some trouble with Dyndolod since I bought my new computer, with almost the exact same mod list (pretty close to vanilla), Dyndolod close during generating lod without any message or any logs. I used many times without trouble Dyndolod in the past, first time I have this issue.

Hope this is the right place to ask help.

 

Thanks !

[sheson]

1 hour ago, MaarMalur said:

Hello, I have some trouble with Dyndolod since I bought my new computer, with almost the exact same mod list (pretty close to vanilla), Dyndolod close during generating lod without any message or any logs. I used many times without trouble Dyndolod in the past, first time I have this issue.

Hope this is the right place to ask help.

Thanks !

Check the Windows Event log.

[MaarMalur]

47 minutes ago, sheson said:

Check the Windows Event log.

I ran Dyndolod (same issue happenned) and checked the Windows Event and nothing special sadly. I'll try to disable half of my mod and rerun Dyndo to see if it does the same.

[sheson]

33 minutes ago, MaarMalur said:

I ran Dyndolod (same issue happenned) and checked the Windows Event and nothing special sadly. I'll try to disable half of my mod and rerun Dyndo to see if it does the same.

If a program is terminated like that, it is not a simple error problem caused my mods. If there is not even a crash log recorded in the Windows Event log, then the OS/3rd party/driver/hardware issue seems likely. Especially if it happens at different times in the process. Set realtimelog=1 in the DynDOLOD_SSE.ini, then check the debug log it has written to see how far it got.

If it is at time of high CPU in DynDOLOD + LODGens (open task manager to see CPU and memory usage), make sure cooling is sufficient, BIOS settings for CPU and memory are correct. Maybe test high load with the usual programs (Prime95 for example.)

[MaarMalur]

47 minutes ago, sheson said:

If a program is terminated like that, it is not a simple error problem caused my mods. If there is not even a crash log recorded in the Windows Event log, then the OS/3rd party/driver/hardware issue seems likely. Especially if it happens at different times in the process. Set realtimelog=1 in the DynDOLOD_SSE.ini, then check the debug log it has written to see how far it got.

If it is at time of high CPU in DynDOLOD + LODGens (open task manager to see CPU and memory usage), make sure cooling is sufficient, BIOS settings for CPU and memory are correct. Maybe test high load with the usual programs (Prime95 for example.)

Ok, I see. Unfortunately, I don't have the realtimelog line in the DynDOLOD_SSE.ini. I use the 3.0. My new setup is way more powerful than my older setup, this is strange if it's doesn't handle correctly DynDOLOD generation process. I will check my task manager next time I use it. Thanks for your help.

[sheson]

1 hour ago, MaarMalur said:

Ok, I see. Unfortunately, I don't have the realtimelog line in the DynDOLOD_SSE.ini. I use the 3.0. My new setup is way more powerful than my older setup, this is strange if it's doesn't handle correctly DynDOLOD generation process. I will check my task manager next time I use it. Thanks for your help.

If a line in an INI file does not exist just add it.

[Surtensoita]

Hello,

I was trying to run DynDOLOD 3 in order for it to generate some Seasons of Skyrim LODs in order to test it out before I do some more work on my mod list.

I downloaded the Alpha-88 version of DynDOLOD 3.00, with the Alpha-24 resources. I was able to run TexGen, and have its output activated as a mod in Mod Organizer 2. The thing is, any time I run Dyndolod after that, it just closes after making my selection when it gets to this point:

The options I chose are Tamriel (Skyrim) - Skyrim.esm [Seasons], and then Medium. I've also tried with the Low option, but I get the same result. Same thing happens if I run MO2 with or without administrator mode. I have attached my load order, my modlist up until now and the two logs that generate when I run DynDOLOD.

Does anyone have any idea what might be causing this issue? If there's anything that I'm missing, please tell me and I will be happy to provide it if I can.

Thank you in advance.

loadorder.txt Modlist.txt DynDOLOD_SSE_Dynamic_LOD.txt DynDOLOD_SSE_Object_LOD.txt

[sheson]

23 minutes ago, Surtensoita said:

Hello,

I was trying to run DynDOLOD 3 in order for it to generate some Seasons of Skyrim LODs in order to test it out before I do some more work on my mod list.

I downloaded the Alpha-88 version of DynDOLOD 3.00, with the Alpha-24 resources. I was able to run TexGen, and have its output activated as a mod in Mod Organizer 2. The thing is, any time I run Dyndolod after that, it just closes after making my selection when it gets to this point:

The options I chose are Tamriel (Skyrim) - Skyrim.esm [Seasons], and then Medium. I've also tried with the Low option, but I get the same result. Same thing happens if I run MO2 with or without administrator mode. I have attached my load order, my modlist up until now and the two logs that generate when I run DynDOLOD.

Does anyone have any idea what might be causing this issue? If there's anything that I'm missing, please tell me and I will be happy to provide it if I can.

Thank you in advance.

loadorder.txt 1.08 kB · 0 downloads Modlist.txt 2.31 kB · 0 downloads DynDOLOD_SSE_Dynamic_LOD.txt 25.76 kB · 0 downloads DynDOLOD_SSE_Object_LOD.txt 413.16 kB · 0 downloads

See the first post of the DynDOLOD 3 Alpha thread where to make posts. I moved your post to the thread.

See  the first post which log, debug and bugreport.txt to upload when making post. If none of them exist because the OS, antivir or whatever just killed the program, check the Windows event log for related messages and post that.

Set realtimelog=1 in ..\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and try again. Upload the log from the logs folder.

Make sure the hardware (CPU, memory in particular), BIOS setting, OS etc. are stable.

[Surtensoita]

My apologies for not doing it correctly the first time.

I checked my DynDOLOD_SSE.ini and there is no option called realtimelog.

Here are the three files that I could get from the required ones.

bugreport.txt DynDOLOD_SSE_Debug_log.txt DynDOLOD_SSE_log.txt

[sheson]

31 minutes ago, Surtensoita said:

My apologies for not doing it correctly the first time.

I checked my DynDOLOD_SSE.ini and there is no option called realtimelog.

Here are the three files that I could get from the required ones.

bugreport.txt 509.78 kB · 2 downloads DynDOLOD_SSE_Debug_log.txt 654.72 kB · 2 downloads DynDOLOD_SSE_log.txt 9.2 kB · 2 downloads

The log files seems to be from newer sessions that do show the error from the bugreport.txt.

Delete the entire log folder and bugreport.txt and then run again. Upload new bugreport.txt and logs.

Then delete those files again. Replace DynDOLODx64.exe with this version and test if runs through.

[Surtensoita]

After deleting it and then re-running, none of the files were created again. These are the only two files that were generated, in case they're useful:

DynDOLOD_SSE_Dynamic_LOD.txtDynDOLOD_SSE_Object_LOD.txt

After trying the new .exe, same thing happened, but at least logs were generated back again:

DynDOLOD_SSE_Debug_log.txtDynDOLOD_SSE_Dynamic_LOD.txtDynDOLOD_SSE_log.txtDynDOLOD_SSE_Object_LOD.txtbugreport.txt

[sheson]

1 hour ago, Surtensoita said:

After deleting it and then re-running, none of the files were created again. These are the only two files that were generated, in case they're useful:

DynDOLOD_SSE_Dynamic_LOD.txt 25.76 kB · 0 downloads DynDOLOD_SSE_Object_LOD.txt 413.16 kB · 0 downloads

After trying the new .exe, same thing happened, but at least logs were generated back again:

DynDOLOD_SSE_Debug_log.txt 654.37 kB · 0 downloads DynDOLOD_SSE_Dynamic_LOD.txt 25.76 kB · 0 downloads DynDOLOD_SSE_log.txt 8.96 kB · 0 downloads DynDOLOD_SSE_Object_LOD.txt 413.16 kB · 0 downloads bugreport.txt 35.85 kB · 1 download

The log and debug you are uploading seem to show DynDOLOD was started and then cancel was clicked.

Do not start the program again after there was an error, so the debug log is not being replaced.