Jump to content

Recommended Posts

Posted
  On 1/10/2022 at 9:14 PM, burnersaurus said:

Hi Sheson

Thank you for replying.
I have read the FAQ, and done my best to follow your advice. I didn't have Wrye Bash installed prior to the issue, and though I've installed it now, I don't really understand, how making a bashed patch is supposed to help out. I've also checked all the mods/plugins that affect the cell with SSEEdit, and given them an auto clean for good messures. But none of them seem to have any errors. This seems futher collaborated by the fact, that when I disable all the mods that affect the Cell, I get the same error message, only then refering directly to the Skyrim.esm.

I'm kinda at my wits end. Went as far as making a clean install, using only the grafics mods i want for my loadout, but the problem remains the same.
Could the Skyrim.esm file it self be corrupted somehow?

Thank you again, for taking the time to help out.

Udklip.JPG

Expand  

Since you switched to DynDOLOD 3 alpha I moved the post the the DynDOLOD 3 alpha thread where all corresponding posts should be made.

See the first post which log, debug log and bugreport files to upload.

Also not the Copy this message to clipboard link to copy and paste the text of the message instead of making screenshot.

If you check a couple posts above, you will see SlapDaddy has a very similar error.

It is likely caused by a (new?) plugin. Once you upload the log etc. we might be able to spot similarities. The error will not be with a cell but with a worldspace record most likely.

The explanations about the Bashed Patch are about redoing a broken Bash Patch, not about creating one if none didn't exist before.

Posted
  On 1/10/2022 at 10:00 PM, burnersaurus said:

Hi again

Wasn´t sure if you ment me to post the logs and report in this thread, but either way, I've attached them bellow. 
SlapDaddys issue, does indeed sound similar, even refering to the same form ID.
I hope we can find a common sollution.

DynDOLOD_SSE_Debug_log.txt 177.01 kB · 1 download DynDOLOD_SSE_log.txt 342.43 kB · 1 download bugreport.txt 46.68 kB · 2 downloads

Expand  

Replace it with this version of DynDOLODx64.exe.

It should print a little bit more information to the log.

Post/upload new bugreport.txt and new DynDOLOD_SSE_Debug_log.txt.

Posted
  On 1/10/2022 at 11:24 PM, burnersaurus said:

Still the same unfortunatly.
But thank you for working on it :)

bugreport.txt 93.8 kB · 1 download DynDOLOD_SSE_Debug_log.txt 181.45 kB · 1 download

Expand  

I'm wondering, are you on the latest Skyrim Special Edition release? Or Have you run the Downgrade Patcher to continue playing? Not sure if that's part of the issue as I used it before without issue with the downgraded version. I'm also still using my USSEP 1.5.97. Trying to find if he have any similar mods that might be causing an issue.

Posted
  On 1/11/2022 at 3:18 AM, SlapDaddy said:

I'm wondering, are you on the latest Skyrim Special Edition release? Or Have you run the Downgrade Patcher to continue playing? Not sure if that's part of the issue as I used it before without issue with the downgraded version. I'm also still using my USSEP 1.5.97. Trying to find if he have any similar mods that might be causing an issue.

Expand  
  On 1/11/2022 at 6:47 AM, burnersaurus said:

I'm using the latest version of Skyrim Anniversary Eddition, and the non-downgrade version of USSEP (version 4.2.6a).  

Expand  

Run with this version and upload bugreport.txt and debug log please.

In MO2 enable the Installation column in the left mods window. Sorting by the installation date check which mods with plugins you updated/installed recently.

Posted
  On 1/11/2022 at 9:49 AM, burnersaurus said:

All done.

I reinstalled all of the mods yesterday, and I've never tryed using DynDOLOD before I ran into the issue, so it unfortunately seems difficult to troubleshoot by most recently added plugin..

bugreport.txt 44.36 kB · 1 download DynDOLOD_SSE_Debug_log.txt 241.23 kB · 1 download

Expand  

Those files seem to be from an older run they both show a date of 2022-01-09 and none of the additional debug message I added to the latest test version.

Probably best to delete old bugreport.txt and remove the log folder, then run the test version.

Posted
  On 1/11/2022 at 10:25 AM, burnersaurus said:

yep, still no logs.. any idea how I might unblock it? it did work with previous versions after all.

Expand  

Check task manager and kill any dead/hidden DynDOLOD processes or reboot.

If that is not it, temporarily try disabling antivir

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.