LordOfTheNeverThere1992 Posted June 7, 2025 Posted June 7, 2025 2 hours ago, z929669 said: See the OP for which log files to include, depending on the problem you are having. Here's the logs that I could find related to DynDOLOD. There was no bugreport log file. DynDOLOD_SSE_log.txt DynDOLOD_SSE_Debug_log.txt I don't know why DynDOLOD is having issues with the rigmor_brumacitydoorsanim.nif but it's been crashing consistently when I run with DynDOLOD.esp enabled and the crash log points to that mesh.
sheson Posted June 8, 2025 Author Posted June 8, 2025 5 hours ago, LordOfTheNeverThere1992 said: Here's the logs that I could find related to DynDOLOD. There was no bugreport log file. DynDOLOD_SSE_log.txt DynDOLOD_SSE_Debug_log.txt I don't know why DynDOLOD is having issues with the rigmor_brumacitydoorsanim.nif but it's been crashing consistently when I run with DynDOLOD.esp enabled and the crash log points to that mesh. Does it alsocrash if you temporarily rename or remove meshes\terrain\rigmor_cyrodiil\impcity\rigmor_brumacitydoorsanim.nif in the ParallaxGen output, so it uses the one shipping with Rigmor of Cyrodiil? If it also crashes with the original NIF, test if using this test version of DynDOLOD.DLL makes a difference. https://mega.nz/file/0MYzjBYA#J_0-482cmXSeHh8a5dnlEdLFsU3xxEZKc3ov-WuSD2A Just replace the DLL and use existing outputs.
LordOfTheNeverThere1992 Posted June 8, 2025 Posted June 8, 2025 52 minutes ago, sheson said: Does it alsocrash if you temporarily rename or remove meshes\terrain\rigmor_cyrodiil\impcity\rigmor_brumacitydoorsanim.nif in the ParallaxGen output, so it uses the one shipping with Rigmor of Cyrodiil? If it also crashes with the original NIF, test if using this test version of DynDOLOD.DLL makes a difference. https://mega.nz/file/0MYzjBYA#J_0-482cmXSeHh8a5dnlEdLFsU3xxEZKc3ov-WuSD2A Just replace the DLL and use existing outputs. The new DLL fixed the issue. Thanks!
LordOfTheNeverThere1992 Posted June 8, 2025 Posted June 8, 2025 13 hours ago, LordOfTheNeverThere1992 said: The new DLL fixed the issue. Thanks! Actually I was mistaken. It fixes the issue when using the regular version of DynDOLODx64.exe but then that ruins the windmill fan again at Katla's Farm. Here's the logs from the build using the original DynDOLOD 3 instead of the test version that you gave me to fix the Windmill. This one doesn't cause a crash in the RoC exterior Worldspace with that new DLL. Maybe you'll spot the difference in the two versions that broke it: DynDOLOD_SSE_log DynDOLOD_SSE_Debug_log And here's the logs from the test version if you need them again for comparison: DynDOLOD_SSE_Debug_log (Test Version) DynDOLOD_SSE_log (Test Version)
sheson Posted June 9, 2025 Author Posted June 9, 2025 7 hours ago, LordOfTheNeverThere1992 said: Actually I was mistaken. It fixes the issue when using the regular version of DynDOLODx64.exe but then that ruins the windmill fan again at Katla's Farm. Here's the logs from the build using the original DynDOLOD 3 instead of the test version that you gave me to fix the Windmill. This one doesn't cause a crash in the RoC exterior Worldspace with that new DLL. Maybe you'll spot the difference in the two versions that broke it: DynDOLOD_SSE_log DynDOLOD_SSE_Debug_log And here's the logs from the test version if you need them again for comparison: DynDOLOD_SSE_Debug_log (Test Version) DynDOLOD_SSE_log (Test Version) Also upload ..\SKSE\plugins\DynDOLOD_Data\DynDOLOD_NG_Tamriel.txt Report result of this: Does it also crash if you temporarily rename or remove meshes\terrain\rigmor_cyrodiil\impcity\rigmor_brumacitydoorsanim.nif in the ParallaxGen output, so it uses the one shipping with Rigmor of Cyrodiil? If it also crashes with the original NIF, test if using this test version of DynDOLOD.DLL makes a difference. Just replace the DLL and use existing outputs. I assume the output when the crash happened originally was made with the test version and it stopped crashing when just the DLL was replaced. You then generated new output with the test version and the crash happened again. You then generated new output with the release version and the crash does not happen. Could it be that the crash is not 100% reproducibility?
LordOfTheNeverThere1992 Posted June 9, 2025 Posted June 9, 2025 9 hours ago, sheson said: Also upload ..\SKSE\plugins\DynDOLOD_Data\DynDOLOD_NG_Tamriel.txt Report result of this: Does it also crash if you temporarily rename or remove meshes\terrain\rigmor_cyrodiil\impcity\rigmor_brumacitydoorsanim.nif in the ParallaxGen output, so it uses the one shipping with Rigmor of Cyrodiil? If it also crashes with the original NIF, test if using this test version of DynDOLOD.DLL makes a difference. Just replace the DLL and use existing outputs. I assume the output when the crash happened originally was made with the test version and it stopped crashing when just the DLL was replaced. You then generated new output with the test version and the crash happened again. You then generated new output with the release version and the crash does not happen. Could it be that the crash is not 100% reproducibility? No the first time it didn't crash I accidently used the release version to make the DynDOLOD. It crashes consistently when I use the test version. Sorry for the confusion on that part. Here's the log you asked for from the release version output: DynDOLOD_NG_Tamriel.txt If you need the copy from the output with the test version for comparison then I'll need to recompile it again using that to get it so it'll take a little bit.
sheson Posted June 9, 2025 Author Posted June 9, 2025 1 hour ago, LordOfTheNeverThere1992 said: No the first time it didn't crash I accidently used the release version to make the DynDOLOD. It crashes consistently when I use the test version. Sorry for the confusion on that part. Here's the log you asked for from the release version output: DynDOLOD_NG_Tamriel.txt If you need the copy from the output with the test version for comparison then I'll need to recompile it again using that to get it so it'll take a little bit. I can not troubleshoot a CTD without the files relevant to the CTD. The formIDs of references/base records change which each generation for example. If you have a crash with DynDOLOD output, then upload the crash log, the corresponding DynDOLOD log, debug log, DynDOLOD_NG_Tamriel.txt DynDOLOD_NG_RigmorCyrodiil.txt and also ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt Use the test versions of DynDOLOD and DynDOLOD DLL you already have. Report the result of this: Does it also crash if you temporarily rename or remove meshes\terrain\rigmor_cyrodiil\impcity\rigmor_brumacitydoorsanim.nif in the ParallaxGen output, so it uses the one shipping with Rigmor of Cyrodiil
LordOfTheNeverThere1992 Posted June 9, 2025 Posted June 9, 2025 5 hours ago, sheson said: I can not troubleshoot a CTD without the files relevant to the CTD. The formIDs of references/base records change which each generation for example. If you have a crash with DynDOLOD output, then upload the crash log, the corresponding DynDOLOD log, debug log, DynDOLOD_NG_Tamriel.txt and also ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt Use the test versions of DynDOLOD and DynDOLOD DLL you already have. Report the result of this: Does it also crash if you temporarily rename or remove meshes\terrain\rigmor_cyrodiil\impcity\rigmor_brumacitydoorsanim.nif in the ParallaxGen output, so it uses the one shipping with Rigmor of Cyrodiil It still crashed with the one that ships with Rigmor of Cyrodiil. Here's the logs you wanted: crash-2025-06-09-19-35-33.log DynDOLOD_SSE_log.txt DynDOLOD_SSE_Debug_log.txt DynDOLOD_SSE_Object_Report.txt DynDOLOD_NG_Tamriel.txt
sheson Posted June 10, 2025 Author Posted June 10, 2025 10 hours ago, LordOfTheNeverThere1992 said: It still crashed with the one that ships with Rigmor of Cyrodiil. Here's the logs you wanted: crash-2025-06-09-19-35-33.log DynDOLOD_SSE_log.txt DynDOLOD_SSE_Debug_log.txt DynDOLOD_SSE_Object_Report.txt DynDOLOD_NG_Tamriel.txt Test what happens with this version of DynDOLOD DLL NG https://mega.nz/file/JURRQYwR#DB0snkpgG_tMwU32B1e9BI2fH55cgSz-YH_ewUNp8F4 Just replace the files and use the already existing output.
LordOfTheNeverThere1992 Posted June 10, 2025 Posted June 10, 2025 11 hours ago, sheson said: Test what happens with this version of DynDOLOD DLL NG https://mega.nz/file/JURRQYwR#DB0snkpgG_tMwU32B1e9BI2fH55cgSz-YH_ewUNp8F4 Just replace the files and use the already existing output. Alright, now it's not crashing anymore. Thanks!
sheson Posted June 10, 2025 Author Posted June 10, 2025 3 hours ago, LordOfTheNeverThere1992 said: Alright, now it's not crashing anymore. Thanks! Great. Thanks for letting us know.
Siruan Posted June 13, 2025 Posted June 13, 2025 190 hadn't had errors for me the last few times since I changed some antivirus rules and stuff. I ran it earlier today and it was all good. Then I updated everything to 191 and ran it twice. Texgen seemed to be fine. Dyndolod had some problems. First time my PC actually crashed which it hasn't done before. I've had the PC for about 2 months and it hadn't crashed before even when running stress tests. Second time Dyndolod gave an integer overflow error. https://www.mediafire.com/file/mohwln6kljp1t18/bugreport.txt/file https://www.mediafire.com/file/8nyku08y3jsc4bo/DynDOLOD_SSE_log.txt/file https://www.mediafire.com/file/pe3jpezswbaxok6/DynDOLOD_SSE_Debug_log.7z/file
sheson Posted June 13, 2025 Author Posted June 13, 2025 2 hours ago, Siruan said: 190 hadn't had errors for me the last few times since I changed some antivirus rules and stuff. I ran it earlier today and it was all good. Then I updated everything to 191 and ran it twice. Texgen seemed to be fine. Dyndolod had some problems. First time my PC actually crashed which it hasn't done before. I've had the PC for about 2 months and it hadn't crashed before even when running stress tests. Second time Dyndolod gave an integer overflow error. https://www.mediafire.com/file/mohwln6kljp1t18/bugreport.txt/file https://www.mediafire.com/file/8nyku08y3jsc4bo/DynDOLOD_SSE_log.txt/file https://www.mediafire.com/file/pe3jpezswbaxok6/DynDOLOD_SSE_Debug_log.7z/file https://dyndolod.info/FAQ#BSOD-Blue-Screen-Of-Death BSOD, the PC crashing or turning off is a hardware, BIOS setting, OS or driver problem. Is the integer overflow repeatable, did you try more than once? Delete all old logs. Run this test version https://mega.nz/file/ZBwHjRTS#lO3GYX9wfo0wwQ01CELqfw4GbMIbhbbTglT5Zu--ELg. Report result.
Siruan Posted June 14, 2025 Posted June 14, 2025 16 hours ago, sheson said: https://dyndolod.info/FAQ#BSOD-Blue-Screen-Of-Death BSOD, the PC crashing or turning off is a hardware, BIOS setting, OS or driver problem. Is the integer overflow repeatable, did you try more than once? Delete all old logs. Run this test version https://mega.nz/file/ZBwHjRTS#lO3GYX9wfo0wwQ01CELqfw4GbMIbhbbTglT5Zu--ELg. Report result. I just tried again with 191 and was able to finish without errors. Sorry, I thought the 2 times I tried before was enough. This time I also rolled back my GPU drivers as the new ones were causing graphical artifacts. Maybe that was actually the problem.
sheson Posted June 14, 2025 Author Posted June 14, 2025 39 minutes ago, Siruan said: I just tried again with 191 and was able to finish without errors. Sorry, I thought the 2 times I tried before was enough. This time I also rolled back my GPU drivers as the new ones were causing graphical artifacts. Maybe that was actually the problem. This is unrelated to graphics drivers. So it happened at least twice. Do you remember if it was the same worldspace and record? Delete all old logs. Run this test version https://mega.nz/file/ZBwHjRTS#lO3GYX9wfo0wwQ01CELqfw4GbMIbhbbTglT5Zu--ELg just once. Report if it works.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now