PumpkinHat

Hey sorry, I didn't see in the instructions that you could enable real time logging, it's made it much easier to see what is going on especially if the UI freezes by just tailing the log file. I really appreciate the patience you have with stupid people like me who don't read the entire documentation. Anyways, here is the realtime log from a DynDOLOD run that froze up when generating atlas for PalePass worldspace from LotD: https://ufile.io/fg14y8h9 It spit out a bunch of errors about missing textures and the UI and debug logs just stopped without the program exiting. The weird thing is, the very next run I did was fine and didn't even spit out those errors even though I'm pretty sure I didn't change anything between the runs. I think at least some of the times I though it was not working I exited prematurely because either the UI was frozen or it was stuck at the same spot for a very long time, but real time logging makes it much easier to tell if work is still being done. I'm not as worried about it anymore now that I can monitor the progress more reliably, but I thought I'd still provide the log just in case this is a bug and not just me being dumb.

I finally fixed it by rebooting my computer and disabling my bashed patch. I'm not sure which one fixed it but I would guess the bashed patch was the problem since it says in the console to disable it if you have problems I just didn't think the problems I was having, DynDOLOD just getting stuck, were caused by the bashed patch. If anyone else encounters this issue make sure to disable the bashed patch before you generate.

My bad I think that was from when I tried to run it with grass LODs but I didn't have a grass cache set up. I've been spending all day today trying to get appropriate logs but the program just keeps stalling freeezing. I let it run last night when I went to bad and it got most of the way through it but when I woke up the UI was frozen and I didn't have any plugins in the output directory so I don't think it finished. Some things I've tried: limiting the the program to only be able to use 12 cores (I have 16 physical cores), limiting the number of concurrent processes in the ini to 1 with MaxLODGen=1, limiting the number of threads to 4 in the ini with LODGenThreadSplit=4, but still no luck it always freezes or stalls around the time that it starts generating texture atlas for tamriel. I wish I could give you more relevant logs but it seems like it only writes them when the program either experiences a fatal error that causes it to crash or it finishes, neither of which are happening for me it's just getting stuck.

I'm running DynDOLOD through Mod Organizer 2 on Linux and many times it will just get stuck and stop doing anything. It's not that the program crashes it just stops spitting anything out to the console. Sometimes it does work and when it does it finishes in a little over 1 hour, but most of the time it just stops around "Creating texture atlas" for Tamriel. I've left it on overnight a few times and woken up to it still being stuck in the same spot. Looking at htop I can see that sometimes it will still be utilizing the CPU and the processes will still be in a running state but I just don't see anything happening. This doesn't happen for TexGen or xLODGen, both of which I can just setup and walk away and they will be finished when I come back. Does anyone know anything that I can do to make it more consistently work? It seems like the few times that I have gotten it to work it has been when I am actively doing other stuff on the computer. It hasn't worked if I just walk away. Some details that might help: I'm on Manjaro Linux. I'm running MO2 through Lutris with feral gamemode enabled. I have a very high end computer so I am confident it is not just taking forever just because of my hardware. I'm using GE-Proton9-23. I'm using DynDOLOD 3 Alpha 182 with the DynDOLOD DLL NG and Scripts installed and using the settings recommended by the STEP guide minus grass lods for now. Relevant log files, though the program doesn't usually crash so I don't know how useful these will be. https://ufile.io/73jrahs0 - bugreport.txt https://ufile.io/ai47a92u - DynDOLOD_SSE_log.txt https://ufile.io/ibt6r6mp - DynDOLOD_SSE_Debug_log.txt (very large!! over 300 MB)