DodoEgg
-
Posts
6 -
Joined
-
Last visited
DodoEgg's Achievements
Watcher (1/12)
0
Reputation
-
That seemed to complete succesfully, though texconv still opened. xEdit was very strange in task manager, appearing and disappearing randomly throughout the process. It also still suspended, seen in the log where it jumps from 05:57 to 07:32. At 05:57 it stopped, though I couldn't see it in task manager at all, just before that CPU usage was at 90-100% for a few seconds, then dropping to single digits when it stopped. Unsuspending xLODGen got it running again at 07:32, though when I tried to unsuspend Texconv, its status went to "terminated", despite xLODGen continuing the textures just fine, so I don't know if it those textures actually completed succesfully. log 2.txt
-
Basically yeah. I do see Texconvx64 in the task manager. Usually it shows up like in the attached image, but sometimes it won't show up under apps, instead under background processes. Occasionally there's also a command prompt window under xEdit (in task manager, I never physically see the other command prompt window). Yesterday the timing varied pretty massively, first run it went for about 17 mins, other times only a minute. Today's attempts all seem to stop at around 2:50-3:00, though once again, never at the same specific cell.
-
I'm not sure if this is the log window you meantlog.txt, but it's the only one I could see (I wasn't able to see the command window for Texconv). I've replaced any part that had my name with "name".
-
I've attached the SSELODGen, but it only seems to have last updated when I had an .ini issue after verifying files on Steam. Refreshing my .ini on BethINI fixed that. I don't think it's a time issue, I'm running on BC7 Quick for today's runs, most recent one it stopped at 3 mins, I left it on for 40 mins after that, zero change. Seems like a 50/50 chance now if it even gets to textures, and when it does, it'll run through several just fine, then at some point just stops at any random texture. My GPU is a 3060Ti, so unless Phoenix Flavour was made for absolute 1% spec, I don't think it should be giving up on this so easily. SSELODGen_log.txt
-
Sorry if I wasn't clear enough about it, it seemed quite similar from my view, down to the process sometimes not even showing in task manager at all despite literally running behind the task manager window. I've attached the log file, for info, I closed LODGen at 23:30 (so it basically stopped doing stuff 12 mins before I decided to close it). This time it didn't even get to the textures, though sometimes it does, sometimes it doesn't. LODGen_log.txt
-
I'm having a similar issue to @z929669 as above, where my SSELODGen just stops whatever it's doing at a seemingly random point. It goes to 0 % CPU usage, and eventually task manager just considers it suspended, resuming the process doesn't get LODGen going again either. Particularly Tamriel and Sovngarde seem to be problem spots, as smaller vanilla areas like Japhet's Folly and Markarth seem to work fine, unfortunately it seems to stop in a different place each time so I don't think it's a specific cell causing a problem. So far I've tried: Clean reinstalling LODGen Running outside of ModOrganizer only on vanilla files (still stopped working) Running with nothing else in the background Turning down settings according to the "first time" description on the download post (I was initially using settings from The Phoenix Flavour guide) Turning off antivirus and security Moving output folder to my NVMe drive (original location was on a HDD, everything related to mods and games is outside of UAC folders) Renaming executable to SSELODGen (removing x64) Unfortunately, because the process never "crashes", I don't have a bug report, though LODGen_log always ends like: Log ended at time Code: 0 With time being whenever it stopped running, whether it ran for 17 minutes before suspending or for half a minute. CPU usage sometimes gets high above 70% but never stays that way for more than a second. My CPU is a Ryzen 5 3600, and I have 16GB of RAM, so I don't think it's due to a lack of processing power. I've seen a few posts with similar issues to mine, but none of the given solutions have helped me yet.
