ricojumpy

I will try that. Found a weird thing with Texture conversion command-line tool being in suspended state in task manager too when I left for a while to look for my dog. Couldn't find the dog and dyndolod got stuck. Looks like a multi pronged computer stuff porcupine designed by architects to make you go crazy.

--> Well, that got better as Dyndolod began generating meshes for Tamriel but it silently quit as it did so, leaving only a command window updating the lod that close once it finished and dyndolod stayed closed (and indeed, it looks like adrenalin software froze). I will try 22.5.1 later. Removing Radeon Software is like removing your driving wheel to me or at least the assisted direction, I won't do that. Thanks for trying to find a solution ! Will try to get a bit of fresh air and everything will magically work later.

Might have found something else in windows events log : As for the drivers, not sure what we can do. Users do use the Radeon Software, there is not really a way to avoid that. Running a test with updated .net routines.

Sorry about RTFM. Here is the debug if ever it is relevant.

Well it is 150Mb heavy so not sure I could. Disk usage is really abysmally low when Dyndolod64 runs so that is linked to the file system access issue. Latest windows updates were Defender definitions. I guess I am screwed until another official windows 11 update to test out if insider build caused that as I don't want to reinstall windows for now. I should try to rerun the texture gen to see if the issue happens on there now too as a test. Ah well. My old lod gen is working fine.

Hi, I upgraded Dyndolod resources to the latest etc. I used to be able to run DynDolod without any issues repeatedly in the last weeks (sometimes had to do a reboot of the computer for it to run). I am trying now to redo a LOD generation and Dyndolod keeps on encountering issues. Most of all if I run Dyndolod 64, the generation creeps to a very slow grind somehow. Windows 11 itself is slowed down (not the UI, just any action ; trying to open a folder will lead to a blue circle cycling for a while before the window explorer opens etc, same for the snipping tool). It's very much like the file system is slowed down to a crawl. This did not happen in the weeks before. There was actually a windows update yesterday. But I have added all exes and folders and even processes to exceptions to windows defender. I even turned off real time protection, changed folder spots etc. I checked for issues with the hard drive but everything is healthy without any issues whatsoever (2tb sn850 pcie4). The slowed down/hanging file system is really weird. I just forced exit a texture process that was not moving in task manager and Dyndolod gave me a code 5 access denied message. Looking at DynDOLOD_SSE_Debug_log.txt ; it looks like Dyndolod is doing stuff all this time (but it's been 20+ minutes without any update on the main window). Dyndolodx64 rand yesterday one last time properly, I just removed a flickering waterfall fix after that to generate lod again and since then it will just have that behavior. Well, I can still use my old lod but it really puzzles and frustrates me to encounter this weird filesystem slowdown when running Dyndolod which never happened before. Any help would be appreciated. bugreport.txt DynDOLOD_SSE_log.txt Cut DynDOLOD_SSE_Debug_log.txt