TexGen is being terminated prematurely, suddenly closes

[3fast5you]

So I tried to look around and search for someone with a similar issue, but couldn't really find a fix that worked. Apologies if I missed something.

TexGen stops responding and eventually crashes when it reaches the "Creating billboards" part.

No TexGen logs, but Event Viewer has this to say:

Faulting application name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61d2f1a9
Faulting module name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61d2f1a9
Exception code: 0xc0000005
Fault offset: 0x0000000000895869
Faulting process ID: 0x3428
Faulting application start time: 0x01d800ea10b45f2b
Faulting application path: C:\Faens C\Modding Utilities\DynDOLOD\TexGenx64.exe
Faulting module path: C:\Faens C\Modding Utilities\DynDOLOD\TexGenx64.exe
Report ID: 835b9ca3-7c4d-4d3c-81cc-f79c3c6f1465
Faulting package full name: 
Faulting package-relative application ID: 

Don't know if it is worth mentioning, but originally I had a different error message in the Event Viewer, but then I ran System File Checker, and now I get the above error.
Here is the one before I ran SFC:
Faulting application name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61d2f1a9
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1387, time stamp: 0x0b9a844a
Exception code: 0x0eedfade
Fault offset: 0x0000000000034f69
Faulting process ID: 0x592c
Faulting application start time: 0x01d800e553cf8a38
Faulting application path: C:\Faens C\Modding Utilities\DynDOLOD\TexGenx64.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: 07b3f337-478d-4cc7-951e-9de7a42acf16
Faulting package full name: 
Faulting package-relative application ID: 

[MrTanku]

2 hours ago, sheson said:

Check if the event id 1000 is preceded by other events with a similar timestamp. For example like event id 1005 like shown in the screenshots of from this post https://stepmodifications.org/forum/topic/15606-dyndolod-300-alpha-65/?do=findComment&comment=256156

Make sure Antivir or other 3rd party tools are not interfering.

Check the used filesystems/disks for errors.

80070070 =  ERROR_DISK_FULL

Free up some disk space. Seems c: is full.

This is the only event within that time frame. I also did revert back to using version 2.98 and I'm not getting any problems. Gonna reinstall the latest version in another folder to see how it goes.

[MrTanku]

12 minutes ago, MrTanku said:

This is the only event within that time frame. I also did revert back to using version 2.98 and I'm not getting any problems. Gonna reinstall the latest version in another folder to see how it goes.

Didn't work, I'm getting the same error 

[sheson]

On 2/12/2022 at 9:57 PM, MrTanku said:

Didn't work, I'm getting the same error 

Set RealTimeLog=1 in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and upload whatever files have been written to the log folder.

It is hard to troubleshoot if the OS just terminates the program without  letting it go through its own exception handler and shutdown procedure.

[MrTanku]

2 hours ago, sheson said:

xEdit/xLODGen/DynDOLOD like any other whatever version use the Windows Registry entry for the game to find the data folder.

See https://dyndolod.info/Messages/Windows-Registry-Key how to update it.

Set RealTimeLog=1 in ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and upload whatever files have been written to the log folder.

It is hard to troubleshoot if the OS just terminates the program without  letting it go through its own exception handler and shutdown procedure.

TexGen_SSE_realtime_log.txt

[sheson]

48 minutes ago, MrTanku said:

TexGen_SSE_realtime_log.txt 322.23 kB · 1 download

This is with the latest Alpha-69?

Test if still happens when setting R8G8B8A for diffuse alpha and normal specular on the left and R8G8B8 for diffuse and normal on the right.

Clean out log beforehand, upload new log if it still happens.

Keep an eye on memory usage with task manager if possible.

1 hour ago, arzt1 said:

Hi Sheson,

I was just trying out powerof3's seasons with your newest v69. Works fine, no errors in creating LOD, but the tree LODs are messed up:

1) wrong tree LODS (e.g. colorful autumn leave tree LOD for a pine tree model), 2) tree LODs where no tree will be, 3) both of these combined, 4) purple LODs which vanish.. 5) summer model instead of winter model (very rare and not disturbing at all)

Using "Enhanced Vanilla trees" mod. Problems existing still when coc to a location and ONLY when switching to winter (only one I got). All other seasons (default) are OK.

Hope I am right here with my question? Thank you so much, have a nice weekend and don't you dare to answer me before next week!

Mike

MainFormSwap_WIN.ini 559.19 kB · 3 downloads

DynDOLOD_WIN.ini 32.95 kB · 0 downloads po3_SeasonsOfSkyrim.iniUnavailable Serialization.iniUnavailable

Upload the log and debug log from TexGen and DynDOLOD as explained on first post.

Reupload the po3_SeasonsOfSkyrim.ini which became "unavailable" (I have no idea why) maybe use paste.ee or ufile.io services instead.

Not sure what Serialization.ini is?

[MrTanku]

21 minutes ago, sheson said:

This is with the latest Alpha-69?

Test if still happens when setting R8G8B8A for diffuse alpha and normal specular on the left and R8G8B8 for diffuse and normal on the right.

Clean out log beforehand, upload new log if it still happens.

Keep an eye on memory usage with task manager if possible.

Upload the log and debug log from TexGen and DynDOLOD as explained on first post.

Reupload the po3_SeasonsOfSkyrim.ini which became "unavailable" (I have no idea why) maybe use paste.ee or ufile.io services instead.

Not sure what Serialization.ini is?

I used the settings above because the R8G8B8A setting was not available on the left column of settings 

TexGen_SSE_realtime_log.txt

[MrTanku]

On another note, I believe updates 65-67 worked for me in the past before I updated to this version.

[sheson]

On 2/13/2022 at 2:06 AM, MrTanku said:

On another note, I believe updates 65-67 worked for me in the past before I updated to this version.

Do you have any 3rd party crapware from AMD running that install with the driver installation?

See if anything behaves differently with newer Alpha versions.

[MrTanku]

9 hours ago, sheson said:

Do you have any 3rd party crapware from AMD running that install with the driver installation?

See if anything behaves differently with newer Alpha versions.

TexGen_SSE_realtime_log.txtsame behavior, worst case scenario I'd do a clean install....which I would rather not do atm.

[sheson]

1 hour ago, MrTanku said:

TexGen_SSE_realtime_log.txtsame behavior, worst case scenario I'd do a clean install....which I would rather not do atm.

If you mean the game or the OS, don't do that. The game install should have no direct affect on this (though it is possible that different input or the different output files size, content or whatever could have an affect)

You could try running in Windows safe mode, see if that makes a difference.

Check if there is anything different with this test version
If not, edit ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and add RenderThreads=1 right under [TexGen] at the top to test if that makes a difference.
If not, set OldMethod=1 in the INI to see if that makes a difference.

[MrTanku]

1 hour ago, sheson said:

If you mean the game or the OS, don't do that. The game install should have no direct affect on this (though it is possible that different input or the different output files size, content or whatever could have an affect)

You could try running in Windows safe mode, see if that makes a difference.

Check if there is anything different with this test version
If not, edit ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and add RenderThreads=1 right under [TexGen] at the top to test if that makes a difference.
If not, set OldMethod=1 in the INI to see if that makes a difference.

Oh wow, it worked. Dyndolod worked as well. May I ask what the RenderThreads command do? 

[sheson]

14 minutes ago, MrTanku said:

Oh wow, it worked. Dyndolod worked as well. May I ask what the RenderThreads command do? 

Instead of having the default of 2 threads, it does render in a single thread.

I take it you did that with the test version? If you could check if it also works with the alpha-71.

Then with either version remove the RenderThreads or set it to two 2 and then add a line RenderContexts=1.

Let me know if this works and compare time difference to RenderThreads=1

It won't be dramatic as far as I know.

[MrTanku]

7 minutes ago, sheson said:

Instead of having the default of 2 threads, it does render in a single thread.

I take it you did that with the test version? If you could check if it also works with the alpha-71.

Then with either version remove the RenderThreads or set it two 2 and add a line RenderContexts=1.

Let me know if this works and compare time difference to RenderThreads=1

It won't be dramatic as far as I know.

I haven't actually used the test version to run dyndolod. After adding that command, I ran LODGen which worked then moved to Dyndolod.exe without using the test version. And both worked afterwards with only the change to the lodgen.ini

[MrTanku]

So I changed renderthreads back to 2 and added that contexts command and I crashed. Changed it back to 1 with the contexts command and it did not crash.

[sheson]

24 minutes ago, MrTanku said:

I haven't actually used the test version to run dyndolod. After adding that command, I ran LODGen which worked then moved to Dyndolod.exe without using the test version. And both worked afterwards with only the change to the lodgen.ini

I assume you mean TexGen instead of LODGen

If you could just let me know if there is any difference with the test version. Most likely not.

You have an AMD graphics card right? No idea if it matters, just taking notes.

Oh, and if could check if the event log entry is always the same or not. Especially the exception address /fault offset.