DynDOLOD DLL

[sheson]

12 hours ago, Aleximofo said:

What is NG?

https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds
NG means Next Generation and means the DynDOLOD DLL NG and Scripts work for Skyrim SE/Skyrim AE 1.5.x/1.6.x and Skyrim VR 1.4.15. This is all thanks to everyone involved around CommonLib/CommonLibSSE-NG and SkyrimSE RE.

[klesoo]

I recently upgraded to DynDOLOD alpha 165, the DynDOLOD NG DLL and run DynDOLOD with the Large Reference Bugs Workaround activated. Prior to this I did the clean save procedure as described on dyndolod.info.

After that upgrade I started having CTDs. Mostly when loading saves in caves but sometimes they also seemed to happen randomly in the Tamriel worldspace.

The first line of my crashlogs would always say "Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x7FFA255EC8A2 DynDOLOD.DLL+003C8A2 mov rcx,"

The FormID 003C8A2 refers to the sound AMBrDungeonCaveCrumbleSD. So I assume anytime this sound is present, my game somehow crashes to desktop. This happend with 100% certainty when loading a save in a cell where this sound is present. For instance, I could enter Fort Dawnguard, walk around and do whatever I want, there would be no CTD. However, if i saved in Fort Dawnguard and I later wanted to load this save, then my game would CTD. (This is not exclusive to Fort Dawnguard. It was the same for other cells but I didn't take note of their names.)

Switching to the standard DynDOLOD DLL and rerunning DynDOLOD without the Large Reference Bugs Workaround fixed this Problem for me. I can now load any new save in Fort Dawnguard (and any other place) without CTD.

I do not know if this is an error specific to my Load Order, but I thought it might be worth noting it here.

Spoiler

In my load order the mentioned FormID 003C8A2 AMBrDungeonCaveCrumbleSD gets modified by "Regional Sounds Expansion" (https://www.nexusmods.com/skyrimspecialedition/mods/77829) and the "Audio Overhaul for Skyrim - Immersive Sounds Compendium Compatibility Patch" (https://www.nexusmods.com/skyrimspecialedition/mods/36761).

 

[sheson]

On 2/3/2024 at 8:10 PM, klesoo said:

I recently upgraded to DynDOLOD alpha 165, the DynDOLOD NG DLL and run DynDOLOD with the Large Reference Bugs Workaround activated. Prior to this I did the clean save procedure as described on dyndolod.info.

After that upgrade I started having CTDs. Mostly when loading saves in caves but sometimes they also seemed to happen randomly in the Tamriel worldspace.

The first line of my crashlogs would always say "Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x7FFA255EC8A2 DynDOLOD.DLL+003C8A2 mov rcx,"

The FormID 003C8A2 refers to the sound AMBrDungeonCaveCrumbleSD. So I assume anytime this sound is present, my game somehow crashes to desktop. This happend with 100% certainty when loading a save in a cell where this sound is present. For instance, I could enter Fort Dawnguard, walk around and do whatever I want, there would be no CTD. However, if i saved in Fort Dawnguard and I later wanted to load this save, then my game would CTD. (This is not exclusive to Fort Dawnguard. It was the same for other cells but I didn't take note of their names.)

Switching to the standard DynDOLOD DLL and rerunning DynDOLOD without the Large Reference Bugs Workaround fixed this Problem for me. I can now load any new save in Fort Dawnguard (and any other place) without CTD.

I do not know if this is an error specific to my Load Order, but I thought it might be worth noting it here.

  Hide contents

In my load order the mentioned FormID 003C8A2 AMBrDungeonCaveCrumbleSD gets modified by "Regional Sounds Expansion" (https://www.nexusmods.com/skyrimspecialedition/mods/77829) and the "Audio Overhaul for Skyrim - Immersive Sounds Compendium Compatibility Patch" (https://www.nexusmods.com/skyrimspecialedition/mods/36761).

 

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts.

Obviously upload the entire crash log when reporting a CTD in the game.

003C8A2 is not a form ID. It is a relative memory address where the shown opcode is executed.

You are most likely not using the correct version of the DynDOLOD DLL NG for the runtime of the game.

[TheShadow208]

Happy Thursday everyone!

 

So, I need a tad bit of help and it might even be simple but, I haven't been able to find this same issue on Google so maybe someone else has experienced it.

 

I have DynDoLOD NG installed, running DynDoLOD 3 Alpha 167. I have all the resources I need installed and everything in the game looks fine (When I can get it to play.)

The issue at hand is when I have DynDoLOD NG installed with the DynDoLOD NG settings loader and all the required resources are still installed in the load order and I go into literally ANY save or new save, the moment I get into the gameplay (For me its as soon as I finish my character in Alternate Start) the settings for the DynDoLOD output show that initiated successfully in the top right, followed by a CTD about a second later. The closest I can get to figuring it out is maybe a heap memory error. But, running on any SE install that should no longer be a issue, AND on top of that, I set up page allocation to make 100% sure but no dice.

 

The ONLY way I can make the game run is either uninstalling DynDoLOD_output, or going to a really old save, mid-playthrough, where the changes are not 100% working properly.

 

This is my crash log as of right now: https://pastebin.com/AEPEhjhQ

If any logs from the DynDoLOD folder are required to help figure this out, I will gladly pastebin whichever one is required since there is a ton for each world space.

 

I would also love to be educated a tad bit on how to properly read these crash logs so I can self-troubleshoot better in the future. The best I have gotten so far is being able to figure out which texture/mesh is causing nasty-looking objects and correcting them in the mod folders (It's kind of fun to be completely honest)

[sheson]

On 2/16/2024 at 12:45 AM, TheShadow208 said:

Happy Thursday everyone!

So, I need a tad bit of help and it might even be simple but, I haven't been able to find this same issue on Google so maybe someone else has experienced it.

I have DynDoLOD NG installed, running DynDoLOD 3 Alpha 167. I have all the resources I need installed and everything in the game looks fine (When I can get it to play.)

The issue at hand is when I have DynDoLOD NG installed with the DynDoLOD NG settings loader and all the required resources are still installed in the load order and I go into literally ANY save or new save, the moment I get into the gameplay (For me its as soon as I finish my character in Alternate Start) the settings for the DynDoLOD output show that initiated successfully in the top right, followed by a CTD about a second later. The closest I can get to figuring it out is maybe a heap memory error. But, running on any SE install that should no longer be a issue, AND on top of that, I set up page allocation to make 100% sure but no dice.

The ONLY way I can make the game run is either uninstalling DynDoLOD_output, or going to a really old save, mid-playthrough, where the changes are not 100% working properly.

This is my crash log as of right now: https://pastebin.com/AEPEhjhQ

If any logs from the DynDoLOD folder are required to help figure this out, I will gladly pastebin whichever one is required since there is a ton for each world space.

I would also love to be educated a tad bit on how to properly read these crash logs so I can self-troubleshoot better in the future. The best I have gotten so far is being able to figure out which texture/mesh is causing nasty-looking objects and correcting them in the mod folders (It's kind of fun to be completely honest)

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts.

Read https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing which papyrus logs and which DynDOLOD.log to upload in case of problems.

[TheShadow208]

15 hours ago, sheson said:

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire DynDOLOD log and debug log to upload when making posts.

Read https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing which papyrus logs and which DynDOLOD.log to upload in case of problems.

I have gathered all the logs I believe are needed here: https://drive.google.com/file/d/1Ft-rNrpVyhrf8883vNzt_es_yqTiqNQw/view?usp=sharing

 

Thank you again for any help that can be made here

[sheson]

12 hours ago, TheShadow208 said:

I have gathered all the logs I believe are needed here: https://drive.google.com/file/d/1Ft-rNrpVyhrf8883vNzt_es_yqTiqNQw/view?usp=sharing

Thank you again for any help that can be made here

Replace the DynDOLOD.DLL in the SKSE\Plugins folder with this version https://mega.nz/file/JVwhBArD#tMNaTuvFniLU28g0XwPu6Zl_sKw7NXlMLbNvbS0ub8A which also includes a DynDOLOD.pdb.

Upload new log from crash logger which hopefully has some additional information for me.

[TheShadow208]

21 hours ago, sheson said:

Replace the DynDOLOD.DLL in the SKSE\Plugins folder with this version https://mega.nz/file/JVwhBArD#tMNaTuvFniLU28g0XwPu6Zl_sKw7NXlMLbNvbS0ub8A which also includes a DynDOLOD.pdb.

Upload new log from crash logger which hopefully has some additional information for me.

I'm sure its probably supposed to look like this, but dang that is a convoluted mess of a crash log haha!

https://pastebin.com/JnZfbRc3

Was this possibly meant for Farsveinn and not myself? I can't even get far enough to tell you if it looks better yet haha

[sheson]

On 2/18/2024 at 5:24 AM, TheShadow208 said:

I'm sure its probably supposed to look like this, but dang that is a convoluted mess of a crash log haha!

https://pastebin.com/JnZfbRc3

The crash log is set to private. Maybe try another service.

[TheShadow208]

8 minutes ago, sheson said:

The crash log is set to private. Maybe try another service.

Yes, that message was meant for someone else.

Here's a drive link instead: https://drive.google.com/file/d/1XECHgYNLrlomoCvu90v7bvJg-YKJbLO7/view?usp=sharing

No idea what happened with that pastebin haha

[sheson]

52 minutes ago, TheShadow208 said:

Here's a drive link instead: https://drive.google.com/file/d/1XECHgYNLrlomoCvu90v7bvJg-YKJbLO7/view?usp=sharing

No idea what happened with that pastebin haha

Doublecheck that there are no wrong/old scripts overwriting the ones from DynDOLOD DLL NG and Scripts.

[TheShadow208]

9 hours ago, sheson said:

Doublecheck that there are no wrong/old scripts overwriting the ones from DynDOLOD DLL NG and Scripts.

I removed DynDOLOD DLL NG and did a fresh install of it from Nexus just to be safe, as well as Address Library but I have the same result. I do not see any conflicts with scripts/old scripts to my knowledge

[TheShadow208]

42 minutes ago, TheShadow208 said:

I removed DynDOLOD DLL NG and did a fresh install of it from Nexus just to be safe, as well as Address Library but I have the same result. I do not see any conflicts with scripts/old scripts to my knowledge

I also just tried removing all existing mods that require PapyrusUtil SE support, just in case and ran a new save but I am getting the same results

[TheShadow208]

20 minutes ago, TheShadow208 said:

I also just tried removing all existing mods that require PapyrusUtil SE support, just in case and ran a new save but I am getting the same results

In light of possibly wondering if Alternate Start is somehow affected by the lack of standard Papyrus DLL. I have uninstalled it and any patches and am re-running TexGen and DynDOLOD NG to see if I get different results. Hopefully, this will allow the DynDOLOD MCM to configure without crashing. We shall see.

[sheson]

2 hours ago, TheShadow208 said:

I removed DynDOLOD DLL NG and did a fresh install of it from Nexus just to be safe, as well as Address Library but I have the same result. I do not see any conflicts with scripts/old scripts to my knowledge

Enable papyrus logging and upload it. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

2 hours ago, TheShadow208 said:

I also just tried removing all existing mods that require PapyrusUtil SE support, just in case and ran a new save but I am getting the same results

Those mods are irrelevant to the problem as they should not contain any DynDOLOD_Sheson_*.pex scripts.

1 hour ago, TheShadow208 said:

In light of possibly wondering if Alternate Start is somehow affected by the lack of standard Papyrus DLL. I have uninstalled it and any patches and am re-running TexGen and DynDOLOD NG to see if I get different results. Hopefully, this will allow the DynDOLOD MCM to configure without crashing. We shall see.

Alternate Start does not use PapyrusUtil SE.

Rerunning TexGen/DynDOLOD is irrelevant and not going to change anything.

There seems to be script  that is trying to use a Function that is included in DynDOLOD DLL SE. The functions is not properly implemented in DynDOLOD DLL NG since the papyrus scripts included with DynDOLOD DLL NG do not use it anymore. Hence why I believe there is an old script made for DynDOLOD DLL SE overwriting.

My theory might be wrong, though, hence why I am asking for the papyrus logs.