blueetenicolet
-
Posts
39 -
Joined
-
Last visited
Everything posted by blueetenicolet
-
Simple tested, the bug won't happen and Dyndolod installed successfully. I think it is fixed !
-
I 'm going on business trip now, i can test it about 2 days later.
-
I remember being in a similar situation: I can't start the sence that Balgruf lead you to Farengar to talk about bleakfall. Balgruf should lead you to meet Farengar, but he do nothing after dialogue, finally i found it was a guard mod caused that. One guard is considered doesn't matter and was disabled by the author, but in fact he's one Alias in a quest, and it caused that quest cannot run, then caused the bleak fall quest broken. Maybe this is the same? Some largeReference is Alias in some quest and was disabled by LargeReference workaround, so caused other quest damaged?
-
Ur, that still happens
-
txt here: Mega And In the log of SSEEdit, it seems only read from some esm plugins, not all esm.
-
Well, still couldn't help testing it. Test 1 : Delete Tamriel, still happen. Test 2: Delete all world space, still happen. Test 3: Delete Anything, make it a empty plugin, not happened. Test456789... Finally i found when i reserve "Game Setting" only(fLargeRefMinSize [GMST:00000F92], DynDOLOD.esm is 1 overwrite 512 in skyrim.esm), the bug will happen. And delete it only from plugin, the bug will not happen. I have checked no other plugin edited this record. I'm really going bed now XD , see you tomorrow
-
Ok, i'll do that tomorrow
-
Yes.Test with Resources and DLL NG scripts installed, DynDOLOD.esm,DynDOLOD.esp and oclusion.esp disabled, that will not happen.
-
Tested. That still happends.
-
I'm not sure the previous logs is with version 2 DLL or NG. I re-tested to repeat the bug with NG DLL. Here's the log. skse64.zip Here's log test with version 2 DLL skse64 Version2 DLL.zip
-
SKSE.zip
-
here MO2 tree.zip
-
I have tried read the "damaged" save with version 2 DLL, the quest target pointer still not displayed, so i think the bug is happend when save the game.
-
Oh and the crash log is created when i use version 2 DLL.
-
OK The LOD is generate with NG DLL and WorshipperACTI=0. use version1 (SE DLL) to test, still happens. use version2, not happen. And here's a new .Net crash log (the crash is caused by somthing other but not DynDOLOD i think), it contains the plugin informations(sorry i don't know other way to post the dll list XD) Crash_2023_1_3_20-13-26.txt
-
You mean generate LOD with version1/2 or just test the bug with them?
-
So my temporary way to fix it is use NG DLL scripts to generate, and use final test DLL to overwrite after generate, and enter game. Seems the LOD working well.
-
Oh NO... Sorry i just realized I made a mistake while testing. I use the final test DLL to overwrite the NG DLL after generate. I noticed that just now and disable the final test DLL test again, the bug will still happens.
-
Tested. The bug will not happened on the new generation.
-
Here's the ESM file DynDOLOD.esm
-
Tested with DynDOLOD.esm and with/without DynDOLOD.esp, no bug happened. Enable Resources and DLL scripts, DynDOLOD.esm,DynDOLOD.esp, test again, bug won't happend. Seems this test DLL have no problem. Good job! P.S : I test with dawnguard quest Touch The Sky again, also no bug here. NICE!
-
Resources ✔ DLL✔ -- bug Happend Resources ✔ DLL✖ -- NO bug Resources ✖ DLL✔ -- bug Happend Resources ✖ DLL✖ -- NO bug when Resources ✖ DLL(no scripts)✔ esm ✔ esp✔ -- bug Happend esm ✔ esp✖ -- bug Happend esm ✖ esp✖ -- NO bug
-
Test1: I delete the scripts in DynDOLOD-DLL-NG Scripts.3.00-Alpha-1, leave the dll only (DynDOLOD Resources still enabled) to test, a message shows: DynDOLOD papyrus scripts are the wrong version (as expected）. The bug still happen. Both the NG DLL and SE DLL. Test2: This time i disabled the DynDOLOD Resources too, test with the DLL only, bug still happens. Both the NG DLL and SE DLL. LOGS02.zip
-
Still happens. DynDOLOD.log Papyrus.0.log
-
Here's the log: Mega
