DynDOLOD 3.00 Alpha 180

[DoubleYou]

1 hour ago, sheson said:

If the game supports sRGB there should be no reason not to support it. In fact, there is no reason for the image library to have this bug with BC1 sRGB.

Texconv converts it properly I think. Try with this test version https://mega.nz/file/JR4xGBAI#sM7AUUgx6SZpCLll7kz7ycW-QrgJUkiLa95vJd6m4U4 Make sure it has no side effects on the other texture formats.

This test version should fix that https://mega.nz/file/YYoxxYxR#mNlC7ezYqCMRxDo7YnJ55hCtGPN-Pkhu_wZoV8uCN5k

This did fix the sRGB texture. However, all normal maps and speculars appear to be brighter. Also, diffuses with alpha transparency appear to be brighter as well.

Log file is with vanilla textures (no texture mods). Included two output examples. Before folder is with TexGen from alpha 100. After is from the test version.

https://mega.nz/file/pMhSTZDJ#FgJjeSMG7IRhynthud9q2_TBlRYUz81y-R1W2Bjy6zQ

[Mephitic]

Alpha-100 - fwiw the Large Reference Bugs Workarounds work very well in my build.
Views from vistas that heretofore were a blinking mess are a stable joy to behold.
Nicely done, and thank you for your excellent work.

[sheson]

6 hours ago, DoubleYou said:

This did fix the sRGB texture. However, all normal maps and speculars appear to be brighter. Also, diffuses with alpha transparency appear to be brighter as well.

Log file is with vanilla textures (no texture mods). Included two output examples. Before folder is with TexGen from alpha 100. After is from the test version.

https://mega.nz/file/pMhSTZDJ#FgJjeSMG7IRhynthud9q2_TBlRYUz81y-R1W2Bjy6zQ

Test with this version https://mega.nz/file/hUQiADhB#0wjEwbhAfDKBXBowcZYzyJS8RCtVcMB2jciismNjpC0.

5 hours ago, Mephitic said:

Alpha-100 - fwiw the Large Reference Bugs Workarounds work very well in my build.
Views from vistas that heretofore were a blinking mess are a stable joy to behold.
Nicely done, and thank you for your excellent work.

Thanks for letting us know.

[Blackread]

16 hours ago, sheson said:

This test version should fix that https://mega.nz/file/YYoxxYxR#mNlC7ezYqCMRxDo7YnJ55hCtGPN-Pkhu_wZoV8uCN5k

Yes, it fixed it indeed, thank you.

Looks like the one run that was successful without Out of memory errors was a random occurrence, haven't been able to repeat it since. It seems that HD Grass was the last straw. I was able to generate occlusion without 3D trees, without a grass LOD, or with 3D trees and a grass LOD using regular grass, but using 3D trees and an HD grass LOD tips it over the edge. Maybe I just need to get more RAM.

I tried generating Occlusion with xLODGen afterwards, but that failed too. I couldn't figure out how to do it with DynDOLOD.

The mentioned BTO files open in Nifskope without problems, although some of them take several seconds to load. Not all though, some open near instantly. It's the ones with a lot of grass that take the longest. The sizes of the reported files range from 4.95 MB to 59.39 MB, with most of them falling in the 10-30 MB territory. There are larger bto files in there though, the largest being around 80 MB. Generating just Tamriel with 3D trees and HD grass with 20 density takes around 40 minutes.

Edited October 3, 2022 by Blackread

[PRieST]

I don't know why, but since the last run with alpha 100 all windmills are missing their fans. I know DynDOLOD isn't affecting active cells but the windmillfans are missing in LOD aswell as on the full model. There are even missing the whole buildings if I coc to 'whiteriverwatchexterior03' and they won't appear if coming closer.

Logs

There were no special errors during the lod creation. I am using the 'LargeRefWorkaround' setting.

One last thing: If I go via coc command from main menu to the location mentioned above everything look and function as it should. I recreated LOD's from scratch from an ongoing save (clean save method), which I did many times with other Alphas, too, but I never had these 'problems'. Is there something in the logs, which tells you that I messed up the generation of LODs? Or could it be a possibility to 'update' the plugins again to get it back to work properly or do I have to start over with a new save as there are no problems - it seems to be stuck on the save, but nothing obvious inside the save itself if I look at it with FallrimTools.

Edit: Mostly I call this very dumb on my side, as somehow DynDOLOD wasn't even active in the MCM. Windmillfans are back, but still if I coc from my savegame to whiteriverwatch there are still windmill building vanishing. From far and if I get closer only the rod in the middle of the building (and the windmill fan) are there.

Edit2: Another thing I observed: After I activated DynDOLOD again and the message for initilasing came and I went via coc command, DynDOLOD was deactivated again. Maybe changing to the DLL instead the papyrus version?

Edited October 3, 2022 by PRieST

[xbk123]

Hi,

Have this error when running dyndolod last version. The only mod I have installed recently is majestic mountains new version.

Running out of ideas how to fix that.

[DoubleYou]

11 minutes ago, xbk123 said:

Hi,

Have this error when running dyndolod last version. The only mod I have installed recently is majestic mountains new version.

 

  Hide contents

 

 

Running out of ideas how to fix that.

 

It literally says how to fix in the error message. 

[sheson]

1 hour ago, Blackread said:

Yes, it fixed it indeed, thank you.

Looks like the one run that was successful without Out of memory errors was a random occurrence, haven't been able to repeat it since. It seems that HD Grass was the last straw. I was able to generate occlusion without 3D trees, without a grass LOD, or with 3D trees and a grass LOD using regular grass, but using 3D trees and an HD grass LOD tips it over the edge. Maybe I just need to get more RAM.

I tried generating Occlusion with xLODGen afterwards, but that failed too. I couldn't figure out how to do it with DynDOLOD.

The mentioned BTO files open in Nifskope without problems, although some of them take several seconds to load. Not all though, some open near instantly. It's the ones with a lot of grass that take the longest. The sizes of the reported files range from 4.95 MB to 59.39 MB, with most of them falling in the 10-30 MB territory. There are larger bto files in there though, the largest being around 80 MB. Generating just Tamriel with 3D trees and HD grass with 20 density takes around 40 minutes.

If the OOM error still happens while reading BTOs, make sure it really only process one BTO at time by doublechecking the OcclusionMaxThreadsObjectLOD in the debug log.
A line like [DynDOLODGenerate] <Debug: OcclusionMaxThreadsObjectLOD: 1>

To only generate an Occlusion.esp, install the DynDOLOD output, start DynDOLOD, advanced mode, select Tamriel, uncheck everything but Occlusion data and Plugin.

[sheson]

40 minutes ago, xbk123 said:

Hi,

Have this error when running dyndolod last version. The only mod I have installed recently is majestic mountains new version.

Running out of ideas how to fix that.

Read the first post, which explains that DynDOLOD 3 Alpha is an alpha test and that things may change between versions.

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

As explained in the first post, click the link "Click on this link for additional explanations and help for this message" to open additional help.

As explained in the first post, if the option "Copy this message to clipboard" is available, copy and paste the text instead posting a screenshot.

Read the entire message. It explains the issue and solutions.

https://dyndolod.info/Generation-Instructions#Prerequisites
Typically generate terrain LOD meshes and textures with xLODGen before generating the LOD mod with DynDOLOD, as the terrain LOD meshes are used to optimize object LOD meshes.

Ask specific questions if further help or advice is required.

[sheson]

44 minutes ago, PRieST said:

I don't know why, but since the last run with alpha 100 all windmills are missing their fans. I know DynDOLOD isn't affecting active cells but the windmillfans are missing in LOD aswell as on the full model. There are even missing the whole buildings if I coc to 'whiteriverwatchexterior03' and they won't appear if coming closer.

Logs

There were no special errors during the lod creation. I am using the 'LargeRefWorkaround' setting.

One last thing: If I go via coc command from main menu to the location mentioned above everything look and function as it should. I recreated LOD's from scratch from an ongoing save (clean save method), which I did many times with other Alphas, too, but I never had these 'problems'. Is there something in the logs, which tells you that I messed up the generation of LODs? Or could it be a possibility to 'update' the plugins again to get it back to work properly or do I have to start over with a new save as there are no problems - it seems to be stuck on the save, but nothing obvious inside the save itself if I look at it with FallrimTools.

Edit: Mostly I call this very dumb on my side, as somehow DynDOLOD wasn't even active in the MCM. Windmillfans are back, but still if I coc from my savegame to whiteriverwatch there are still windmill building vanishing. From far and if I get closer only the rod in the middle of the building (and the windmill fan) are there.

https://dyndolod.info/FAQ  "Out of place or floating objects"

Which Windmill building(s) are you specifically (reference form id) talking about? The ones around Whiterun have vanilla large reference bugs and should be handled properly now.

Are the buildings missing inside or outside the uLargeRefLODGridSize or the uGridsToLoad?

Outside the uLargeRefLODGridSize they are supposed to have static object LOD.

Check which plugins overwrites the references.

Enable and check the papyrus log for related error message from the SHESON_DynDOLOD_* scripts.

[PRieST]

23 minutes ago, sheson said:

https://dyndolod.info/FAQ  "Out of place or floating objects"

Which Windmill building(s) are you specifically (reference form id) talking about? The ones around Whiterun have vanilla large reference bugs and should be handled properly now.

Are the buildings missing inside or outside the uLargeRefLODGridSize or the uGridsToLoad?

Outside the uLargeRefLODGridSize they are supposed to have static object LOD.

Check which plugins overwrites the references.

Enable and check the papyrus log for related error message from the SHESON_DynDOLOD_* scripts.

Hm, this issue isn't always replicable.
This is the record ID of the building: 0005CA6B (nothing is overwriting it). Sometimes the building is and will stay there and sometimes it is missing.
A quick test with the DynDOLOD DLL (and it's scripts - also for the workaround) seemed to not have the problem.

Nothing inside the papyrus log.

I did the 'setup' 3 times now: 1.: Everything ok, 2.: Building was there, but heavy flickering on the honeybrew meadery buildings 3.: Windmillbuilding missing.
I went to the stormcloack camp and back, but the building wasn't there all the time only the fan.

As I came closer also the windmillfan disappeared and DynDOLOD was inactive again in the MCM. After reactivating it, only the fan came back. I could provide some screenshots, but there are no further infos to get out of them.

[Blackread]

1 hour ago, sheson said:

If the OOM error still happens while reading BTOs, make sure it really only process one BTO at time by doublechecking the OcclusionMaxThreadsObjectLOD in the debug log.
A line like [DynDOLODGenerate] <Debug: OcclusionMaxThreadsObjectLOD: 1>

To only generate an Occlusion.esp, install the DynDOOLOD output, start DynDOLOD, advanced mode, select Tamriel, uncheck everything but Occlusion data and Plugin.

Debug log reported that only one thread was used. I was inspecting the latest run I did with Process Explorer to get a better grasp of what is going on, and as soon as DynDOLOD started updating the height map the number of Private Bytes spiked up sharply, staying above 20 GB for the majority of the time and peaking at 28 GB. Process Explorer also reported over a dozen active threads for DynDOLOD during that and the number of active threads correlated pretty well with the memory usage, so I was wondering if it's possible, that Windows or something else circumvents the thread limit somehow? Although I'm not sure how reliable Process Explorer actually is for these things.

Do I need to have an Occlusion.esp already in my LO when doing the occlusion? I tried first generating LODs with Occlusion unticked, and then running again with only Occlusion data and Plugin ticked, but when I hit ok to start the process DynDOLOD asked me whether I want to update my plugins, and a few seconds after hitting Yes I got an Item not found error.

Spoiler

[Window Title]
DynDOLOD

[Main Instruction]
Error: Item not found.

[Content]

Click on this link for additional explanations and help for this message

[OK] [Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

Logs

 

Edited October 3, 2022 by Blackread

[sheson]

1 hour ago, PRieST said:

Hm, this issue isn't always replicable.
This is the record ID of the building: 0005CA6B (nothing is overwriting it). Sometimes the building is and will stay there and sometimes it is missing.
A quick test with the DynDOLOD DLL (and it's scripts - also for the workaround) seemed to not have the problem.

Nothing inside the papyrus log.

I did the 'setup' 3 times now: 1.: Everything ok, 2.: Building was there, but heavy flickering on the honeybrew meadery buildings 3.: Windmillbuilding missing.
I went to the stormcloack camp and back, but the building wasn't there all the time only the fan.

As I came closer also the windmillfan disappeared and DynDOLOD was inactive again in the MCM. After reactivating it, only the fan came back. I could provide some screenshots, but there are no further infos to get out of them.

You mean there is large reference bugs in the cell that contains the Meadery?

DynDOLOD should not go inactive by itself in the exterior worldspace, that should only happen when going into an interior or disabling it via MCM until again loading an exterior cell.

Check if anything is different after generating with this test version https://mega.nz/file/YYoxxYxR#mNlC7ezYqCMRxDo7YnJ55hCtGPN-Pkhu_wZoV8uCN5k

I nothing like that happens with the workaround scripts for DynDOLOD DLL, use them for now.

[sheson]

41 minutes ago, Blackread said:

Debug log reported that only one thread was used. I was inspecting the latest run I did with Process Explorer to get a better grasp of what is going on, and as soon as DynDOLOD started updating the height map the number of Private Bytes spiked up sharply, staying above 20 GB for the majority of the time and peaking at 28 GB. Process Explorer also reported over a dozen active threads for DynDOLOD during that and the number of active threads correlated pretty well with the memory usage, so I was wondering if it's possible, that Windows or something else circumvents the thread limit somehow? Although I'm not sure how reliable Process Explorer actually is for these things.

Do I need to have an Occlusion.esp already in my LO when doing the occlusion? I tried first generating LODs with Occlusion unticked, and then running again with only Occlusion data and Plugin ticked, but when I hit ok to start the process DynDOLOD asked me whether I want to update my plugins, and a few seconds after hitting Yes I got an Item not found error.

  Reveal hidden contents

[Window Title]
DynDOLOD

[Main Instruction]
Error: Item not found.

[Content]

Click on this link for additional explanations and help for this message

[OK] [Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

Logs

 

Is this an AMD CPU? Any crapware from AMD installed that comes with drivers?

You can either create a new Occlusion.esp  or update an existing one, just as with xLODGen  https://dyndolod.info/Help/Occlusion-Data - in theory anyways, will have to fix the bug you reported.

[delweyn]

Hello,

I would like to point out that the glows from the braziers in Solstheim are bugged. They don't disappear at close range, only when I uncheck dyndolod in the mcm.

In the screen I clicked on 1 of them to have the references.

Spoiler

Form ID: DefaultTorch01NS_DynDOLOD_LOD [STAT:18021D29]

Editor ID:DefaultTorch01NS_DynDOLOD_LOD

Model: DynDOLOD\Lod\effects\fxglowdefault6_dyndolod_lod.nif

Thank you.