aljoxo
-
Posts
9 -
Joined
-
Last visited
aljoxo's Achievements
Noble (3/12)
0
Reputation
-
I was able to successfully generate LOD on this version. Thank you sheson. here are the logs and debug logs in case they are of any use. Debug Log DynDOLOD_SSE_log.txt
-
Hey sheson, was busy yesterday so I was unable to test. I only included the edits regarding the older versions of DynDOLOD because I had them to test and figured that there was no harm in sharing the information. The BSOD was likely unrelated to DynDOLOD anyways, I was just documenting it. For the record the mega file's exe was named DynDOLOD.64.exe instead of DynDOLOD64.exe This new test version of Alpha179 log: attached debug log: https://drive.google.com/file/d/1m_jy_eiBPvGc9IdVvL28XKbIFzxEpatw/view?usp=sharing DynDOLOD_SSE_log.txt
-
Seems the issue is still persisting. DynDOLOD is still using Memory, but the CPU usage drops down to like 1/4th to 1/5th the usage prior to the step (this is consistent with the way it was behaving on 178 as well). Debug Log: https://drive.google.com/file/d/1MAxSqLX5BcxHnSFwfCkmygUGof-TVKGJ/view?usp=sharing DynDOLOD_SSE_log.txt Edit: tested alpha 173 and it seems to at least be making progress on the "exporting terrain height" step that 178/179test were stuck on, successfully moving on to creating texture atlases and generating tree LOD + dynamic LOD. Should note I am using the x64 version on Alpha 173. Edit 2: alpha 173 blue screened my PC Edit 3: successfully generated LODs on alpha 177
-
Alpha 178 consistently gets stuck and stalls on "exporting terrain height data" step. These logs are from me having let the program sit for ~20-30 minutes without any activity before closing the process. I have tried doing a clean reinstall of DynDOLOD, restarting my PC, and redoing my Antivirus exceptions (Windows Defender). However, I am not quite sure what else I should be doing to try and troubleshoot this. If anyone has any thought or advice I would love to hear it. Debug Log 1: https://drive.google.com/file/d/1ipqJGMscVJn_81En3AI8Tr6t1qAE06kQ/view?usp=sharing Debug Log 2: https://drive.google.com/file/d/1RQCUuzLbnX404yeLTCP3vD7IsUryRJ_v/view?usp=sharing DynDOLOD_SSE_log.txt DynDOLOD_SSE_log.txt
-
These logs were generated with alpha 13 and 14. My own logs are in there as well but those were the logs I had gathered for this issue. I have not tested alpha 15 or 16 since I reverted to using non-NG for the moment to fix the crash at the moment because I only have so much time to troubleshoot this crash and leaving my list in a broken state with a critical crash. BTPS and FSMP are completely unrelated to the crash, they only show up in the callstack because they show up in any callstack for any crash that occurs during a load screen since they hook the onframe function. The plugins loaded after DynDOLOD/Occlusion in these cases have absolutely no influence on whether or not the crash would occur, this was tested. As for the next troubleshooting steps you linked, we already tested Papyrus Tweaks' potential impact, the issue was present on version 13/14 with or without papyrus tweaks active and with or without papyrus tweaks' native speed setting. I will regenerate lod later this week if I have time using the new version of NG to try and reproduce the crash, but based on Blackread's earlier post, the issue appears to still be present on version 15/16.
-
Attached files are crashlogs generated from the crash after loading save, discussed above by Blackread. On 1.6 the crash address appears to be 09432E2 instead of 1.5's 902691 / C072DF. These logs were collected from 3 wabbajack lists (Fahluaan, Vagabond, and Nordic Souls) Nordic Souls and Fahluaan have both swapped from DynDOLOD NG to regular DynDOLOD scripts in recent updates (this past weekend) and the crashes ceased to occur. I have worked with Ylikollikas and other Wabbajack list developers over the past month trying to diagnose this crash, and with the removal of Dyn NG seemingly stopping the crash, I'm fairly confident in saying the issue was a part of DynDOLOD NG version 13+ (though ylik and I originally believed it to be an issue with DynDOLOD alpha 154+ which came out around the same time), as the crash on load popped up in several Wabbajack lists after the move to NG version 13. I would have liked to test this by trying downgraded version 12 at some point but I did not have access to the archive file anywhere so I was unable to. crash-2024-02-12-05-34-36.log crash-2024-02-14-05-24-21.log crash-2024-02-14-05-41-43.log crash-2024-02-15-04-32-05.log crash-2024-02-16-23-12-00.log crash-2024-02-18-19-11-57.log crash-2024-02-19-19-53-16.log crash-2024-02-20-21-25-10.log crash-2024-02-21-20-01-28.log crash-2024-02-21-22-49-03.log crash-2024-02-22-19-53-19.log 1-crash-2024-02-09-20-46-20.log 1-crash-2024-02-13-03-57-35.log Crash_2024_2_22_15-11-58.txt Crash_2024_2_22_15-32-22.txt crash-2024-02-04-10-58-17 (1).log crash-2024-02-04-13-03-52 (1).log crash-2024-02-05-21-26-00.log crash-2024-02-10-19-34-47.log
-
Thanks sheson
-
DynDOLOD_SSE_log.txt Debug log: https://drive.google.com/file/d/11qJQhS7Cao6Nx3cSQ_fKqkLpUBMfX0KO/view?usp=sharing
-
Latest version of DynDOLOD (alpha 138) and NG DLL (alpha 12) and Resources (alpha 41) Assertion failure (C:\Delphi\Projects\DynDOLOD3\Core\wbImplementation.pas, line 12868). bugreport.txt
