sheson Posted April 18 Author Posted April 18 47 minutes ago, Kattmandu said: I was referring to the scripts you provided once we stopped testing the DLL and started testing the script. The .txt files are only used by the DynDOLOD.DLL, so their content does not matter. I still wonder if any of the navmesh, NPC crashes can be made to happen without any DynDOLOD output, scripts and Resources at all and then again if they still happen with all other mods/DLLs restored or vice versa.
Kattmandu Posted April 19 Posted April 19 20 hours ago, sheson said: The .txt files are only used by the DynDOLOD.DLL, so their content does not matter. I still wonder if any of the navmesh, NPC crashes can be made to happen without any DynDOLOD output, scripts and Resources at all and then again if they still happen with all other mods/DLLs restored or vice versa. I will definitely try this and report my results. Just need to find time to designate an entire day of play testing Skyrim. Weather is warming up here so I've been doing a lot of work in the yard this week.
Kattmandu Posted April 20 Posted April 20 (edited) On 4/18/2025 at 12:33 PM, sheson said: The .txt files are only used by the DynDOLOD.DLL, so their content does not matter. I still wonder if any of the navmesh, NPC crashes can be made to happen without any DynDOLOD output, scripts and Resources at all and then again if they still happen with all other mods/DLLs restored or vice versa. When I test without DynDOLOD, should I only disable DynDOLOD Resources. DynDOLOD DLL NG, and DynDOLOD Output. Or should I disable other mods which add DynDOLOD meshes and textures such as Majestic Mountains DynDoLod 3 Pack and Aspens Ablaze Add-On - DynDOLOD 3? Also, should I leave xLODGen Output and TexGen Output enabled? Edited April 20 by Kattmandu
sheson Posted April 20 Author Posted April 20 1 hour ago, Kattmandu said: When I test without DynDOLOD, should I only disable DynDOLOD Resources. DynDOLOD DLL NG, and DynDOLOD Output. Or should I disable other mods which add DynDOLOD meshes and textures such as Majestic Mountains DynDoLod 3 Pack and Aspens Ablaze Add-On - DynDOLOD 3? Also, should I leave xLODGen Output and TexGen Output enabled? You can leave LOD resources from other mods enabled. Also leave terrain LOD meshes and textures enabled. 1
Kattmandu Posted April 23 Posted April 23 On 4/20/2025 at 11:38 AM, sheson said: You can leave LOD resources from other mods enabled. Also leave terrain LOD meshes and textures enabled. I can't seem to get the game to CTD without DynDOLOD Resources. DynDOLOD DLL NG, and DynDOLOD Output. However, after dying and loading saves many times (around 200 or so), it does eventually get to a point where NPCs won't move to attack me. They will only attack me if I'm directly in front of them.
sheson Posted April 24 Author Posted April 24 6 hours ago, Kattmandu said: I can't seem to get the game to CTD without DynDOLOD Resources. DynDOLOD DLL NG, and DynDOLOD Output. However, after dying and loading saves many times (around 200 or so), it does eventually get to a point where NPCs won't move to attack me. They will only attack me if I'm directly in front of them. OK, now enable only DynDOLOD.esm and DynDOLOD.esp - nothing else. Leave meshes, texture, SKSE folder hidden and do not activate DynDOLOD Resources or DynDOLOD DLL and none of the scripts. That hopefully should be fine as well.
Kattmandu Posted April 24 Posted April 24 5 hours ago, sheson said: OK, now enable only DynDOLOD.esm and DynDOLOD.esp - nothing else. Leave meshes, texture, SKSE folder hidden and do not activate DynDOLOD Resources or DynDOLOD DLL and none of the scripts. That hopefully should be fine as well. Occlusion.esp disabled as well?
sheson Posted April 24 Author Posted April 24 3 hours ago, Kattmandu said: Occlusion.esp disabled as well? Yes. 1
Kattmandu Posted April 24 Posted April 24 10 hours ago, sheson said: OK, now enable only DynDOLOD.esm and DynDOLOD.esp - nothing else. Leave meshes, texture, SKSE folder hidden and do not activate DynDOLOD Resources or DynDOLOD DLL and none of the scripts. That hopefully should be fine as well. Ended up getting a CTD upon death. crash-2025-04-24-16-22-19.log --> https://limewire.com/d/6U5Ce#Dn7C5jYZrm skse64.log --> https://limewire.com/d/99KCT#HsSK11vb93 Papyrus.0.log --> https://limewire.com/d/CZRGP#3JyX2LC48H
sheson Posted April 25 Author Posted April 25 14 hours ago, Kattmandu said: Ended up getting a CTD upon death. crash-2025-04-24-16-22-19.log --> https://limewire.com/d/6U5Ce#Dn7C5jYZrm skse64.log --> https://limewire.com/d/99KCT#HsSK11vb93 Papyrus.0.log --> https://limewire.com/d/CZRGP#3JyX2LC48H Another crash that seems related to the head of the player character. If you believe this has to do with the 2 DynDOLOD plugins, continue the test with only DynDOLOD.esm and not the DynDOLOD.esp. If that seems to make a difference, we will start removing stuff from the DynDOLOD.esp, otherwise from the DynDOLOD.esm.
Kattmandu Posted April 25 Posted April 25 5 hours ago, sheson said: Another crash that seems related to the head of the player character. If you believe this has to do with the 2 DynDOLOD plugins, continue the test with only DynDOLOD.esm and not the DynDOLOD.esp. If that seems to make a difference, we will start removing stuff from the DynDOLOD.esp, otherwise from the DynDOLOD.esm. I used a RaceMenu preset to create my character. I could try starting a new game and not use a RaceMenu preset.
sheson Posted April 25 Author Posted April 25 3 hours ago, Kattmandu said: I used a RaceMenu preset to create my character. I could try starting a new game and not use a RaceMenu preset. That is up to you. Do it with another profile maybe so we can go back back to this.
Kattmandu Posted May 4 Posted May 4 On 4/25/2025 at 11:50 AM, sheson said: That is up to you. Do it with another profile maybe so we can go back back to this. I started a new playthrough using the default Nord player character that Skyrim generates upon a new game (I didn't load a RaceMenu preset). I haven't experienced a CTD yet although I haven't logged an insane amount of hours on this playthrough either. I'm also using the latest DynDOLOD DLL NG test file with timestamp 2025-04-11-05-41. The gate at Fahlbtharz Grand Hall seems to be doubled. When I click on the lever, one set of gates open and the other remains shut. Also, the lever seems to be doubled. After clicking on it, one lever moves up while the other stays down. The current DynDOLOD DLL NG available on Nexus doesn't appear to have this issue. The DLL NG test file with timestamp 2025-04-06-06-15 is okay as well. The doubled gate and lever bug seems to have been introduced in the test file with timestamp 2025-04-06-10-17.
sheson Posted May 4 Author Posted May 4 25 minutes ago, Kattmandu said: I started a new playthrough using the default Nord player character that Skyrim generates upon a new game (I didn't load a RaceMenu preset). I haven't experienced a CTD yet although I haven't logged an insane amount of hours on this playthrough either. I'm also using the latest DynDOLOD DLL NG test file with timestamp 2025-04-11-05-41. The gate at Fahlbtharz Grand Hall seems to be doubled. When I click on the lever, one set of gates open and the other remains shut. Also, the lever seems to be doubled. After clicking on it, one lever moves up while the other stays down. The current DynDOLOD DLL NG available on Nexus doesn't appear to have this issue. The DLL NG test file with timestamp 2025-04-06-06-15 is okay as well. The doubled gate and lever bug seems to have been introduced in the test file with timestamp 2025-04-06-10-17. That test version is not fully functional. It would be best if for now you continue with the release version. Once there there is an, upload new logs. Then we continue testing with the fully function test version that has the changes based on our earlier troubleshooting. 1
Kattmandu Posted May 4 Posted May 4 3 hours ago, sheson said: That test version is not fully functional. It would be best if for now you continue with the release version. Once there there is an, upload new logs. Then we continue testing with the fully function test version that has the changes based on our earlier troubleshooting. CTD when manually loading a save. crash-2025-05-04-18-12-35.log --> https://limewire.com/d/8lGVw#8zLWZZAQVQ DynDOLOD.log --> https://limewire.com/d/qhcOB#1ic0hSTMXq (sorry, didn't have debug enabled) skse64.log --> https://limewire.com/d/BFa7Y#0AR7ZY7kz6 Papyrus.0.log --> https://limewire.com/d/nJKtT#RtXVm3Oijb
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