DynDOLOD suddenly closes without any pop-up (usually after 3 minutes or so)

[lighthouse-lady]

After installing all pre-requisites that support both TexGen and the new DynDOLOD Alpha 3.0 then successfully running TexGen and installing it's respective zipfile added into the folder (which I have placed into my C: drive and not any specific one folder)--I tried running DynDOLOD and through every attempt the window just decides to close without following up with a hint or anything that would help diagnose and locate the cause. I've tried reinstalling it with even the help of video and reinstalling the complimentarily required .NET and C++ and still the issue persists. The one thing I haven't tried that I can think of is just reinstalling the game itself and both TexGen & DynDOLOD but that would suck if it were caused by user error (which I'm definitively sure that it's me) that I overlooked. I asked around on reddit and received help from someone generous and was routed to come here instead. I'll hand over the same link I gave to them: https://workupload.com/file/4jbWsStCqvr. Thanks to whoever can help!

[sheson]

On 12/10/2024 at 4:26 AM, lighthouse-lady said:

Ok I'm stupid I was editing the DynDOLOD non-sse config instead of sse one. So after running the tool not only was the log created but the tool ran flawlessly this time. Is there a specific reason why this is so? Here's the log anyways if that helps with that question: https://ufile.io/pltiwpme. I'm not sure if there was something possibly bypassed by enabling this setting and that's what allowed the tool to run without being halted--but if this doesn't sound like a true solution to you maybe I should be doing something else? I've tried things like running the tool in administrator mode (yeah I know stupid) yet that did nothing and this did...

Writing the realtime log means the tool is using a bit less CPU and the entire process to take a bit longer. It will generate everything just the same, so the output is perfectly usable.

[lighthouse-lady]

I see, do you think there is a clear explanation for this anyways? Have you encountered someone that this worked for as well? It just seems kind of strange but of course I'm glad that it works at least!

[sheson]

8 minutes ago, lighthouse-lady said:

I see, do you think there is a clear explanation for this anyways? Have you encountered someone that this worked for as well? It just seems kind of strange but of course I'm glad that it works at least!

Less demand on certain resources so the situation with the error is avoided. Probably happened before trying to troubleshoot TexGen being terminated IIRC. 

[lighthouse-lady]

Makes sense. I seriously doubt I would have managed to pin down the problem without you so thank you so much for helping a newbie like myself! Have a good one!

[lighthouse-lady]

So I just wanted to follow-up with this issue as I didn't want to rely on a workaround but also I was really curious what cause of it is especially after reading this windows error;

"Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Taking Your Firstborn because of this error."

I know that windows errors can be rather cryptic when diagnosing application failures and this is especially true when I know myself that this could not be a hardware issue after stress-testing as you've mentioned and no other signs of failure (I forgot to mention that I am using a 12700kf cpu) and modern. So I looked over my windows firewall settings and which applications are allowed to run or not... but I could not find "Taking Your Firstborn" (lol) anywhere in the list so I decided to just add it. Well--it runs perfectly now without the workaround. I realized building LODs for Tamriel was the most resource intense which is probably why it was blocked by my firewall (don't know why the application wasn't listed though... maybe it updates in realtime when it encounters a supposed threat unlike ones it recognizes by default). Just thought this might help anyone who is having the same problem. Thanks again though for your time in helping me solve this!

Edited Thursday at 05:59 PM by lighthouse-lady