ahrneely

I'm not quite sure I understand. Does this mean that if no error message appears the log wouldn't display the .dds file of the texture it's trying to convert? Therefore, my assumption that the x86 version "not calling a .dds" that the x64 version errors out on is invalid? (Which, by the way, is cool. As long as something is working, I guess I don't care how it works.)

Interesting effects to note: 1.) I ran SSELODGen through a command prompt as suggested. This time, the error messages each had to do with a VCRUNTUIME dll file and the percentage of errors dropped to 2%. 2.) I also ran the x86 version of SSELODGen through MO2. This returned zero errors. 3.) Neither of the above methods attempted to call .dds files that are being called when running the x64 version of SSELODGen through MO2. This leads me to believe I have something installed in MO2 that is telling xLODGen to look for .dds files that don't actually exist. More investigation is necessary. I'll report back if I make any discoveries.

This may be an inappropriate place to post this question and it may have already been answered somewhere else, but I'm struggling with xLODGen and haven't been able to find an answer anywhere else. I'm following the most recent iteration of the TucoGuide over on Nexus (TucoGuide 3.4.3.0) and have pretty much followed everything in the guide to the letter. I have reached the portion where they guide us through the use of xLODGen and have run into an issue. When I run SSELODGen, 90% of the functions return an error message. Those error messages look like this: [04:46] <Warning: Error reading texture Textures\Landscape\ReachDirt01_N.dds>[04:46] Error: Executing TexConv failure: "D:\Steam\steamapps\common\xLODGen\Edit Scripts\Texconvx64.exe" -nologo -y -f R32G32B32A32_FLOAT -o "C:\Users\[NAME]\AppData\Local\Temp\SSEEdit" "C:\Users\[NAME]\AppData\Local\Temp\SSEEdit\242B0E3ADB5D41F3B693026F6928C882.dds" After two hours of runtime, SSELODGen finished and left me with about 10% of processes that didn't return these error messages. Does anyone have any idea of what could be causing the error messages or what I could do about them? For what it's worth, <C:\> is my system drive and <D:\> is the drive where I keep SSE and MO2 and all mods. Thanks in advance! :-D