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

[sheson]

 

  On 7/28/2018 at 9:18 AM, David2408 said:

I meant that the DynDOLOD_log.txt is outdated (from previous LOD generation) and does not update itself when regenerating LOD.

The log is appended when DynDOLOD.exe is closed. Scroll to the bottom for the most recent generation log.

 

 

  On 7/28/2018 at 9:18 AM, David2408 said:

Trying to move the MSTT to an additional ESL sounds pretty doable though, as RWT 2 has only 2 of these records.

It does not matter in what plugin type the MSTT overwrite is. The overwrites to references need to be in a ESM or ESL.

 

Those are two different things and they both trigger large reference bugs.

 

Whenever a reference is listed in the report, it will trigger the bug in the cell.

 

Whenever a large reference uses a MSTT record without the flag it will trigger the bug in the cell.

 

RWT happens to do both for some records, both have to be fixed.

 

Other changes that can trigger the bug regardless of plugin type are for example IsInitiallyDisabled flag, Enable/Disable via XESP, changed scale or bounds on the base record that make an object smaller below a limit for large references etc.

Edited July 28, 2018 by sheson

[David2408]

  On 7/28/2018 at 10:56 AM, sheson said:

 

It does not matter in what plugin type the MSTT overwrite is. The overwrites to references need to be in a ESM or ESL.

 

Sorry, but I don't really get what that means. "It does not matter in what plugin type the MSTT overwrite is" and "the overwrites to refrences need to be in a ESM or ESL" sounds kinda contradictory to me. ^^

 

Maybe I don't get a differentiation you are trying to make, but it sounds like you just said it does not and at the same time does matter what MSTT record-containing plugins are flagged as. 

 

As far as I understood, the correct approach would be to delete the MSTT base record override from RWT and create an identical record with Unknown 2 set in a new plugin flagged as .esm/.esl. Is this correct?

Edited July 28, 2018 by David2408

[sheson]

  On 7/28/2018 at 2:23 PM, David2408 said:

Sorry, but I don't really get what that means. "It does not matter in what plugin type the MSTT overwrite is" and "the overwrites to refrences need to be in a ESM or ESL" sounds kinda contradictory to me. ^^

 

Maybe I don't get a differentiation you are trying to make, but it sounds like you just said it does not and at the same time does matter what MSTT record-containing plugins are flagged as. 

 

As far as I understood, the correct approach would be to delete the MSTT base record override from RWT and create an identical record with Unknown 2 set in a new plugin flagged as .esm/.esl. Is this correct?

MSTT (Movable Static) is a type of base record like STAT (Static).

A REFR (Reference) is a record that is placed into a CELL which "references" a base record.

 

If an ESP overwrites a REFR which happens to be large references, it will trigger the large references bugs. An ESM/ESL overwriting such a large reference will not trigger the large reference bugs. Certain settings on the REFR can trigger the large reference bugs regardless of ESM/ESL/ESP.

 

Any large reference using a MSTT base record without the flag set will trigger the large references bugs. It does not matter if the base record is defined or overwritten by an ESM/ESL/ESP.

 

Those are two different issues. The plugin type (ESM/ESL/ESP) only matter for REFRs.

Edited July 28, 2018 by sheson

[MongeHDS]

Where I find the Resources SE 2.42 beta?

[sheson]

  On 7/28/2018 at 8:02 PM, MongeHDS said:

Where I find the Resources SE 2.42 beta?

2.41 beta is the most recent version of DynDOLOD Resources SE . That is why it is linked everywhere and that is why the last time DynDOLOD Resources SE was mentioned in the change log.

[David2408]

  On 7/28/2018 at 4:04 PM, sheson said:

MSTT (Movable Static) is a type of base record like STAT (Static).

A REFR (Reference) is a record that is placed into a CELL which "references" a base record.

 

If an ESP overwrites a REFR which happens to be large references, it will trigger the large references bugs. An ESM/ESL overwriting such a large reference will not trigger the large reference bugs. Certain settings on the REFR can trigger the large reference bugs regardless of ESM/ESL/ESP.

 

Any large reference using a MSTT base record without the flag set will trigger the large references bugs. It does not matter if the base record is defined or overwritten by an ESM/ESL/ESP.

 

Those are two different issues. The plugin type (ESM/ESL/ESP) only matter for REFRs.

What the hell... This makes things much more complicated. Seems out of scope for me now, as the issue is twofold and I do not have enaugh knowledge on that whole topic. 

 

Thank you for the explanation, though.

[KountervibeJVC]

Hi, I generated "Skyrim 3D Trees and Plants BILLBOARDS 3.2.0" and I had a file in meshes / terrain / tamriel / tree / Tamriel.4.-44.28.btt (in the overwrite folder of Mod Organizer 2 )
I went into play but I do not see any changes, the LODs are still so ugly
I made a screen:
https://imgur.com/a/5PYVosD

You know why I have no good results? I followed the instructions to the letter

I thank you in advance for your help

[sheson]

  On 7/31/2018 at 4:48 PM, KountervibeJVC said:

Hi, I generated "Skyrim 3D Trees and Plants BILLBOARDS 3.2.0" and I had a file in meshes / terrain / tamriel / tree / Tamriel.4.-44.28.btt (in the overwrite folder of Mod Organizer 2 )

I went into play but I do not see any changes, the LODs are still so ugly

I made a screen:

https://imgur.com/a/5PYVosD

 

You know why I have no good results? I followed the instructions to the letter

 

I thank you in advance for your help

 

DynDOLOD generates LOD files into the selected output folder, which should not be anywhere near the games data folder or any folder under the control of MO. So if you followed instruction correctly the Tamriel.4.-44.28.btt in the MO overwrite folder has nothing to do with the LOD generation you did with DynDOLOD.

 

It seems you are using a third party tree mod and its billboard tree LOD resources to generate tree LOD. If you do not like how the billboards look in the game, find better ones or create your own. Alternatively use better tree mods that come with better billboards or use tree mods that support 3D tree LOD support.

Edited July 31, 2018 by sheson

[Pop000100]

zilav's NIFScan has a problem with a lot of resources in the latest package 2.41. According to the description of NIFScan these can cause crashes.

[zilav]

  On 8/1/2018 at 3:28 AM, Pop000100 said:

zilav's NIFScan has a problem with a lot of resources in the latest package 2.41. According to the description of NIFScan these can cause crashes.

NifScan doesn't support SSE meshes, only Skyrim LE ones. That's why it is hosted on Skyrim Nexus only.

[sheson]

  On 8/1/2018 at 3:28 AM, Pop000100 said:

zilav's NIFScan has a problem with a lot of resources in the latest package 2.41. According to the description of NIFScan these can cause crashes.

The meshes in DynDOLOD Resources are used without problems since a long time by thousands of people.

 

If a mesh causes CTD, it is a rather easy to find, since it is 100% reproducible error. Such cases in the past were usually 3rd party meshes used for dynamic LOD. There is a FAQ entry and the readme has instructions how to narrow such cases down.

Edited August 1, 2018 by sheson

[Jasagna]

Hi all,

Using SkyrimVR I am not seeing animated LODs working (waterfalls or windmills for example). My understanding is that DynDOLOD now generates these automatically (I'm using the HIGH setting). Is this incorrect?

Please note:
MO2.14 (build 7)
Pure Waters
Latest Resources
Latest PapyrusUtil pulled from Nexus

[sheson]

  On 8/1/2018 at 12:10 PM, Jasagna said:

Hi all,

 

Using SkyrimVR I am not seeing animated LODs working (waterfalls or windmills for example). My understanding is that DynDOLOD now generates these automatically (I'm using the HIGH setting). Is this incorrect?

 

Please note:

MO2.14 (build 7)

Pure Waters

Latest Resources

Latest PapyrusUtil pulled from Nexus

There is no PapyrusUtil for Skyrim VR.

 

From first post:

"This beta version of DynDOLOD standalone generates static object, tree and dynamic LOD for Skyrim SE. It generates static object and tree LOD for Skyrim VR."

"Everything from Skyrim SE applies to Skyrim VR, but no dynamic LOD, obviously."

 

From DynDOLOD_Manual_TES5VR.html:

"Because there is no PapyrusUtil for Skyrim VR at the moment, dynamic LOD is not generated and as a result there won't be a SKSE folder and no *.json files in the output path."

Edited August 1, 2018 by sheson

[Celegon]

I've encountered a repeatable CTD any time I get near Skyborn Altar. I tested out my mod load order to find the culprit and found Dyndolod was causing the CTD. I've updated Dyndolod to the latest version and ran it successfully but the problem persists. So far (*knocks on wood*) this seems to be the only area that it crashes in. I'm open to suggestions.

[sheson]

  On 8/6/2018 at 1:32 AM, Celegon said:

I've encountered a repeatable CTD any time I get near Skyborn Altar. I tested out my mod load order to find the culprit and found Dyndolod was causing the CTD. I've updated Dyndolod to the latest version and ran it successfully but the problem persists. So far (*knocks on wood*) this seems to be the only area that it crashes in. I'm open to suggestions.

FAQ: Skyrim: ILS or CTD

 

A: More LOD uses more memory and this can cause infinite loading screen (ILS) or crash to desktop (CTD) if the game is not setup correctly. Double check heap memory usage (block 1) with Memory Blocks Log from https://www.nexusmods.com/skyrim/mods/50471/ and adjust SKSE or SSME memory settings. Or use alternative OSAllocator from crash fixes with pre-loader. Remove satefy-load if it is used to verify it doesn't cause CTD. Set ExpandSystemMemoryX64=false in enblocal.ini 

 

A: If heap memory is not the cause of CTD see ..DynDOLOD\Docs\DynDOLOD-README.txt for checking if a missing or invalid nif model used for dynamic LOD is the cause.