TexGen error code FFFFFFFF

[Completed]

Currently attempting to run TexGen for the first time using MO2. TexGen loads, but fails upon attempting to run Texconvx64 (returning error code FFFFFFFF, which doesn't appear to correspond to any of the codes listed for Texconv on the wiki). I've gone and done a fresh install of all the pre-reqs, and updated to the latest DynDOLOD standalone and resources packages. I didn't have any issues with xLODgen.

Not sure what I'm missing. See attached logs. Would appreciate any suggestions, since I'm getting zero hits for that error code on a forum search.

TexGen_SSE_Debug_log.txt TexGen_SSE_log.txt

[sheson]

3 hours ago, Completed said:

Currently attempting to run TexGen for the first time using MO2. TexGen loads, but fails upon attempting to run Texconvx64 (returning error code FFFFFFFF, which doesn't appear to correspond to any of the codes listed for Texconv on the wiki). I've gone and done a fresh install of all the pre-reqs, and updated to the latest DynDOLOD standalone and resources packages. I didn't have any issues with xLODgen.

Not sure what I'm missing. See attached logs. Would appreciate any suggestions, since I'm getting zero hits for that error code on a forum search.

TexGen_SSE_Debug_log.txt 158.74 kB · 0 downloads TexGen_SSE_log.txt 17.56 kB · 1 download

Install/update/repair https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist x64 version.

Open a command prompt and run Texconvx64.exe from it to see what it prints.
If it prints nothing, get official texconv from https://github.com/microsoft/DirectXTex/releases and run it from a command prompt, see what it says / posts its output. Do not replace texconv in the Edit Scripts folder.

[Completed]

I reinstalled the Visual C++ redist. Running Texconvx64 from cmd prints nothing.

Official texconv from the github prints the usage instructions. In case there's something interesting in there, I've copied that text to a text file and attached it.

github_texconv_results.txt

[sheson]

17 hours ago, Completed said:

I reinstalled the Visual C++ redist. Running Texconvx64 from cmd prints nothing.

Official texconv from the github prints the usage instructions. In case there's something interesting in there, I've copied that text to a text file and attached it.

github_texconv_results.txt 6.12 kB · 3 downloads

Let me know if there is anything different with this version https://mega.nz/file/YNIlXQ7C#-NY9FcWU1B8N_QdSxtRyNrgIih7cSxSPNy0EJKBF834

[Completed]

Thanks for looking into this for me, and hope you had a good new year!

Unfortunately, no obvious change from before with this new version. When run from the command prompt nothing is printed. I also temporarily substituted it for the texconvx64 in the edit scripts directory and tested it by running it through MO2, but also no change. See attached for the logs.

TexGen_SSE_Debug_log.txt TexGen_SSE_log.txt

[sheson]

9 hours ago, Completed said:

Thanks for looking into this for me, and hope you had a good new year!

Unfortunately, no obvious change from before with this new version. When run from the command prompt nothing is printed. I also temporarily substituted it for the texconvx64 in the edit scripts directory and tested it by running it through MO2, but also no change. See attached for the logs.

TexGen_SSE_Debug_log.txt 158.74 kB · 0 downloads TexGen_SSE_log.txt 17.56 kB · 0 downloads

What happens if you start TexGen directly without MO2?

[Completed]

The behavior is identical, just with a shorter list of bsa/esm/esp files background loaded in the dialog prior to texconvx64 failing.

 

[sheson]

2 hours ago, Completed said:

The behavior is identical, just with a shorter list of bsa/esm/esp files background loaded in the dialog prior to texconvx64 failing.

Is this a real Windows?

If you rename the official texconv.exe to texconvx64.exe and put it into the Edit Scripts folder does the log show the usage information as it did when running it from command prompt and then the same return code? The official texconv might fail later in the process, though.

[Completed]

15 hours ago, sheson said:

Is this a real Windows?

If you rename the official texconv.exe to texconvx64.exe and put it into the Edit Scripts folder does the log show the usage information as it did when running it from command prompt and then the same return code? The official texconv might fail later in the process, though.

Yes, it's a normal Windows 10 installation.

I went ahead as you suggested and replaced texconvx64 with the official texconv (renaming it in the process), then ran TexGen through MO2. The dialog showed the background loader messages and then it successfully opened the TexGen options form (dialog box for output path, LOD options etc). I ran it from there, and it managed to complete generation. What's interesting is that I then switched the files back, and now texconvx64 also works when running TexGen from MO2. I made no other changes.

Frankly, I'm baffled as to why that did the trick, but I'm not going to complain. 

Thanks so much Sheson for your help in puzzling this out.