DynDOLOD 3.00 Alpha 196

[sheson]

33 minutes ago, Khermiit said:

Dammit, I tried not to be one of those guys that didn't rtfm too. Lol

Thanks for your patience. I'll try the suggestions today. I had thought the x64 versions were for SE only.

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

[Khermiit]

3 hours ago, sheson said:

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

Switching to the x64 tools solved all issues. Didn't even have to alter the TexGen ini. I was even able to run it on much higher settings than previously.
You are a gentleman and a scholar. I would like to send a tip. Which do you prefer... the Kofi link,  or the paypal link back to Step Modifications?

[Soulmancer]

Hello,

I appear to be encountering issues with the Sovngarde Braziers due to Dyndolod 3.0 106 and ELFX?

 

https://cdn.discordapp.com/attachments/710269640005386240/1053493918290956299/20221216175217_1.jpg

 

The settings I am using are these; oddly enough I don't even have FXGlow or Candles enabled for lod... maybe fake lights in child worlds?

http://icecream.me/uploads/d340e67e4b8c781dfc1642c8aab5029d.png

 

 

 

Edited December 17, 2022 by Soulmancer

[sheson]

1 hour ago, Khermiit said:

Switching to the x64 tools solved all issues. Didn't even have to alter the TexGen ini. I was even able to run it on much higher settings than previously.
You are a gentleman and a scholar. I would like to send a tip. Which do you prefer... the Kofi link,  or the paypal link back to Step Modifications?

Either is fine and appreciated. You either support me directly or this support forum.

[sheson]

1 hour ago, Soulmancer said:

Hello,

I appear to be encountering issues with the Sovngarde Braziers due to Dyndolod 3.0 106 and ELFX?

 

https://cdn.discordapp.com/attachments/710269640005386240/1053493918290956299/20221216175217_1.jpg

 

The settings I am using are these; oddly enough I don't even have FXGlow or Candles enabled for lod... maybe fake lights in child worlds?

http://icecream.me/uploads/d340e67e4b8c781dfc1642c8aab5029d.png

Read the first post which log and debug log to upload when making posts.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots.
A screenshot alone does not substitute describing the issue with text. "This" is not a problem description.

fxglowdefault_dyndolod_lod.nif is used for fake lights https://dyndolod.info/Help/Glow-LOD#Fake-Lights that are added for references using LIGH base records and has nothing to do with mesh rules for candles or fxglow[fill|flat]*.nif meshes.

The reference could have only been added if Fake lights selected world was checked or you have a mod that changes Sovnguard into a child worldspace or moved the reference into a (new) childworld space of Sovnguard while Fake lights child world was checked. 

[blueetenicolet]

Hello, I'm using Large Reference Bugs Workarounds( DynDOLOD version Alpha-106), so I follow the guide to use DynDOLOD PapyrusUtil SE - Scripts 3 (3.0 - Alpha1)

But I got a notification "DynDOLOD_None.json file not found" every time I first enter a new exterior world after generate DynDOLOD.

After compare the SHESON_DynDOLOD_Master.psc from 3.0 - Alpha1 and  3.0 - Alpha29 i think i found something wrong, so i add

 

MyWorld = StringUtil.SubString(self.GetWorldspace() As String, 13, StringUtil.Find(self.GetWorldspace() As String, "(") - 14)

before MyImportFileName =... and compile it.

Then seems the issue fixed. The notification became "DynDOLOD successfully initialized"

May be the script source that Large Reference Bugs Workarounds required needs an update?

Edited December 17, 2022 by blueetenicolet

[sheson]

58 minutes ago, blueetenicolet said:

Hello, I'm using Large Reference Bugs Workarounds( DynDOLOD version Alpha-106), so I follow the guide to use DynDOLOD PapyrusUtil SE - Scripts 3 (3.0 - Alpha1)

But I got a notification "DynDOLOD_None.json file not found" every time I first enter a new exterior world after generate DynDOLOD.

After compare the SHESON_DynDOLOD_Master.psc from 3.0 - Alpha1 and  3.0 - Alpha29 i think i found something wrong, so i add

 

MyWorld = StringUtil.SubString(self.GetWorldspace() As String, 13, StringUtil.Find(self.GetWorldspace() As String, "(") - 14)

before MyImportFileName =... and compile it.

Then seems the issue fixed. The notification became "DynDOLOD successfully initialized"

May be the script source that Large Reference Bugs Workarounds required needs an update?

Read the first post which log ande debug log to upload when making reports.
Also upload the papyrus log.

Do not make assumptions or try to fix things. self.worldpace is incorrect.
See https://dyndolod.info/FAQ "DynDOLOD could/can not read/find *"

Make sure to use a new or a clean save. https://dyndolod.info/Help/Clean-Save

Download scripts again from alternative mega link.
Make sure nothing overwrites the Scripts 3 files for either PapyrusUtill or DynDOLOD.DLL depending on what you are currently testing.

Test with the alternative DynDOLOD DLL.

[Khermiit]

1 hour ago, sheson said:

Either is fine and appreciated. You either support me directly or this support forum.

Did the Ko-fi one. Thanks a bunch.

[primem0ver]

Ok.  This time I have pictures and logs.  I also have to report that this problem has gotten worse since I started playing through the various versions of DyndoLOD.  I have been "finishing"  a load order in my spare time (not a lot since September) since June.  In June through August, when running Dyndolod, I have gotten the occasional plus shaped object in certain areas of Tamriel.  Just a few (I only remember seeing 3 near Winterhold).  Last time I reported 4-5 between Riverwood and Whiterun which was after a rebuild in November.  As you can see from the pictures, that has changed with later versions of DyndoLOD (up from 95 to 106).  The only thing that has changed since my previous post (in November which was apparently deleted) was the DyndoLOD version and me switching from Sunhelm to Last Seed. Plus one or two other minor mods that looked interesting.  Nothing to merit the changes you see in the pictures.  Before that, back in September, I added a bunch of patch mods to fix some major issues around Morthal and Dawnstar caused by Cities of the North mods.  I may have added a few more patch mods but little else. Before that I had ZERO tall plus shaped objects between Riverwood and Whiterun.  So something has changed with DyndoLOD to cause these issues.  As mentioned earlier, in the original build (with zero in this scene) the only plusses I ever saw in the game that far back were 2-3 of them near Winterhold.  That is all.  Now as I look over the Whiterun Valley from the path from Riverwood, this is what I see (two different runs of DyndoLOD.  The first one without HQ trees, the second with.)

The log can be downloaded here.

 

 

 

Edited December 19, 2022 by primem0ver

[vektor9999]

Hey guys,

Before using the latest version of dyndolod 3 (alpha 106) i was using alpha 87. A thing i noticed is the size of bto files almost doubled for the same load order with the same settings. I know using HD grass, it will increase the size but i set ForceComplexGrass=0 and did not select hd grass. But the size is still way bigger.

Any ideas why?

Thank you in advance for your help

[sheson]

2 hours ago, vektor9999 said:

Hey guys,

Before using the latest version of dyndolod 3 (alpha 106) i was using alpha 87. A thing i noticed is the size of bto files almost doubled for the same load order with the same settings. I know using HD grass, it will increase the size but i set ForceComplexGrass=0 and did not select hd grass. But the size is still way bigger.

Any ideas why?

Thank you in advance for your help

No. Read the first post.

[Mousetick]

• Tree billboard models https://dyndolod.info/Help/Ultra-Tree-LOD

Quote

The mesh DynDOLOD_flat_3x2_lod.nif has 3 planes intersecting at 60 degree angles and allows for 3 different textures. [...] Generating HD tree LOD billboards with TexGen creates a front and side view texture.

How would one use Billboard3 DynDOLOD_flat_3x2_lod.nif which has 3 textures (_1, _2, _3) with TexGen which generates only front and side textures (_1, _2)?

• External billboards in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].ini

TreeBillboard1=Internal
TreeBillboard2=DynDOLOD_flat_2x2_lod.nif
TreeBillboard3=DynDOLOD_flat_3x2_lod.nif
TreeBillboard4=DynDOLOD_flat_4x2_lod.nif
TreeBillboard5=Internal
TreeBillboard6=LODGen_flat_lod.nif

Are DynDOLOD_flat_2x2alt_lod.nif and DynDOLOD_flat_4x2alt_lod.nif located in ..\DynDOLOD\Edit Scripts\DynDOLOD available for use by end-users? If so, how are they intended to be used, for what purpose, in which circumstances?

• Temporary references setting in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].ini

; Set to 1 to add activators as temporary references if possible.
; Will result in more plugins used as masters and larger plugin
; size because of additional CELL data that needs to be copied to the DynDOLOD plugin
Temporary=0

I'd like to use this feature: Temporary=1. More masters and larger plugin(s) notwithstanding, are there other reasons you would recommend against it? E.g. experimental, not fully tested, not up to date with default (persistent references).

Thank you.

[sheson]

30 minutes ago, Mousetick said:

• Tree billboard models https://dyndolod.info/Help/Ultra-Tree-LOD

How would one use Billboard3 DynDOLOD_flat_3x2_lod.nif which has 3 textures (_1, _2, _3) with TexGen which generates only front and side textures (_1, _2)?

• External billboards in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].ini

TreeBillboard1=Internal
TreeBillboard2=DynDOLOD_flat_2x2_lod.nif
TreeBillboard3=DynDOLOD_flat_3x2_lod.nif
TreeBillboard4=DynDOLOD_flat_4x2_lod.nif
TreeBillboard5=Internal
TreeBillboard6=LODGen_flat_lod.nif

Are DynDOLOD_flat_2x2alt_lod.nif and DynDOLOD_flat_4x2alt_lod.nif located in ..\DynDOLOD\Edit Scripts\DynDOLOD available for use by end-users? If so, how are they intended to be used, for what purpose, in which circumstances?

• Temporary references setting in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].ini

; Set to 1 to add activators as temporary references if possible.
; Will result in more plugins used as masters and larger plugin
; size because of additional CELL data that needs to be copied to the DynDOLOD plugin
Temporary=0

I'd like to use this feature: Temporary=1. More masters and larger plugin(s) notwithstanding, are there other reasons you would recommend against it? E.g. experimental, not fully tested, not up to date with default (persistent references).

Thank you.

It is supposed to use _1 texture if there is no _3 texture. Might be defunct.

The "alt" are used for grass LOD with GrassBillboardX=

Temporary=1 seemed to work for the couple users with the "overmodding symptoms" at the time before Skyrim SE was out and before we knew about the ref handle cap. Knowing what we know now temporary/persistent should make no difference for ESP, but it helped those users anyways.

[sheson]

5 hours ago, primem0ver said:

Ok.  This time I have pictures and logs.  I also have to report that this problem has gotten worse since I started playing through the various versions of DyndoLOD.  I have been "finishing"  a load order in my spare time (not a lot since September) since June.  In June through August, when running Dyndolod, I have gotten the occasional plus shaped object in certain areas of Tamriel.  Just a few (I only remember seeing 3 near Winterhold).  Last time I reported 4-5 between Riverwood and Whiterun which was after a rebuild in November.  As you can see from the pictures, that has changed with later versions of DyndoLOD (up from 95 to 106).  The only thing that has changed since my previous post (in November which was apparently deleted) was the DyndoLOD version and me switching from Sunhelm to Last Seed. Plus one or two other minor mods that looked interesting.  Nothing to merit the changes you see in the pictures.  Before that, back in September, I added a bunch of patch mods to fix some major issues around Morthal and Dawnstar caused by Cities of the North mods.  I may have added a few more patch mods but little else. Before that I had ZERO tall plus shaped objects between Riverwood and Whiterun.  So something has changed with DyndoLOD to cause these issues.  As mentioned earlier, in the original build (with zero in this scene) the only plusses I ever saw in the game that far back were 2-3 of them near Winterhold.  That is all.  Now as I look over the Whiterun Valley from the path from Riverwood, this is what I see (two different runs of DyndoLOD.  The first one without HQ trees, the second with.)

The log can be downloaded here.

Moved to the DynDOLOD 3 Alpha thread.

The screenshot seems to show billboard tree LOD in object LOD using the wrong object LOD atlas texture. Make sure that absolutely nothing whatsoever overwrites any of the DynDOLOD output files. Make sure the output folder is empty when generating LOD from scratch, so there are no old files preventing creation of newer files.

Do not use object LOD output from LODGens that did not complete successfully. Fix the file not found error reported in LODGen_SSE_MSWorld_log.txt
The mentioned BSA is probably corrupt.

https://dyndolod.info/Generation-Instructions#Prerequisites
Do not install any 3rd party tree LOD billboards. Use TexGen to generate all desired LOD billboards.

https://dyndolod.info/Help/Tree-Grass-LOD-Billboards#3rd-Party-LOD-Billboards
Do not install 3rd party LOD billboards. Use TexGen to generate them.

https://dyndolod.info/Messages/Texture-Resolution
For mipmap generation, textures should have resolutions that are divisible by 4, which is also a requirement of the newer compression formats like BC7.
In case there are 3rd party LOD billboards listed in the message (textures\terrain\LODGen\*), remove all 3rd party LOD billboards and instead use TexGen to generate all the desired LOD billboards. See TexGen Configuration for more.

https://dyndolod.info/Messages/Deleted-Reference
The mentioned plugin(s) needs to be cleaned. Pay attention to similar LOOT messages.

Reread what I wrote here https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-106/page/345/#comment-262975 
CoreLocationsStandard.esp and HybridLocationMerge.esp seem to intentionally trigger as many large reference bugs as possible. Maybe turn the large reference system off and set IgnoreLargeReferences=1.

[Mousetick]

1 hour ago, sheson said:

Temporary=1 seemed to work for the couple users with the "overmodding symptoms" at the time before Skyrim SE was out and before we knew about the ref handle cap. Knowing what we know now temporary/persistent should make no difference for ESP, but it helped those users anyways.

Oh right, I forgot the references were added to DynDOLOD.esp, so no difference and more like a placebo.