Epslion_09cc

I see, and now I know why this problem occured. Guess what is it? Few hours ago I was troubled cause Nemesis seems didn't work: deleted animations still being generated and worked fine over and over again! At that moment I felt like being kicked at my head: Idealism is happening! Holy wonderful god I am in the 11th dimension! I gave a reasonable guess then: goddamn DISK been gone. And yes, SMART info of my HHD verified my suspecting. I bet it's the second a**hole incident in 4 years. That's out of my edge. Seagate ST1000LM049. Worse thing is I am going waste money & time now LMAO. A dramatic week I have.

Uh..Sorry? I didn't follow. As you mentioned unable to bind script.. happend everytime, that probably caused by anything stop mod loading but mods themselves. But as you said just now, unresolved form IDs. In fact I did error check for DynDOLOD plugins in xEdit few days ago, it prompted no errors were found. Should I understand the words you mean is the problem can also result from unresolved form ID?

Alright...That's confusing? I use MO2 also to manage FO4, Skyrim LE, FNV(TTW), even Anomaly(Stalker Mod). Most CTDs that I encountered as far as I could tell should be caused by available memory lacking, especially in FO4. Hard to imagine that, maybe I have to care about something out of game managing itself.. Thanks for technical supporting anyway.

Thanks mate, but that makes no sense. I installed resource file for 6 times at least. And I just checked my resource file folder, It looks like that: https://imgur.com/a/RNUFKHz And here is the Script folder looks like: https://imgur.com/a/yHeP9Zt I will try only with DynDOLOD to generate files later, and re-install all files of course. I already even tried, vanilla game +skse +USSEP +DynDOLOD. Still same problem, Unable to bind script.. Yes I am 100% sure I re-install resource files and re-generated files. Here is the DynDOLOD log: https://ufile.io/cxubudq6

https://ufile.io/f/m4vox Here are my logs, Papyrus logs and NetScriptFramework logs. I checked the help docs earlier, but while doing I was under the side effect taking anti-cold drug, so no progress in checking. I may will do a more detailed checking later, I am really tossed, thinking about why the hell "LOD generation" could problem me for goddamn 4 days.

First, using alpha 53 of DynDOLOD 3, and the generation is fine, no interrupt in whole process. But while using DynDOLODx64.exe to generate it goes with heavy number of "Warning: Overwritten large reference in.." or "Warning: Initially disabled large reference in..", and few Warning: File not found.. I move the outputed file and create as a mod, load it and sort order, everything is OK. In game, the LOD looks fine and nothing obvious wrong. BUT, when I move to a specific area(Windhelmet indeed), probably as the LOD near it started loading, the game crashed. By reading README, I do what the manual said. Hide generated mesh folder, Crashed. Hide DynDOLOD.esp, No Crash. Also, tons of error in Papyrus Log like that below: Same error "Unable to bind script SHESON_DynDOLOD_.." filled almost the whole log. I searched for long time and trying find a similar issue like this, but there isn't any. I don't know what's wrong with the damn mod file, I suffered this dumb problem for totally 3 days. Also, I tried using the latest & stable version, DynDOLOD 2.96 and Resource 2.88 in Nexus Page, same. Tried take off other irrelevant mods, keep only enviorment mod then generate LOD, same. NEED HELP PLS