JustSomeGuy12345

I expected that as well you are right, but I wanted it to be known that I had the issue too which could mean a issue between the latest driver update and Texgen. As a update the solution above also worked for me. Specifically for anyone reading this and a little lost please navigate to the following folder: -Where you unpacked Dyndolod start by going to the "Edit Scripts" folder > DynDOLOD > TexGen_SSE.INI (Note: if you are doing this for a different game edit that games ini. Since I am doing this for Skyrim SE I edited the SSE ini) -Scroll to the bottom of the ini and add this at the very bottom: ;Fix Errors While Running RenderSingle=1 RenderTexturesSingleThread=1 As a side note. I noticed that Texgen does NOT work on some 4k monitors, specifically the start button is hidden. It of course will depend likely on your monitor type etc. but for my monitor the default scale is 300% and this is where the actual problem and solution lie. If you have issues seeing the entire popup window for Texgen and cant even run it because the button is hidden on you, right click your desktop and select "display settings" Change your scale to a lower number. For reference my default scale is 300 but I change it to 200 to run texgen. This allows me to see the entire window. Without changing the scale I cannot see or select the run button in Texgen. Im not sure if you will read this Seshon but out of intellectual curiosity when we add the two ini lines above are we just processing using a single thread meaning its no different from multi processing just slow? What would be the cause of this and can you explain to me why you thought (correctly so) that would be the solution?

Looking above your comment where I quoted this I only see the original post without a solution present but I also have this exact same issue. I see now I can scroll down for more posts and info and will but I am in the same boat here. I have the exact same issue and have the same setup. I just updated my drivers. Ill come back and attach logs after trying to update the ini per some of what I read above but I just wanted to make it known that I also have the exact same issue everyone here is describing. Moreover I checked VRAM and RAM no issues I have 64 gigs ram and a 4090 GPU and my vram is okay. Just thought Id mention it since I see you talking about it. Ill try the single threaded run or whatever it was I saw mentioned above. Ill make a new post if it works.