DynDOLOD 3.00 Alpha 190

[sheson]

  On 8/31/2021 at 7:56 PM, PRieST said:

Ok, so how do I solve the 'initally disabled' warnings, will I have to reenable them, even if they are disabled on purpose?

Expand  

If this reference is Initially disabled with an enable state opposite to player and a z position of -30000 it should be "fixed" by DynDOLOD automatically. Check if it overwrites the record.

[PRieST]

  On 9/1/2021 at 5:15 AM, sheson said:

If this reference is Initially disabled with an enable state opposite to player and a z position of -30000 it should be "fixed" by DynDOLOD automatically. Check if it overwrites the record.

Expand  

OK, I'll check it after generation. I hope some Samples are enough, because I have a lot of These warnings/records inside the plugins.

But most If the records should have the enable state an z-position you mentioned...at least as far as I can tell.

[sheson]

  On 8/31/2021 at 6:32 PM, ButchDiavolo said:

Hey Sheson,

Just found out about Version 3! So of course I had to download it and try it out.

TexGen went without a hitch (one error)

However when trying to do the lod gen I got this message:  Load order FileID [32] can not be mapped to file FileID for file "DynDOLOD.esp". Can you tell me what this means exactly? Does it mean that load order esp (Blackthorn manor in this case) is causing the problem. If so, is there anything I can do about it myself?

Just in case, I have also uploaded the needed logs to Mega.

Thanks for any help/ info you can provided. And for your amazing work!

Expand  

Download this test version see if it runs through without error. In case there still is an error upload the new bug report and log files.

[ButchDiavolo]

  On 9/1/2021 at 8:02 AM, sheson said:

Download this test version see if it runs through without error. In case there still is an error upload the new bug report and log files.

Expand  

Worked like a charm! It finished the dyn lod generation without any errors. Thanks so much for the help.

One question though: I saw many warnings about large references ("<Warning: Overwritten large reference" and "<Warning: Initially disabled large reference in"). Should I be worried about those or did I do something wrong that would create them?

Edited September 1, 2021 by ButchDiavolo

[sheson]

  On 9/1/2021 at 1:15 PM, ButchDiavolo said:

Worked like a charm! It finished the dyn lod generation without any errors. Thanks so much for the help.

One question though: I saw many warnings about large references. Should I be worried about those or did I do something wrong to create them?

Expand  

Read:

..\DynDOLOD\docs\help\LogMessages.html what certain log messages mean.
..\DynDOLOD\docs\DynDOLOD_Manual_SSE.html "Skyrim Special Edition Visual Bugs and Oddities"
..\DynDOLOD\docs\SkyrimSELargeRefGrid\SkyrimSE-LargeRefGrid.html

These log message tell you which plugin(s) are visually incompatible with the Skyrim Special Edition large reference feature.

I would argue it is typically up to a mod author to make mods that do not cause well known/documented visual problems.

[PRieST]

Another question concerning the overwritten large references:

Is it only fixable by setting the esm flag and use the Script, or could I do this manually?

I am aksing, because I have some plugins which are causing the warnings, but I can't change the loadorder and so can't set the flag.

[ButchDiavolo]

  On 9/1/2021 at 1:22 PM, sheson said:

Read:

..\DynDOLOD\docs\help\LogMessages.html what certain log messages mean.
..\DynDOLOD\docs\DynDOLOD_Manual_SSE.html "Skyrim Special Edition Visual Bugs and Oddities"
..\DynDOLOD\docs\SkyrimSELargeRefGrid\SkyrimSE-LargeRefGrid.html

These log message tell you which plugin(s) are visually incompatible with the Skyrim Special Edition large reference feature.

I would argue it is typically up to a mod author to make mods that do not cause well known/documented visual problems.

Expand  

Hmm, ok. So, basically most of my mods are being listed in the warnings. And after reading the docs, I am not really sure what to do about the warnings. A combination of English not being my native tongue AND well... technicalities I have never dealt with before. (Well, not to exclude being blond). So for a "noob" in this case, what would you suggest I do to get rid of the warnings?

EDIT: Um... did I mention I am blond? I just saw the conversations you have been having with Priest and it seems I have the same issues as him/her. So I will try the script thingie.

Edited September 1, 2021 by ButchDiavolo

[sheson]

  On 9/1/2021 at 1:51 PM, PRieST said:

Another question concerning the overwritten large references:

Is it only fixable by setting the esm flag and use the Script, or could I do this manually?

I am aksing, because I have some plugins which are causing the warnings, but I can't change the loadorder and so can't set the flag.

Expand  

Only ESM flagged plugins can overwrite large references without triggering the bugs.

A solution would be to move all such overwrites out of the ESP into a ESM (can also be flagged ESL).

  On 9/1/2021 at 1:53 PM, ButchDiavolo said:

Hmm, ok. So, basically most of my mods are being listed in the warnings. And after reading the docs, I am not really sure what to do about the warnings. A combination of English not being my native tongue AND well... technicalities I have never dealt with before. (Well, not to exclude being blond). So for a "noob" in this case, what would you suggest I do to get rid of the warnings?

Expand  

As a user who is not fixing the plugins/mods you will just have to ignore the warnings. Large reference are a visual problem. The bugs are only visible when the large reference system is enabled via the launcher/INI setting.

[ButchDiavolo]

  On 9/1/2021 at 1:55 PM, sheson said:

As a user who is not fixing the plugins/mods you will just have to ignore the warnings. Large reference are a visual problem. The bugs are only visible when the large reference system is enabled via the launcher/INI setting.

Expand  

Well... Even I can do that!  Thanks so much for your help. And keep up the good work

[PRieST]

  On 9/1/2021 at 1:55 PM, sheson said:

Only ESM flagged plugins can overwrite large references without triggering the bugs.

A solution would be to move all such overwrites out of the ESP into a ESM (can also be flagged ESL).

Expand  

Thanks for the Info, seems I'll have a lot to do now.

Is there any Script, with which I could Filter such records via xEdit?

[sheson]

  On 9/1/2021 at 2:15 PM, PRieST said:

Thanks for the Info, seems I'll have a lot to do now.

Is there any Script, with which I could Filter such records via xEdit?

Expand  

I never made a pas script to do the same type of overwritten reference detection that prints the warning in the DynDOLOD log.

Not sure how proficient you are in writing pas scripts, but the logic to find them is something like this:

REFR defined in ESM, is referenced by its WRLD record, has a winningoverride in an ESP.

You might need use an xLODGen terran LOD beta version in xEdit mode that shows the RNAM data on skyrim.esm.

Might be quicker to just compile a list from the DynDOLOD log warnings.

[PRieST]

  On 9/1/2021 at 2:28 PM, sheson said:

I never made a pas script to do the same type of overwritten reference detection that prints the warning in the DynDOLOD log.

Not sure how proficient you are in writing pas scripts, but the logic to find them is something like this:

REFR defined in ESM, is referenced by its WRLD record, has a winningoverride in an ESP.

You might need use an xLODGen terran LOD beta version in xEdit mode that shows the RNAM data on skyrim.esm.

Might be quicker to just compile a list from the DynDOLOD log warnings.

Expand  

Oh, never had written a pas script before, maybe I have to learn it now^^

[nolbear]

I'm using DynDOLOD to generate an underside mesh, but no matter what I do I can't seem to stop it from poking through the regular terrain. I've tried changing the quality and position settings several times, but it doesn't seem to make any difference. I'm attaching a screenshot to show the issue. It's especially evident on the throat of the world. You can see the lighter colored underside mesh sticking through the mountain, causing a very unnatural "banded" look. Can someone please tell me if this is the expected result, or if I'm just doing something wrong? The settings used for the screenshot are -1000 position and 5 quality, but like I said, I've seen the very same issue with the default settings and others that I've tried. Any help would be much appreciated.

Edit: I realize the picture isn't very clear. I can take another one in clearer weather if the issue isn't visible enough.

Edited September 1, 2021 by nolbear

[sheson]

  On 9/1/2021 at 10:19 PM, nolbear said:

I'm using DynDOLOD to generate an underside mesh, but no matter what I do I can't seem to stop it from poking through the regular terrain. I've tried changing the quality and position settings several times, but it doesn't seem to make any difference. I'm attaching a screenshot to show the issue. It's especially evident on the throat of the world. You can see the lighter colored underside mesh sticking through the mountain, causing a very unnatural "banded" look. Can someone please tell me if this is the expected result, or if I'm just doing something wrong? The settings used for the screenshot are -1000 position and 5 quality, but like I said, I've seen the very same issue with the default settings and others that I've tried. Any help would be much appreciated.

Edit: I realize the picture isn't very clear. I can take another one in clearer weather if the issue isn't visible enough.

Expand  

Increase the Static Object LOD distances in the DynDOLOD SkuUI MCM Settings, with BethINI, the launcher or directly in SkyrimPrefs.INI

Also generate terrain LOD with xLODGen in case it isn't.

[nolbear]

  On 9/2/2021 at 6:31 AM, sheson said:

Increase the Static Object LOD distances in the DynDOLOD SkuUI MCM Settings, with BethINI, the launcher or directly in SkyrimPrefs.INI

Also generate terrain LOD with xLODGen in case it isn't.

Expand  

Thank you for the quick response! Messing with the MCM settings did help a lot, and also made my LOD a lot prettier with seemingly minimal performance loss. Don't know why I never tried adjusting those before... Thanks so much!