TexGen.exe detecting Enderal even though Enderal is not installed

[TwoArmedMan15]

Hello. My friend is having issues with TexGen detecting Enderal, even though he does not have Enderal installed. TexGen displays "Ender found..." in the log, then begins searching for Enderal textures and errors out when it can't find the non-existent textures. Has anyone else experienced this issue? What could be the cause?

 

I was wondering, does TexGen detect Enderal by looking for a regeistry key? While he doesn't have ENderal installed anymore, my firen d did have Enderal installled a while back, and he just deleted the files. If the Enderal launcher created a registry key and TexGen looks for this to detect the mod, that might be the issue. Otherwise, I'm stumped...

[sheson]

DynDOLOD and TexGen check for a record in Skyrim.esm that is unique to Enderal. The Skyrim.esm presented to DynDOLOD/TexGen has to be from Enderal, as no other Skyrim.esm contains worldspace "Vyn" with the exact same form id.

 

I suggest to look at the first few lines of the log that show which data path, ini and and plugin list are currently used. Unless the game path is defined as command line parameter -D: "c:\path\to\Skryim\data" it is looked up in the registry, of course. Every tool has to do it that way or prompt the user for it. Run the games launcher to update the information in the registry.

Edited August 19, 2017 by sheson

[TwoArmedMan15]

  On 8/19/2017 at 8:05 PM, sheson said:

DynDOLOD and TexGen check for a record in Skyrim.esm that is unique to Enderal. The Skyrim.esm presented to DynDOLOD/TexGen has to be from Enderal, as no other Skyrim.esm contains worldspace "Vyn" with the exact same form id.

 

I suggest to look at the first few lines of the log that show which data path, ini and and plugin list are currently used. Unless the game path is defined as command line parameter -D: "c:\path\to\Skryim\data" it is looked up in the registry, of course. Every tool has to do it that way or prompt the user for it. Run the games launcher to update the information in the registry.

Thank you for your help. However, I already checked his Skyrim.esm and Update.esm, and they are the correct Skyrim ones. I also already checked the plugin and loadorder TXTs referenced in the log, and none of these files contain Enderal references. What's really bizarre is that Dyndolod works fine; only TexGen is detecting Enderal. if TexGen adn Dyndolod use the same mechanism for detecting Enderal, why would only TexGen detect it in this case?

[sheson]

The same Skyrim.esm can not give different results for the same command used by both applications. They must be each loading a different Skyrim.esm.

 

Compare line #458 in ..\DynDOLOD\Edit Scripts\DynDOLOD TexGen.pas to line # 500 in ..\DynDOLOD\Edit Scripts\DynDOLOD Worlds.pas.

 

My guess would be one application is started with a command line parameter and the other isn't or a different one. Or different profiles in MO.

 

Check the log for "Using Skyrim Data Path", second line usually.

Edited August 19, 2017 by sheson