Jump to content

Recommended Posts

Posted (edited)
3 hours ago, sheson said:

If you have crashes without DynDOLOD installed, fix those first. Only generate LOD output once those are solved and  the load order is finalized and working.

I can not help with crashes that already happen before generating DynDOLOD.

Maybe I misspoke but the game does not crash without DynDOLOD installed and the MemoryManager patch from SSE Engine Fixes (https://www.nexusmods.com/skyrimspecialedition/mods/17230) applied. I only included the crash from not using MemoryManager to see if maybe the usage of DynDOLOD was related to memory allocation and the memory manager didn’t work well with DynDOLOD.

To clarify, with my current load order and patches the game is completely stable, it is only when I install and activate the generation from DynDOLOD that I get crashes on reloading saves.

Edited by ArmchairNapoleon
Additional info
Link to comment
Share on other sites

4 hours ago, ArmchairNapoleon said:

Maybe I misspoke but the game does not crash without DynDOLOD installed and the MemoryManager patch from SSE Engine Fixes (https://www.nexusmods.com/skyrimspecialedition/mods/17230) applied. I only included the crash from not using MemoryManager to see if maybe the usage of DynDOLOD was related to memory allocation and the memory manager didn’t work well with DynDOLOD.

To clarify, with my current load order and patches the game is completely stable, it is only when I install and activate the generation from DynDOLOD that I get crashes on reloading saves.

You uploaded a crash log that does not contain any DynDOLOD plugins, so excuse my confusion.

Upload the DynDOLOD log and debug log as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

Edit ..\SKSE\Plugins\DynDOLOD_Data\DynDOLOD_NG_Worlds.txt with notepad and change to debug=true and under it add a new line debuglevel=2
Reproduce the crash.
Upload the crash log and c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log

Link to comment
Share on other sites

Posted (edited)

Hello

I am having some issues and I found the only "fix" for now is to deactivate the dyndolod dll NG while playing after generating the tex + lod (I get a wrong version message for the script at launch which is not good I guess). Every time I come out of a house (Solitude, Dawnstar) I get a constant CTD, removing the DLL NG and its scripts stops the CTD and all the LOD seems to be correct (guess it's not though because a script mismatch is never good)

I get this type or error https://pastebin.com/DCnCjZJ7

I'm using the latest version of the DLL NG (Alpha 24), the TEXGEN + LODGEN (with grass lod in 3.0a169 version) both resulted with success.  Maybe it not Dyndolod but a mod I use that has something that result in the CTD with the DLL on, If there is a real fix I could use, that's be great

[1:51:32] DynDOLOD plugins generated successfully
[1:51:32] Occlusion.esp completed successfully

...
[3:03:40] LODGenx64Win.exe generated object LOD for Tamriel WIN successfully
[3:03:40] LODGenx64Win.exe generated object LOD for Tamriel successfully

Edited by Hercules6969
Link to comment
Share on other sites

On 5/2/2024 at 10:34 PM, sheson said:

You uploaded a crash log that does not contain any DynDOLOD plugins, so excuse my confusion.

Upload the DynDOLOD log and debug log as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

Edit ..\SKSE\Plugins\DynDOLOD_Data\DynDOLOD_NG_Worlds.txt with notepad and change to debug=true and under it add a new line debuglevel=2
Reproduce the crash.
Upload the crash log and c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log

I apologize it took me a couple days to get everything together for you here. I have 8 logs for you, some edited filepaths only for privacy. I followed your instructions exactly, hopefully this is everything you need. Thank you again Sheson.

Crash log: https://ufile.io/liz2rs88

DynDOLOD_SSE_debug_log: https://ufile.io/1vphynb8

DynDOLOD_SSE_log: https://ufile.io/yi43sf3k

LODGen_log: https://ufile.io/0eoos12s

SSELODGen_log: https://ufile.io/rpq4job4

TexGen_SSE_debug_log: https://ufile.io/qakjfacg

TexGen_SSE_log: https://ufile.io/sm2a7tff

DynDOLOD.log: https://ufile.io/ddcvwvr2

Link to comment
Share on other sites

On 5/2/2024 at 2:48 AM, ArmchairNapoleon said:

https://pastebin.com/C7Jh3r3R

The disabling did not fix the issue.

Let me know if there is anything I can do to help. Would love to see my house from here without CTDing when loading saves.

Test if using this version of the DLL makes any difference https://mega.nz/file/1d42ybaJ#7wP8O_5MFg_J_h8VrJcva5ohz8ZB3aYMROI-6Vsg-Wk

If not, upload new version of DynDOLOD.log and try explain how to reproduce the crash.

Link to comment
Share on other sites

Posted (edited)

The game still crashes upon reloading saves.

Crash log: https://pastebin.com/DmNvJC5a

DynDOLOD.log: https://pastebin.com/gRDSf2fS

To reproduce crash

1. Activate all plugins (DynDOLOD resources, DynDOLOD DLL NG, xLODGen (terrain only) Output, TexGen Output, DynDOLOD Output). This will also activate the DynDOLOD.esm, Occlusion.esp, etc

1a. Sort plugins with the latest LOOT

2. Start game from interior cell

3. Go outside so that DynDOLOD activates, check and make sure DynDOLOD is active

4. Use quick, auto, or manual save

5. Reload that recent save (this is problematic as it can occur naturally, i.e. accidentally attack a guard, reload recent save after death, etc)

6. If the game does not crash (it does not always crash, but it never crashes without DynDOLOD activated, i.e. you can reload as many saves as you want with my modlist and it is stable), save again and try again

7. Repeat Step 6 until you experience crash-to-desktop (short load screen then game crashes)

Let me know if you need any other information, the above crash I reproduced in Riverwood, and it crashed on my first reload (my first attempt to reproduce)

Edited by ArmchairNapoleon
clarification and more info, detail
Link to comment
Share on other sites

On 5/6/2024 at 7:20 PM, ArmchairNapoleon said:

The game still crashes upon reloading saves.

Crash log: https://pastebin.com/DmNvJC5a

DynDOLOD.log: https://pastebin.com/gRDSf2fS

To reproduce crash

1. Activate all plugins (DynDOLOD resources, DynDOLOD DLL NG, xLODGen (terrain only) Output, TexGen Output, DynDOLOD Output). This will also activate the DynDOLOD.esm, Occlusion.esp, etc

1a. Sort plugins with the latest LOOT

2. Start game from interior cell

3. Go outside so that DynDOLOD activates, check and make sure DynDOLOD is active

4. Use quick, auto, or manual save

5. Reload that recent save (this is problematic as it can occur naturally, i.e. accidentally attack a guard, reload recent save after death, etc)

6. If the game does not crash (it does not always crash, but it never crashes without DynDOLOD activated, i.e. you can reload as many saves as you want with my modlist and it is stable), save again and try again

7. Repeat Step 6 until you experience crash-to-desktop (short load screen then game crashes)

Let me know if you need any other information, the above crash I reproduced in Riverwood, and it crashed on my first reload (my first attempt to reproduce)

Backup ..\skse\plugins\DynDOLOD_Data\DynDOLOD_NG_Tamriel.txt from the DynDOLOD output.

Edit it in notepad and find the section [Resets] near the bottom.
Remove all its entries and test if it makes a difference.

If not, find [Markers] in the middle and test if removing all its entries makes a difference.

If not, find [Objects] at top and test if removing all its entries makes a difference.

If removing all of the entries for a section made a difference, use binary search to narrow it down to a single line.

Binary search means to make a backup, remove half the entries, test if the problem is still there. If not restore backup and remove the other half. If the problem still exists repeat until you are down to a single or a couple entries left that are required to cause the problem.

If removing entries makes no difference at all, let me know.

Link to comment
Share on other sites

I have a weird problem I have been struggling with for hours on end but I can't find a solution. I'm a fairly experienced modder but this stumps me.

I'm on 1.5.97.

When I use DynDOLOD DLL NG the saw mill in Riverwood disappears. Well the logs are there, but not the saw mill itself. That seems to be the only problem , I haven't found anything else that disappears. In all other aspects DynDOLOD 3 seems to work fine, with grass LODs and all.

And if I deactivate DynDOLOD DLL NG in my mod list, after having run DynDOLOD 3, the saw mill is there. 

The problems I have encountered before always had to to with a new mod I installed (I'm a mod horder I'm afraid) and I have removed a number of mods I suspected, but no difference. I have even started a completely new installation of Skyrim 1.5.97 but that didn't help either.

It looks like it's, weirdly enough, DynDOLOD DLL NG that causes the problem - but I have been using earlier version of that mod and didn't have that problem. (I tried to download and earlier version of DynDOLOD DLL NG for testing but wasn't able to do so).

And yes, all mods that LOOT has found problems with are cleaned.

Any idea anyone, what I should try next?

Link to comment
Share on other sites

19 minutes ago, Gurion said:

I have a weird problem I have been struggling with for hours on end but I can't find a solution. I'm a fairly experienced modder but this stumps me.

I'm on 1.5.97.

When I use DynDOLOD DLL NG the saw mill in Riverwood disappears. Well the logs are there, but not the saw mill itself. That seems to be the only problem , I haven't found anything else that disappears. In all other aspects DynDOLOD 3 seems to work fine, with grass LODs and all.

And if I deactivate DynDOLOD DLL NG in my mod list, after having run DynDOLOD 3, the saw mill is there. 

The problems I have encountered before always had to to with a new mod I installed (I'm a mod horder I'm afraid) and I have removed a number of mods I suspected, but no difference. I have even started a completely new installation of Skyrim 1.5.97 but that didn't help either.

It looks like it's, weirdly enough, DynDOLOD DLL NG that causes the problem - but I have been using earlier version of that mod and didn't have that problem. (I tried to download and earlier version of DynDOLOD DLL NG for testing but wasn't able to do so).

And yes, all mods that LOOT has found problems with are cleaned.

Any idea anyone, what I should try next?

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload.
Also upload the DynDOLOD.log created by DynDOLOD.DLL NG as explained in https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing

Make a useful screenshot of the full model with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots

What is the problem downloading different versions of DynDOLOD DLL NG from https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Requirements?

Does this happen with a new game?

Does it happen with this test version? https://mega.nz/file/1d42ybaJ#7wP8O_5MFg_J_h8VrJcva5ohz8ZB3aYMROI-6Vsg-Wk

Link to comment
Share on other sites

6 hours ago, sheson said:

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload.
Also upload the DynDOLOD.log created by DynDOLOD.DLL NG as explained in https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing

Make a useful screenshot of the full model with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots

What is the problem downloading different versions of DynDOLOD DLL NG from https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Requirements?

Does this happen with a new game?

Does it happen with this test version? https://mega.nz/file/1d42ybaJ#7wP8O_5MFg_J_h8VrJcva5ohz8ZB3aYMROI-6Vsg-Wk

Firstly - many, many thanks for all your efforts with DynDOLOD. I couldn't imagine playing Skyrim without it.

Sorry I was a bit lazy and didn't read the documentation thoroughly. I will recapture what I did. Today I went on with DynDOLOD DLL SE instead and that worked fine (fully aware of the difference).

Yes, it happens with a new game.

I will try out the test version and report back to you (with log and screenshot).

Link to comment
Share on other sites

Gave the test version a quick try (just replaced the files without rerunning DynDOLOD) and it solved the problem. The Riverwood lumber mill  is visible again!

Got the error message "DynDOLOD.DLL and Papyrus scripts versions do not match". But that is as it should be, right?

Do you still need the logs and a screenshot when the lumber mill is missing? 

Link to comment
Share on other sites

1 hour ago, Gurion said:

Gave the test version a quick try (just replaced the files without rerunning DynDOLOD) and it solved the problem. The Riverwood lumber mill  is visible again!

Got the error message "DynDOLOD.DLL and Papyrus scripts versions do not match". But that is as it should be, right?

Do you still need the logs and a screenshot when the lumber mill is missing? 

Created a new DynDOLOD output with the test version. Problem gone! (Still got the error message about script versions though). Uploading screen shots and the debug log, just in case you want to have a look. Let me know if another log is needed.

ScreenShot1_Riverwood_Lumber_Mill_cropped.png

ScreenShot-with-moreinformativeconsole-Riverwood-Lumbermill.png

ScreenShot-YouAreHere_inside_Riverwood_Lumber_Mill.png

DynDOLOD_SSE_Debug_log.txt

Link to comment
Share on other sites

2 hours ago, Gurion said:

Gave the test version a quick try (just replaced the files without rerunning DynDOLOD) and it solved the problem. The Riverwood lumber mill  is visible again!

Got the error message "DynDOLOD.DLL and Papyrus scripts versions do not match". But that is as it should be, right?

Do you still need the logs and a screenshot when the lumber mill is missing? 

An error messages means, that there is an error and that something is not as it should be.

Make sure to keep the papyrus scripts from DynDOLOD DLL NG and Scripts Alpha 24 and that they overwrite DynDOLOD Resources.
Only replace the the DynDOLOD.DLL and the PDB from DynDOLOD DLL NG with the ones from the test version archive.,

If there is still an error message, upload the DynDOLOD.log and the papyrus script logs.

1 hour ago, Gurion said:

Created a new DynDOLOD output with the test version. Problem gone! (Still got the error message about script versions though). Uploading screen shots and the debug log, just in case you want to have a look. Let me know if another log is needed.

 

DynDOLOD_SSE_Debug_log.txt 160.31 kB · 0 downloads

The debug log seems stop after Background Loader: finished, so it does even show if DynDOLOD started or any information from the last generation.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs, which DynDOLOD log to also upload and the explanations how the debug log is replaced every session, while the normal log is appended to.

Link to comment
Share on other sites

Posted (edited)

Hey there Sheson, a new DynDOLOD DLL NG and Scripts 3.00 CTD Error for SkyrimVR, previous Alpha version 24 of DynDOLOD DLL NG and Scripts 3.00 still works good and produces no errors for VR before or after a Dyn compile, from what I can tell this looks like another PlayerEvent error.

Here's the Crash Log

Edited by ex0-tekk
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.