Oozaru85
-
Posts
11 -
Joined
-
Last visited
Everything posted by Oozaru85
-
Omg, yes! Changing my virtual memory settings actually fixed it! Works smoothly and fast again, now. Thanks!
-
1. I was going to try lower settings there next, with lod8=billboard4 and lod16=billboard4 or billboard1, but I'm not really into wating 3 hours again for occlusion data to be generated just for this. Unless I can rerun the lod generation and don't have to re-generate occlusion for that small change of tree lod quality? 2. Maybe, I was going to order a new SSD and make a clean new install of Win10 anyway. Hopefully this is going to fix it. But wouldn't the OS slow down all of Dyndolod, also the lod generation and not just occlusion? 3. The last time when it worked fast and flawlessly was few weeks ago. I was still on Dyndolod 3 alpha 106. BUT it was also on this version few days ago when this issue first happened, thats the reason why I updated to alpha118. But this didn't fix it sadly. 4. Yes, been running it on OcclusionMaxThreadsObjectLOD=1 all the time now, and nothing changed.
-
The output folder without the occlusion esp is 6GB. HLT? Do you mean Happy Little Trees? If so, then no, not just that. I have HLT with ultra tree LODs but also the ultra tree LODs for Aspen Ablaze. But Ive been using them before with the same Dyndolod settings (lod4=level0, lod8=level1, lod16=level2) and never had any such issues. As I said, nothing changed there. Dunno why I'm suddenly having such issues. Oh, you mean just the Tamriel output? Not sure, Im not at home rn. Will have to check later. But since its the biggest output I assume its at least 4-5GB. Alright, so the Tamriel folder has 6.75GB. Pretty big. Still, I'm pretty sure it wasn't that much smaller the last time I ran Dyndolod without these issues. So it's kinda hard to believe this is an issue now. I will try generating occlusion with the latest LodGen, tho I doubt this is gonna change anything. Nope, same thing with the latest xLodGen. Also, my CPU goes up to 100% and RAM to 99%, before my system freezes completely. My specs aren't that bad, however: i5-10400F GTX 1080 16 Gigs DDR4 Win10 Pro 64-bit (SSD) And Dyndolod and SSE as well as my MO2 mod folder are also on an SSD (all on the same one, not the system one tho).
-
Alright, occlusion generation finished now, after 3(!) hours. Attached the log file. The debug log has not updated after I restarted Dyndolod, but I'm gonna attach it anyway. Also, no bug log generated this time since the process finished successfully. DynDOLOD_SSE_log.txt DynDOLOD_SSE_Debug_log.txt
-
I did that, but I have to wait for the occlusion generation process to finish before any logs are being updated, dont I? Cant just cancel the process, no logs will be created then, will they? And as I already mentioned, I did all the other suggestions you linked. My load order hasnt changed since the last time I generated my Dyndolod Output few weeks ago (besides adding a few armor and skse mods). It worked with no issues back then, didnt even take an hour and didnt freeze my system. Im also not using grass lod. I have no idea why Occlusion generation takes 5 hours suddenly and freezes my whole system. Never did that before with the same load order. 1 hour 40 minutes past now btw, my system is still frozen, system clock still at 10:00am (its 11:42am now), and Dyndolod is still running (even tho no progress is visible due to the system being frozen). I fear this will take as long as last night, again. Even with OcclusionMaxThreadsObjectLOD=1. Im at my wits end here. Waiting for this to finish and spit out some usable logs.
-
Yeah, I changed that back to 4 because it didnt do anything. I set it to 1 again and am rerunning the occlusion generation now. I started at 10:00am (CET) and my system has been frozen since then and its 10:48am now. Im doing just Tamriel again this time. No other world spaces. But if this takes 5 hours again, Im done with this. Will post the logs as soon as Dyndolod finishes.
-
Alrighty, my bad. here you go: DyndolodDebug.log: https://ufile.io/7tqig6n9 and the bug report log file: https://ufile.io/b3td747c Thats all I have. This is the latest debug files after I let Dyndolod run again the Occlusion generation today (or rather tonight). Took almost 5 hours again, just for the Occlusion only, and in the end it didn't even finish this time, it crashed for some reason it seems. Hope these files give some input into whats going on. Also, already tried all the memory fixes you posted, but they didn't help.
-
Hey, Sheson. Not sure if anyone posted this issue already but Im having a huge issue with Occlusion generation for some reason. It worked with no issues before, but now for some reason it takes forever and freezes my whole system while generating it. I had to run Dyndolod for 5 hours, just because of the slow Occlusion generation process. Couldnt use my pc during that time at all, system was completely frozen. So I rerun Dyndolod today without creating Occlusion, and it was finished after ~15 mins, with 41 world spaces being activated. The result was a 6gb zip file. Then In tried to create Occlusion seperately afterwards, just for Tamriel world space, but again during Occlusion generation my whole system froze and one hour has passed and nada. Any idea what could be causing this? As I said, this worked perfectly fine before with the same system specs. Ive even updated Dyndolod 3 to the latest vrsion, but this didnt fix it. LodGen has the same issue, btw. I use the default Occlusion settings btw. Didnt change anything there.
