Not initializing, No MCM, can not find DynDOLOD.esm, DynDOLOD.esp or Occlusion.esp

[ck1007197714]

DynDOLOD NG plugin version: 3.0.13.0 | SKSE version: 2.0.20.0 | Game version: 1-5-97-0
DynDOLOD save/load handler installed.
DynDOLOD Papyrus functions installed.
Default Trampoline => 0B / 28B (00.00%)
Trampoline initialized.
Default Trampoline => 14B / 28B (50.00%)
Default Trampoline => 28B / 28B (100.00%)
DynDOLOD Patch installed.
DynDOLOD Cell Events installed.
DynDOLOD Menu Events installed.
DynDOLOD Player Events installed.
Reading file Data/SKSE/Plugins/DynDOLOD_Data/DynDOLOD_NG_Worlds.txt
can not get version from dyndolod.esm
dyndolod.esm not found
dyndolod.esp not found

I don’t know which version the DynDOLOD initialization will not be displayed at the beginning, and the mcm menu will not be displayed. However, the DynDOLOD effect is normal, and the dynamic lod in the distance is normal.

https://ufile.io/hvtychaq

[maramsp]

Just now, sheson said:

Yes, manually dragging plugins to control their correct position is "safe".

Now that youre here @sheson

With dyndolod outside of whiterun my fps is varying a lot.

I have decided not to use precached grass, cause of i have to do it 5 times cause i use seasons. I did had a lot of fps to spare, so i decided not to use it, and still am glad that i didnt used it at all, however..

Like i said, my fps outside of whiterun is varying a lot, from the mid 50's all the way up to the high 90's.

So, is there a tiny little setting in bethini that i can alter to get the low fps margin to be in the low 60s?

Ive already raised the grass density from 40 to 50. But havent tested it yet. But should that do the trick, or should i alter some other things there as well.

Btw, keep in mind that my pc is quite a beast (ryzen 5800x3d, rtx 4070 ti super, 32gb ram, game installed on a fast samsung ssd)

But hey, nevertheless still thanks for your support. I remember you gave me some support back in the days as well with my old system. Glad to see that you still do

Cheers, Mara

[sheson]

6 minutes ago, maramsp said:

Now that youre here @sheson

With dyndolod outside of whiterun my fps is varying a lot.

I have decided not to use precached grass, cause of i have to do it 5 times cause i use seasons. I did had a lot of fps to spare, so i decided not to use it, and still am glad that i didnt used it at all, however..

Like i said, my fps outside of whiterun is varying a lot, from the mid 50's all the way up to the high 90's.

So, is there a tiny little setting in bethini that i can alter to get the low fps margin to be in the low 60s?

Ive already raised the grass density from 40 to 50. But havent tested it yet. But should that do the trick, or should i alter some other things there as well.

Btw, keep in mind that my pc is quite a beast (ryzen 5800x3d, rtx 4070 ti super, 32gb ram, game installed on a fast samsung ssd)

But hey, nevertheless still thanks for your support. I remember you gave me some support back in the days as well with my old system. Glad to see that you still do

Cheers, Mara

Since no grass LOD was generated, you might be talking about the fill grass density. I can not really help with stuff unrelated to LOD like full grass etc. You will have to adjust settings to your needs, load order and hardware. I can not really help with that.

See https://dyndolod.info/FAQ#Performance and https://dyndolod.info/FAQ#Performance#Long-running-time-or-output-several-GB-in-file-size

Disabling all static LOD with tll in console is a quick method to test its current impact. Deactivating DynDOLOD dyanmic LOD from its MCM the other.
If LOD is performance intensive, a quick fix might be lowering its distances in the DynDOLOD MCM.

From the DynDOLOD log I can see, that the 3D tree LOD might use be a bit performance intensive, listing these top 10:

Meshes\dyndolod\lod\trees\srg_treepineforest05_99ef1303passthru_lod.nif used 24682 times, ~ 1393.79 MB
Meshes\dyndolod\lod\trees\srg_treepineforest02_bf980207passthru_lod.nif used 15956 times, ~ 877.28 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnowl02_f222b833passthru_lod.nif used 9910 times, ~ 545.58 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnow02_94519138passthru_lod.nif used 9894 times, ~ 544.52 MB
Meshes\dyndolod\lod\trees\srg_treepineforest04_843e19c4passthru_lod.nif used 14479 times, ~ 460.57 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnowl04_ebb31443passthru_lod.nif used 10134 times, ~ 323.10 MB
Meshes\dyndolod\lod\trees\treepineforest03_566cac0bpassthru_lod.nif used 22199 times, ~ 288.68 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnow04_becd705bpassthru_lod.nif used 9985 times, ~ 233.98 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnow05_e02ca399passthru_lod.nif used 13385 times, ~ 199.22 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnowl05_07e08f7dpassthru_lod.nif used 12452 times, ~ 185.49 MB

From the log I can see that the object atlas texture in Tamriel is large:
Creating texture atlas F:\skyrim\modding\tools\DynDOLOD\DynDOLOD_Output\textures\DynDOLOD\LOD\DynDOLOD_Tamriel.dds 16384 x 8192

If the tll testing made a noticeable difference, test if shrinking the atlas texture to 8192x4096 with an image tool makes a difference.
If it does, changing MaxTextureSize=8192 in F:\skyrim\modding\tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and generating from scratch might help as it should then make 2 smaller atlas texture instead without sacrificing the resolution of the individual LOD textures.

[maramsp]

19 minutes ago, sheson said:

Since no grass LOD was generated, you might be talking about the fill grass density. I can not really help with stuff unrelated to LOD like full grass etc. You will have to adjust settings to your needs, load order and hardware. I can not really help with that.

See https://dyndolod.info/FAQ#Performance and https://dyndolod.info/FAQ#Performance#Long-running-time-or-output-several-GB-in-file-size

Disabling all static LOD with tll in console is a quick method to test its current impact. Deactivating DynDOLOD dyanmic LOD from its MCM the other.
If LOD is performance intensive, a quick fix might be lowering its distances in the DynDOLOD MCM.

From the DynDOLOD log I can see, that the 3D tree LOD might use be a bit performance intensive, listing these top 10:

Meshes\dyndolod\lod\trees\srg_treepineforest05_99ef1303passthru_lod.nif used 24682 times, ~ 1393.79 MB
Meshes\dyndolod\lod\trees\srg_treepineforest02_bf980207passthru_lod.nif used 15956 times, ~ 877.28 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnowl02_f222b833passthru_lod.nif used 9910 times, ~ 545.58 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnow02_94519138passthru_lod.nif used 9894 times, ~ 544.52 MB
Meshes\dyndolod\lod\trees\srg_treepineforest04_843e19c4passthru_lod.nif used 14479 times, ~ 460.57 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnowl04_ebb31443passthru_lod.nif used 10134 times, ~ 323.10 MB
Meshes\dyndolod\lod\trees\treepineforest03_566cac0bpassthru_lod.nif used 22199 times, ~ 288.68 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnow04_becd705bpassthru_lod.nif used 9985 times, ~ 233.98 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnow05_e02ca399passthru_lod.nif used 13385 times, ~ 199.22 MB
Meshes\dyndolod\lod\trees\srg_treepineforestsnowl05_07e08f7dpassthru_lod.nif used 12452 times, ~ 185.49 MB

From the log I can see that the object atlas texture in Tamriel is large:
Creating texture atlas F:\skyrim\modding\tools\DynDOLOD\DynDOLOD_Output\textures\DynDOLOD\LOD\DynDOLOD_Tamriel.dds 16384 x 8192

If the tll testing made a noticeable difference, test if shrinking the atlas texture to 8192x4096 with an image tool makes a difference.
If it does, changing MaxTextureSize=8192 in F:\skyrim\modding\tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and generating from scratch might help as it should then make 2 smaller atlas texture instead without sacrificing the resolution of the individual LOD textures.

Thank you so much again!

A simple setting of the grass density from 40 to 50 did the trick, without costing too much of a quality decrease.

But i will refer to what youve typed in the future if i need it

Again, thanks for your amazing support over all the years