Jump to content
  • 0

TexGen is being terminated prematurely, suddenly closes


Question

Posted

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: 

  • Answers 110
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

Posted Images

Recommended Posts

  • 0
Posted
34 minutes ago, Aquos_666 said:

Make sure to use a legal game that does not contain corrupted assets or BSAs

Once TexGen reaches the end and waits for Texconv like this, give it time to complete. You system seems incredible slow and you might just be impatient for Texconv to finish at the end. You can check for Texconvs still working in Windows task manager.

Change texture compression to from BC7 to DX1 and DXT5 should reduce time and use of Texconv.

  • 0
Posted
21 minutes ago, Aquos_666 said:

thanks for your response.. for now i give up.. maybe my video card doesn't support texconv
and thanks for your time 

According to the logs Texconv is used without error many many times.

  • 0
Posted

I have tested the last 4 releases of TexGen64 with MO2 2.5.2 and a rather large mod list. So issue is present with Alpha-194 (DLL NG Alpha-36).
The program runs fine until it stalls for several seconds (last message: basic billboard records, so mods are loaded).
Afterwards it exits (or crashes) silently. I checked that all requirements are installed (Windows 10).

The problem is for me I have zero log output or bugreport files generated. The folder "Logs", "Edit Scripts", "TexGen_Output" are generated.
I also see that it generates several subfolders like Cache or Presets.

Are there any possibilities to find out what happens? I can only speculate if issues are related to mod conflicts in Bill Boards causing this behaviour or something completely else. As I tried out multiple releases and the behaviour is very similar, the issue could be unrelated to recent changes.

Last time I used TexGen64 in february (and the installation folder is still all the same as well as MO2 version), but the installation then was much smaller. The only thing what I could try beyond this is try to run TexGen64 with that much older release if that is helpful for analysis.

  • 0
Posted (edited)
4 hours ago, sheson said:

Moved to an appropriate thread for the problem. See posts above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to enable and upload the realtime log in case the program is terminated prematurely.

Thank you. I think I have found the cause why it was not started. The start of the UI was blocked by another program, that was already running a longer time in an unstable state (crash, restart). I also had issues with communication between MO2 and steam, but had not rebooted since I fixed it (only restarted steam and MO2).

So it looks like not an issue with TexGen64. The only thing I noticed that the logs are getting generated very late (which is good when you just accidently start and exit, but kind of confusing if you do not know that the UI should show up directly after "bill board gathering records" message. So thank you for the proper documentation link!

Edited by ssuamier1

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.