Caaros

As of now, Dyndolod is working properly once again. Thank you very much for your assistance.

I apologize if my post came off a bit rough. As said, I tried multiple areas on my computer and the only place it would work is the place it told me not to put it. I'm not on my main pc at the moment, but I believe the file path is something along the lines od D/Program Files/Dyndolod Folder, with everything nestled into that last part. Again, I apologize if I'm just being dense, but do you have any suggestions as to where I should put it? The obvious doesn't seem to work for me. I do have TexGen generating the largest textures it lets me, as I was confident that my computer could run it. How likely is this part of the problem? I'm guessing very. I could have sworn that, at least in previous versions of the program, I would frequently see the command prompt quickly open and close during the process, always after the point where it says the real work starts. I'm guessing that was and now no longer is a thing? Or am I mistaken entirely? I also apologize for my wording in the third paragraph there. Not the best choice of words, really. I do have to say that I wasn't aware that the window is supposed to be locked in place. Explains why I can neither move its position around or get it to show up above other windows. May I ask as to why that is? Again, I apologize if I'm being rude and/or dense here. I have a bad history with troubleshooting just about anything, so I consequently have very little patience for it. Nothing to do with you or your program specifically, in fact I really do appreciate what you've done for the modding community and how helpful you've been here. Thanks for all the help so far.

I used to store Dyndolod in a folder on my desktop called "Mod Tools", more specifically in a folder inside the aforementioned folder labelled "Dyndolod". It worked just fine for the longest time it was there, but upon updating to the latest version I would get an error that warned that the installation path was invalid, and that I wasn't supposed to put it in "special folders" like the program files, desktop, and game files. To be completely honest, I had no idea at the time what wasn't a special folder in that case, because a quick Google search on "special folders" essentially translated to "anywhere on your computer" to me. I might just be missing something vital, but what I do know is that putting it directly in one of the places it told me not to immediately fixed the immediate issue. Interestingly enough, going through each individual world space and rebuilding the atlas did not cause the error. Granted, it took a combined 2-&-a-half to 3 hours, with the Tamriel worldspace taking at least one hour on its own. Also granted, I never saw the command prompt open at all, which makes me doubt the actual efficiency of the apparent success. I am starting to think that if I started Dyndolod as usual and just didn't touch it at all for several hours, it would generate just fine. Which would be odd, considering that I could sit there and check on it just fine before recently. Just clicking on the window during the 'creating atlas textures' can and likely will freeze it for reasons beyond me. If this is all the case, the issue becomes "Why is dyndolod throwing a tantrum when I poke it while it works", but that would be a far more manageable issue than "it literally has a mental breakdown at the prospect of its own bloody job". Is there anything else you want me to try out or know before I make my attempt at just generating it like normal and leaving it be while it do? Should I delete everything in the output before I try again? Edit: So, for some reason I wasn't expecting the program to keep going after building all of those atlasses, so it may have in fact opened th cmd when I wasn't looking.

If I run the x64 version, it becomes unresponsive at the same spot that the 32 bit version produces the error. The only way I know to avoid this problem is to disable the generation of atlas textures in the advanced settings, which is what I probably did for the successful generation you are looking at. I am of the mind that this is probably an issue with the program suddenly being denied access to the command prompt, but I have no real clue as to how I should go about fixing that.

I'm just going to apologize now for how stupid I'm about to be. Pastebin's file size limit is only marginally larger than the one here, and I have no clue where in the log would signify the last generation, so I went full moron and just chopped the log up and made it into four separate pastes. I may have messed it up somehow, but I did my best. They are in chronological order and labeled as such, so it should be easy to figure out where it all goes. https://pastebin.com/ZYgPCB5Q https://pastebin.com/dJTzuzw4 https://pastebin.com/LrWpqWRx https://pastebin.com/qVxe2gfT The issue did start after an update to Malwarebytes, however disabling all protection features on the antivirus did not yield any results. I'm not sure how to check other things, but I do think this very well could be the issue. Strangely enough, the only place on my computer that I could find that Dyndolod didn't give me the invalid installation path error was the Program Files. Even putting it on its own in the D drive didn't work. I have no real clue where to put it. It may be just me being stupid though. I apologize if I'm being difficult here.