Veyrah

Yeah I'm stupid I got all the file versions wrong, sorry for wasting your time.

I got the steam version but changed some things to be able to use a certain version of SE for a certain SKSE version. Everything runs fine so far so I didn't expect it to be a problem for DynDolod. Which it isn't really as I am able to generate the lods when using 512 texture size just fine, so the program is working. Just setting it to 1024 makes it "run out of memory", which doesn't seem likely to be the case as I have sufficient ram. Also I believe I have the latest DynDOLOD version as I downloaded it last week.

"Exception in unit userscript line 322: Error while creating image data with params: Width=8192 Height=4096 Format=A8R8G8B8. Exception Message: Out of memory" Is the error I am getting. I'm on a Windows 10 with 8gb ram. Using mo2 with SSE. Tried using the 64 bit exe but that gave me an "Access violation error". Running the x86 version works for 512 tile size, as I have tested and seen in-game. Do I not have enough system ram to generate 1024 tilesize? log: https://www.codepile.net/pile/v0R5BB65

Yeah been looking at the conflicts tab. After going through a few texture packs with each quite a few conflicts I kind of chickened out and hoped to find a better way to do this.

Hello! I'm using MO2 with SSE. While there are lots of things wrong with it I can't seem to go backt o NMM after using normal MO with oldrim. So aside from all the errors it throws at me I have a question about something that most likely would share functionality with the original one. Basically I want to save some hard drive space. My folder is getting quite big, while my game only really uses 70% of it due to all the texture packs that overwrite each other partly. Is there a quick way to delete all the files that get overwritten anyways? The alternative is going through every texture mod and deleting all that gets overwritten but this kind of manual labour is why things like MO exist right?

I'm sure I did all the steps correctly. This isn't the first time I installed/updated DynDOLOD, but it has been a while since the last time I updated. I'm gonna do it all over from scratch again, if I come across anything weird I'll tell you here.

I'm having this exact error after having updated from 2.XX to 2.35. It made me think I didn't clean my saves the right way, even though I did it exactly like in the manual. After 8 tries of cleaning my savefile and encountering that json error I found this thread. Turns out it's not my save files that are wrong, as even with new characters I get this error. That alternate SHESON_DynDOLOD_Firstborn.pex you posted here seems to work for me too, but I'm here to ask if that won't bring any instability issues in the long run, or if I should use a newer version of that alternate file as this thread was from april.