DynDOLOD Beta for Skyrim Special Edition, Skyrim VR and Enderal SE 2.98

[mikegray]

P.S. I figured out how to record videos and upload them ... 

 

https://www.youtube.com/watch?v=20UKrgu6tfs

[geraintwd]

A current MajesticMountains.esp installed with the the current game version does not have unresolved errors in my load order. My hunch would be that at least the Update.esm is outdated or that cleaning it went wrong.Other than that I can not really help with errors in 3rd party plugins. You need to ask the mod authors for help with their plugins.

You sir have hit the nail right on the head! A while back (probably more than a couple of updates ago), I cleaned my DLC esms and update.esm for UDRs and ITMs.

 

When I started this mod build, I put the cleaned versions in my data folder and have been using them since. Obviously it didn't occur to me that update.esm might occasionally be updated!

 

Fortunately, I had the sense to keep backups, so I've reverted to the (more or less - I disabled updates for SSE in Steam since the last update broke several SKSE mods) current version and cleaned that in SSEEdit.

 

Now my mods have no "could not be resolved" errors and DynDOLOD works perfectly with Majestic Mountains enabled.

 

Thank you so much for your patience and taking the time to help me, even though I am clearly an idiot!

[exploiteddna]

P.S. I figured out how to record videos and upload them ... 

 

https://www.youtube.com/watch?v=20UKrgu6tfs

that sir is not dyndolod -- to me it looks like a graphics card or driver issue. maybe something like ENB could cause that. i would be really surprised if that was dyndolod causing it.

 

 

You sir have hit the nail right on the head! A while back (probably more than a couple of updates ago), I cleaned my DLC esms and update.esm for UDRs and ITMs.

 

When I started this mod build, I put the cleaned versions in my data folder and have been using them since. Obviously it didn't occur to me that update.esm might occasionally be updated!

 

Fortunately, I had the sense to keep backups, so I've reverted to the (more or less - I disabled updates for SSE in Steam since the last update broke several SKSE mods) current version and cleaned that in SSEEdit.

 

Now my mods have no "could not be resolved" errors and DynDOLOD works perfectly with Majestic Mountains enabled.

 

Thank you so much for your patience and taking the time to help me, even though I am clearly an idiot!

"could not be resolved" means that the linked reference is not present. Many records in a plugin will have information that points to another record, either in the same plugin or a different one. If plugin A makes reference to something in Plugin B, but then for whatever reason Plugin B cannot be found or is not loaded properly, xEdit will show the "could not be resolved" error where the reference should be

 

how exactly this applies to you im not sure, as I dont fully understand what's going on with your situation. But if you were able to resolve it, thats all that matters.

 

But cleaning plugins or masters, in theory, should not affect references/ref links in any way. Cleaning will remove ITM records (but not actually remove the master record) and will find records that have the Delete flag and change it to an 'initially disabled' flag (UDR). This is what is meant by "undelete and disable references". Records get a "delete" flag anytime a mod author uses the delete function inside creation kit. If you click on an object in the world, hit delete key, it will remove the object from the default world, which adds the "delete" flag to that object reference, essentially telling the game not to render it.

 

EDIT: forgot to mention, I also have majestic mountains, and most/all of the other plugins that were mentioned and no probs here. only issue ive had recently was with the update, forcing me to downgrade back to 1.5.50

[mikegray]

that sir is not dyndolod -- to me it looks like a graphics card or driver issue. maybe something like ENB could cause that. i would be really surprised if that was dyndolod causing it.

 

Weird, huh?

 

And I agree - it looks more like a GPU/driver problem to me - only, I honestly haven't seen ANYTHING of the sort in any other game or situation. First thing I did back when I first got this glitch (about 6 months ago) was to turn off all my overclocks, reboot, restart the game. Sadly, no dice. But just to be sure, I haven't OC'd anything (CPU or GPU) since. 

 

Any putative connection to DynDOLOD never even crossed my mind, until I happened notice that exiting the flicker-cell, killing the game, deactivating DynDOLOD, restarting and re-entering the cell made the flicker disappear. (I wasn't even targeting DynDOLOD but trying to see if deactivating one DynDOLOD's masters might make a difference.)

 

Anyway, so far, DnyDOLOD is the first plugin whose deactivation seems to have any effect.

 

BTW, I DO have an ENB (latest build with Rudy - nothing exotic), and that was also one of my first hunches. Disabling ENB and re-entering doesn't seem to change anything - and I haven't noticed any other correlations over the last few months.

 

A couple other things come to mind:

 

- Maybe there's a funky interaction between DynDOLOD and some of the more exotic stuff going on in my Smashed Patch?? Smash does ALL KINDS of whacky stuff, and I have no idea what a lot of it even is, so I kind of wonder whether it is feeding some settings into DnyDOLOD that glitch out. (However: Since DnyDOLOD doesn't have any dependency on my Smashed Patch, I'm really not sure how that could work ... This is tin hat territory.)

 

- More reasonable: Maybe I accidentally ran "SSE NIF Optimizer" on a mesh it shouldn't have touched, and it's somehow corrupted in such a way that it doesn't actually REGISTER as corrupted (i.e., no messages in the DynDOLOD logs), but it's causing a weird interaction.

 

P.S. Here's my modwat.ch page:

https://modwat.ch/u/mikeroygray/plugins

[Godis]

Since 2.44 I'm not able to create any LOD for Bruma anymore. It always throws me the same error (But I don't remember the exact words currently...Sorry) It's something like: "This file cannot be mapped as master in the load order".

It only happens when I uncomment BSHEARTLAND in the worldspace ignore list and select it in the worlds window.

I tried to generate Dyndolod for Bruma seperately, but this way it throws me another error, something like: "DynDOLOD_SSE_childworldlod_BSHeartland.txt not found". And this file obviously doesn't exist anywhere.

 

On all previous versions of Dyndolod I was using, I never had a problem with it Bruma.

 

 

Ooops, seems I posted in the wrong section. I'm using SSE.

Edited October 28, 2018 by sheson

[sheson]

Since 2.44 I'm not able to create any LOD for Bruma anymore. It always throws me the same error (But I don't remember the exact words currently...Sorry) It's something like: "This file cannot be mapped as master in the load order".

It only happens when I uncomment BSHEARTLAND in the worldspace ignore list and select it in the worlds window.

I tried to generate Dyndolod for Bruma seperately, but this way it throws me another error, something like: "DynDOLOD_SSE_childworldlod_BSHeartland.txt not found". And this file obviously doesn't exist anywhere.

 

On all previous versions of Dyndolod I was using, I never had a problem with it Bruma.

 

 

Ooops, seems I posted in the wrong section. I'm using SSE.

 

As asked ("If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum"), post the entire log. Then we wouldn't have to wonder about the exact error messages.

 

The message DynDOLOD_SSE_childworldlod_BSHeartland.txt is expected, because the files does not exist.

Edited October 28, 2018 by sheson

[DX3M]

Is there is a way without generating NEW output (hence using my old dyndolod.output and texgen.output) and creating new esm / esp files for 2.44?

 

Cheers!

Edited October 28, 2018 by DX3M

[sheson]

Is there is a way without generating NEW output (hence using my old dyndolod.output and texgen.output) and creating new esm / esp files for 2.44?

 

Cheers!

As the TexGen message to save users from themselves and the TexGen manual explain, old TexGen output should be removed before generating new output.

 

DynDOLOD 2.44 can only update plugins that were made with DynDOLOD 2.44. The stop message appears when incompatible DynDOLOD plugins are loaded.

 

Use DynDOLOD 2.43 to update existing plugins version 2.30 or generate from scratch with DynDOLOD 2.44.

Edited October 28, 2018 by sheson

[Godis]

Ok, here's bugreport.txt: https://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/filehttps://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/filehttps://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/filehttps://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/filehttps://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/file

 

 

and here the full log: https://www.mediafire.com/file/8cvx85u3bp3g9rz/DynDOLOD_SSE_log.txt/file

[sheson]

Ok, here's bugreport.txt: https://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/filehttps://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/filehttps://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/filehttps://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/filehttps://www.mediafire.com/file/3hvb3dvbqcjcoj4/bugreport.txt/file

 

 

and here the full log: https://www.mediafire.com/file/8cvx85u3bp3g9rz/DynDOLOD_SSE_log.txt/file

 

Thanks that helped. The bug causing the problem will be fixed in the next version.

 

Edit: Fixed in DynDOLOD 2.45

Edited November 5, 2018 by sheson

[Godis]

Thx a lot! :)

[Aymerick]

Nevermind I've figured it out :)

[DarthVitrial]

2.45 crashed when running with the same config that worked in 2.44...Bugreport: https://pastebin.com/aewHLSrC

Crashed when loading mesh rules, possibly because I was using those custom waterfall rules from the script you provided?

 

EDIT: Wait, I might have fixed it by renaming DynDOLOD_SSE_skyrimesm_blackreach.patch to DynDOLOD_SSE_skyrimesm_Blackreach.patch.

Edited November 5, 2018 by DarthVitrial

[sheson]

2.45 crashed when running with the same config that worked in 2.44...Bugreport: https://pastebin.com/aewHLSrC

Crashed when loading mesh rules, possibly because I was using those custom waterfall rules from the script you provided?

 

EDIT: Wait, I might have fixed it by renaming DynDOLOD_SSE_skyrimesm_blackreach.patch to DynDOLOD_SSE_skyrimesm_Blackreach.patch.

The upper/lower case of file names does matter. In case the patch continues to cause trouble, just upload it so i can test myself.

[DarthVitrial]

Generated Dyndolod successfully, but now LOOT says there’s a “cyclic integration between dyndolod.esm and bring out your dead.espâ€. Back cycle: “bring out your dead.esp, realisticwatertwo.esp, dyndolod.esmâ€.

Any idea what that means?