DYNDOLOD erroring out & TexGen paths

[Brooklyn670]

I am running Lexy's LOTD Guide and DynDOLOD is erroring out on me.  From the log:

 

[spoiler=Log Text]

[00:01:39.212] Combining 2 textures into textures\dlc02\lod\treepineforestbarkcompashlod.dds
[00:01:38.869]
[00:01:38.966]
[00:01:39.060]
[00:01:39.157]
[00:01:39.539]
[00:01:40.724] A call to an OS function failed
[00:01:40.750] D:\Mod Organizer 2 - Lexys LOTD SE\mods\TexGen_Output\DynDOLOD-temp\textures\dlc02\landscape\volcanic_ash_03.dds 256 256 0 0 textures\dlc02\lod\volcanic_ash_03lod.dds 512 512
D:\Mod Organizer 2 - Lexys LOTD SE\mods\TexGen_Output\DynDOLOD-temp\textures\dlc02\landscape\volcanic_ash_03.dds 256 256 256 0 textures\dlc02\lod\volcanic_ash_03lod.dds 512 512
D:\Mod Organizer 2 - Lexys LOTD SE\mods\TexGen_Output\DynDOLOD-temp\textures\dlc02\landscape\volcanic_ash_03.dds 256 256 0 256 textures\dlc02\lod\volcanic_ash_03lod.dds 512 512
D:\Mod Organizer 2 - Lexys LOTD SE\mods\TexGen_Output\DynDOLOD-temp\textures\dlc02\landscape\volcanic_ash_03.dds 256 256 256 256 textures\dlc02\lod\volcanic_ash_03lod.dds 512 512

[00:01:40.781] Removing temporary files
[00:01:40.987]
[00:01:41.019] Temp dir and files were sucessfully removed. No further action required.
[00:01:41.049]
[00:01:41.076] Copy textures from D:\Mod Organizer 2 - Lexys LOTD SE\mods\TexGen_Output\ to game directory or install to a new mod.
[00:01:41.102] Overwrite any vanilla or DynDOLOD LOD textures.
[00:01:41.127] Then run DynDOLOD.exe to generate LOD for world spaces.
[00:01:41.152]
[00:01:41.176] Completed successfully

 

At the beginning of the log, when Texgen sets up the paths, I see it is pulling paths from my User Drive.  None of my current MO2, SSEEdit, or DynDOLOD apps are running from UAC, but I may have had previous installations there at some point. 

 

[spoiler=Log Text]

[00:00:00.057] TexGen based on xEdit x64 (0D13DDD8) starting session 2019-11-22 17:42:49

[00:00:00.061] Using Skyrim Special Edition Data Path: D:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\Data\

[00:00:00.065] Using Backup Path: D:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\Data\SSEEdit Backups\

[00:00:00.068] Using Scripts Path: D:\Modding\Tools\DynDOLOD Standalone\Edit Scripts\

[00:00:00.071] Using Cache Path: D:\Modding\Tools\DynDOLOD Standalone\Edit Scripts\DynDOLOD\cache\

[00:00:00.075] Using Temp Path: C:\Users\Seth0067\AppData\Local\Temp\SSEEdit\

[00:00:00.080] Using ini: C:\Users\Seth0067\Documents\My Games\Skyrim Special Edition\Skyrim.ini

[00:00:00.084] Using save path: C:\Users\Seth0067\Documents\My Games\Skyrim Special Edition\Saves\

[00:00:00.088] Using Creation Club Content list: D:\Program Files (x86)\Steam\steamapps\common\Skyrim Special Edition\Skyrim.ccc

[00:00:00.093] Using plugin list: C:\Users\Seth0067\AppData\Local\Skyrim Special Edition\Plugins.txt

[00:00:00.099] Using settings file: C:\Users\Seth0067\AppData\Local\Skyrim Special Edition\DynDOLOD_settings.ini

 

1) Are the paths causing DynDOLOD to shut down?

2) Is there a way to reset the paths so that they point to locations off the UAC drive?

 

Thanks for any help anyone can give me here... almost done with this 2-week long installation and this hard stop is making me crazy, lol.

[sheson]

"A call to an OS function failed"

 

The Os, antivir or another 3rd party process is probably blocking access. Make sure none of that affects the TexGen.exe/DynDOLOD.exe and the LODGen.exe/Texconv.exe in the Edit Scripts folder or their x64 versions.

 

Any proper modding guide should have instructions moving the game outside of Programs Files x86 as part of the generic basic setup. That is unrelated to TexGen/DynDOLOD.

 

Files in C:\Users\Seth0067\Documents\My Games\Skyrim Special Edition are where the game stores INIs etc. and not a problem.

Edited November 23, 2019 by sheson

[Brooklyn670]

Thank you, Dragon King, for your attention.  

 

I guess I had assuming that keeping the game installation off the UAC C: drive would be sufficient, and that having an install under D: would be enough to avoid problems, regardless of what the path names are.  Looking at the guide again, I see that this is a really bad assumption on my part, but am now locked out of moving my Skyrim install because of the recent update (which breaks SKSE).

 

:tears hair out in frustration, which is probably okay because there wasn't that much of it anyway:

[Brooklyn670]

Hi,  I figured out how to move my Skyrim install out of the (x86)Program Files path to a new location on the same D: drive (which is not the UAC C: drive).  Making sure all the MO2 paths were changed to the new location, I attempted to run again, and it looks like Texgen and DynDOLOD are having the same issue.  I am attaching the output logs (the app doesn't seem to be saving its log, so i cut/pasted from the app console directly). 

 

Just to help my sanity check my steps:

 

All game files are running from a Steam install on D: not under a Program Files path

All modding tools are running from a Modding\Tools directory (as above, not on the C: Windows drive)

MO2 is in its own root drive on the same D:

i have disabled Antivirus shield when running in case those are interfering 

 

Q: Are there any other OS processes I should be checking?

Q: Are there any other third party processes that are known problems?

Q: What else can I do here?

 

Thanks, in advance, for any help or guidance.

bugreport.txt

Dyn-Tex-Errors.zip

[sheson]

Just reading log messages seems rather self explanatory:

Missing textures in "meshes\dyndolod\lod\trees\treepineforestsnowl05_5141a436passthru_lod.nif" "textures\lod\sfo\vurt_lsnowypinelod.dds

 

In case the file texture mentioned shortly before or after actually exists in the load order, "System Error. Code: 2. The system cannot find the file specified" typically happens because of UAC, antivir or other third party software preventing access.

 

Not being able to execute TexConv typically happens because of UAC, antivir or other third party software preventing access. I suggest trying to test if TexConv works when being used directly from the command prompt. It might print additional information.

 

Try to adding exceptions for the programs, also right click and unblock if the options exists.

 

Do not  set the output folder to a mod folder in MO, folders part of its virtual file structure or game folders. 

Edited November 24, 2019 by sheson

[Brooklyn670]

I located the problem.

 

Turns out at some point the Texconv64 exe was hijacked by Avast Antivirus.  Reinstalling DynDOLOD addressed this.  Thanks for your attention!