Exit Code 1063

[Joat_Mon]

I must have made a mistake somewhere. Does the exit code give a clue as to where I need to start looking?

 

LODGen_SSE_Tamriel_log.txt

 

 

Skyrim Object LOD Generator 1.8.4.0
Created by Ehamloptiran and Zilav
Updated by Sheson

Log started at 6:25:53 PM
Game Mode: SSE
Fix Tangents: False, False, False, False
Generate Tangents: True, True, True, True
Generate Vertex Colors: True, True, True, True
Merge Vertex Colors: True, True, True, True
Merge Meshes: True
Grouping: False
Remove Faces under Terrain: True
Remove Faces under Water: True
Remove Faces Z-Shift: 10
Use HD Flag: True
Ignore Materials: False
Alpha DoubleSided: False
Use Alpha Threshold: False
Use Backlight Power: False
Use Decal Flag: False
Global scale: 1.00
Specific level: No
Specific quad: No
Output: F:\Tools\DynDOLOD\DynDOLOD_Output\Meshes\Terrain\tamriel\Objects
Using UV Atlas: F:\Tools\DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_SSE_atlas_map_tamriel.txt
Texture name already defined in atlas file textures\architecture\falmer hut\falmerhut.dds
Log ended at 6:25:55 PM
Code: 1063

 

[sheson]

Not only that, but also the accompanying message "Texture name already defined in atlas file ..." does as well.

 

Not quite sure how that can happen though. Something went sideways when generating the texture atlas definition file.

 

You could try again to see if it is a one time thing. If problem persists, check/post the DynDOLOD log and ..DynDOLOD\Edit Scripts\DynDOLOD\cache\DynDOLOD_SSE_atlas_map_tamriel.txt

[Joat_Mon]

This is the latest of several attempts with the same result.

 

The logs you requested were too large to post so I sent them to you via pm.

 

It is possible that I corrupted either the DynDOLOD executable or resources be accidentally starting two instances at the same time (double click on launch) on an earlier attempt, so maybe I need to do a clean install.

 

Thank you

[sheson]

Thanks I got the files. This seems like a rather odd error.

 

Even if you had multiple instances of something, it should always overwrite / replace the DynDOLOD_SSE_atlas_map_tamriel.txt file.

 

It seems that for some reason each run attaches the new data to it instead of replacing it.

 

I guess fr now the easiest solution would be to simple delete all files in ..DynDOLOD\Edit Scripts\DynDOLOD\cache\ before doing a new run.

[Joat_Mon]

I had already done a clean uninstall from Wrye Bash following the SSE and Main manuals instructions on that previous run, so I went ahead and deleted everything in my Games(F:)/Tools/DynDOLOD folder and reinstalled.

 

That solved the problem with one hiccup.

 

TexGen would not complete on the first attempt. So I closed ALL other programs (Firefox, Wrye Bash, Steam), rebooted and ran TexGen from the -sse shortcut in the DynDOLOD folder, installed TexGen_Output to WB and repeated the close out, reboot and ran DynDOLOD from its -sse shortcut and installed to WB.

 

Thank you Sheson, it all looks good in game, I guess the next thing is to attempt to learn to generate 3d lod.

[sheson]

great that it works for now. DO you happen to still have the TexGen log with the error? I would be interested in it to see if it is related somehow.

[Joat_Mon]

TexGen froze about 27 seconds in to the run, in processing 3 and had advanced to combining beehivelod.dds. That was the last thing on screen (I know because I watched for about 20 minutes for any signs of life).

 

I had to control alt delete out and it does not appear to have written anything to disk, which may have been the problem. My guess would be a race condition with all 8 threads at 100% according to HWMonitor. Sorry.

 

Skyrim SE is on a different computer from Skyrim and is on its own SSD (1 Tb), my OS's are on a different SSD (512 Gb). There is a lot of free space on both SSD's as my downloads and backed up mods and saves are on a separate hard drive.

[sheson]

Ahh I see, no log then, I thought there might have been an exception or error message of some kind. Thanks.

Edited September 10, 2017 by sheson

[Joat_Mon]

To follow up I checked Windows Event Viewer and it looks like we probably can blame this failure on Win10 1703.

 

At about the time TexGen froze, a number of other processes also failed because they "timed out", including a Windows Defender update. What it looks like happened is that Windows updated the system time at that point. It only changed a few seconds but the weird thing is the time stamp on the event entry shows like it happened exactly 5 hours earlier. This could be because it timed out also, maybe due to lack of processor availability and fell back on GMT briefly, maybe only milliseconds, but enough to cause processes to think they had timed out and therefore they failed. 

 

That's my best guess.

[sheson]

That kind of sounds terrible, but then 1703 is still beta, right? So anything is possible :)