DynDOLOD 3.00 Alpha 190

[adrianb]

ok did that falskaar and sovngarde failed.  one caused an exception.  have pasted the event log text into a text file.

 

the debug log is large so have rared the logs up :- 

 

https://mega.nz/file/lxckgAbQ#T7Dv8Cvz0-eAdA4LZiUV-GJGw0b31xG__SshPCRZNIE

 

 

windows event .net error.txtFetching info... DynDOLOD_SSE_log.txtFetching info...

[sheson]

  On 4/28/2022 at 3:47 PM, adrianb said:

ok did that falskaar and sovngarde failed.  one caused an exception.  have pasted the event log text into a text file.

 

the debug log is large so have rared the logs up :- 

 

https://mega.nz/file/lxckgAbQ#T7Dv8Cvz0-eAdA4LZiUV-GJGw0b31xG__SshPCRZNIE

 

 

windows event .net error.txt 13.91 kB · 3 downloads DynDOLOD_SSE_log.txt 843.06 kB · 0 downloads

Expand  

Please test with this version https://mega.nz/file/0EgAkTIB#2CxoKpabhmzYi-WOibmVp-AH382jrdxMJLhg31TVGvY
This is a pre-Seasons version from late last year to see if we can find out if earlier versions exhibit the same issue or not.
In case it does, check for recent c:\Users\[username]\AppData\Local\CrashDumps\LODGen.exe.*.dmp and upload one.

[adrianb]

only one of the world spaces generated the rest failed.  have found some old crash dumps for lodgen 

 

 

https://mega.nz/file/ZhsFCb5R#45EoVudU3WM6S3RxRUDo8SXmoeZ76rdfFD0p1fTF6VU

 

https://mega.nz/file/Rx9mTYIT#0ARbLM_GEaJPxSS9Hc3eDHJy4CvMEIaGu0Dlqz32yVg

 

hope this helps.

 

DynDOLOD_SSE_log.txtFetching info...

[sheson]

  On 4/28/2022 at 5:34 PM, adrianb said:

only one of the world spaces generated the rest failed.  have found some old crash dumps for lodgen 

https://mega.nz/file/ZhsFCb5R#45EoVudU3WM6S3RxRUDo8SXmoeZ76rdfFD0p1fTF6VU

https://mega.nz/file/Rx9mTYIT#0ARbLM_GEaJPxSS9Hc3eDHJy4CvMEIaGu0Dlqz32yVg

 

hope this helps.

 

DynDOLOD_SSE_log.txt 844.41 kB · 0 downloads

Expand  

Old crash dumps not belonging to his version do not help unfortunately. Don't worry about it.

Let me know what happens with this version. https://mega.nz/file/NVhnjDRQ#biQ49K_HBFvl86Uyw4i58UcRPwWfdIl1m3cJoQ_7gU4

Just let me know if it works or still has errors.

[DarthVitrial]

  On 4/28/2022 at 6:38 PM, sheson said:

Old crash dumps not belonging to his version do not help unfortunately. Don't worry about it.

Let me know what happens with this version. https://mega.nz/file/NVhnjDRQ#biQ49K_HBFvl86Uyw4i58UcRPwWfdIl1m3cJoQ_7gU4

Just let me know if it works or still has errors.

Expand  

This one fails immediately for me, here's my logs.

Crash dumps: https://mega.nz/file/NhEkDRyB#7VKXA64nZuiTy4s7hMC_VsHdpYLmPNvnyk7O2kKHZ40
Dyndolod: https://mega.nz/file/8odjlLaJ#3_m4YJH_OaZxGN93CL0QzwTHWcUv-4KN2qRptzy1tmc

  On 4/27/2022 at 12:45 PM, sheson said:

Test with #1 https://mega.nz/file/JFQQga7S#XanMQOyxyxO2hxKvbGBzSzws6z5cVMSzRqAitpJCoJU
Test with #2 https://mega.nz/file/JFQQga7S#XanMQOyxyxO2hxKvbGBzSzws6z5cVMSzRqAitpJCoJU

Upload logs / dump if they exist. The logs will tell me which version is used. If there are dumps rename them to indicate the #1 or #2.

What Windows version and which highest version of Microsoft  .Net Framework is installed to Windows?

Expand  

Says the files have been removed, what should I be testing with?

I'm on Windows 11 (22H2 beta), .net framework 6.0.4.

[sheson]

  On 4/28/2022 at 7:55 PM, DarthVitrial said:

This one fails immediately for me, here's my logs.

Crash dumps: https://mega.nz/file/NhEkDRyB#7VKXA64nZuiTy4s7hMC_VsHdpYLmPNvnyk7O2kKHZ40
Dyndolod: https://mega.nz/file/8odjlLaJ#3_m4YJH_OaZxGN93CL0QzwTHWcUv-4KN2qRptzy1tmc

Says the files have been removed, what should I be testing with?

I'm on Windows 11 (22H2 beta), .net framework 6.0.4.

Expand  

No point in testing with versions that others already reported and uploaded logs for showing same issue.

Ah crap the test version 5 https://mega.nz/file/0EgAkTIB#2CxoKpabhmzYi-WOibmVp-AH382jrdxMJLhg31TVGvY
and 6 https://mega.nz/file/NVhnjDRQ#biQ49K_HBFvl86Uyw4i58UcRPwWfdIl1m3cJoQ_7gU4
from last year do not work with the newer bin file format as shows in the logs.

Delete the *.bin files in the export folder and use expert mode to Execute LODGen, see what happens. 
Do not select seasons for this test.

[DarthVitrial]

  On 4/28/2022 at 8:04 PM, sheson said:

No point in testing with versions that others already reported and uploaded logs for showing same issue.

Ah crap the test version 5 https://mega.nz/file/0EgAkTIB#2CxoKpabhmzYi-WOibmVp-AH382jrdxMJLhg31TVGvY
and 6 https://mega.nz/file/NVhnjDRQ#biQ49K_HBFvl86Uyw4i58UcRPwWfdIl1m3cJoQ_7gU4
from last year do not work with the newer bin file format as shows in the logs.

Delete the *.bin files in the export folder and use expert mode to Execute LODGen, see what happens. 
Do not select seasons for this test.

 

Expand  

It already worked without seasons for the test though, regardless of version.
Should I still do this test?

[sheson]

  On 4/28/2022 at 8:07 PM, DarthVitrial said:

It already worked without seasons for the test though, regardless of version.
Should I still do this test?

Expand  

Yes please, Zahkrii and adrianb do not use seasons, but have same issue. Just Execute LODGen several times...

[DarthVitrial]

  On 4/28/2022 at 8:47 PM, sheson said:

Yes please, Zahkrii and adrianb do not use seasons, but have same issue. Just Execute LODGen several times...

Expand  

Logs from 5 (No crash dump): https://mega.nz/file/VlEhFaaT#xRg7oZ9UW3E802PNQZ1e2bFUe5zV8FFKYcC7dvChtXg
 

[Mirari]

Running DynDOLOD with the Happy Little Trees Addon, Performance Edition. The included 3D Hybrid Tree Lods use an array of prebaked branch textures included in the addon download. DynDOLOD copies these textures into its DynDOLOD_Tamriel.dds texture atlas. 

Most of the branch textures are copied over just fine with transparent backgrounds. But as can be seen in this picture, the LOD branch textures for TreePineForestSnow04 are copied over with very strange artifacts and a colored background, resulting in some crazy looking TreePineForestSnow04's Lods in the game.

I cannot for the life of me figure out why DynDOLOD is messing up this texture specifically.

Additionally, a few of the other LOD trees appear to have invisible branches in game, which reappear when zooming in, indicating the mipmaps are not displaying properly from a distance. But the other trees are fine, and all the branch textures come from this same atlas, which should have one collective set of mipmaps being applied to every LOD object referencing this atlas. So again, cannot figure out why only a few trees would have this issue.

Is this an issue with how the original LOD branch textures are saved? I tried resaving them using BC7 Compression (Linear, DX 11+), with a Uniform Error Metric and Super Sampled Mipmaps, but to no avail. Any help appreciated.

Currently using the latest DynDOLOD 3 from Nexus.

[DarthVitrial]

  On 4/28/2022 at 8:04 PM, sheson said:

No point in testing with versions that others already reported and uploaded logs for showing same issue.

Ah crap the test version 5 https://mega.nz/file/0EgAkTIB#2CxoKpabhmzYi-WOibmVp-AH382jrdxMJLhg31TVGvY
and 6 https://mega.nz/file/NVhnjDRQ#biQ49K_HBFvl86Uyw4i58UcRPwWfdIl1m3cJoQ_7gU4
from last year do not work with the newer bin file format as shows in the logs.

Delete the *.bin files in the export folder and use expert mode to Execute LODGen, see what happens. 
Do not select seasons for this test.

Expand  

Logs from 6 are attached

 

bugreport.txtFetching info... Logs.7zFetching info...

[adrianb]

on the 1st run of v6 it errored at the skyrim.esm,  on the next run it processed the worldspaces but failed on them all except tokmountianpassworld. i deleted to export folder files but it made no difference

 

 

[00:29] Assertion failure (C:\Delphi\Projects\DynDOLOD3\Core\wbImplementation.pas, line 16708) while processing Skyrim.esm NorExtRubblePile04_LightIce [STAT:0010AAE2]

 

 

ive uploaded the log files to mega, i dont know if they will be of any use to you.

 

https://mega.nz/file/thkDkaYK#UXPQI8FOz6NA27Zt1jKdP8l8VrzVoKumKoe4KyteLaA

 

 

bugreport.txtFetching info... DynDOLOD_SSE_log.txtFetching info...

[sheson]

  On 4/28/2022 at 9:34 PM, DarthVitrial said:

Logs from 5 (No crash dump)

Expand  

  On 4/28/2022 at 9:52 PM, DarthVitrial said:

Logs from 6 are attached

Expand  

  On 4/28/2022 at 11:03 PM, adrianb said:

on the 1st run of v6 it errored at the skyrim.esm,  on the next run it processed the worldspace

Expand  

A crap deleting the bin also does't seem to work, it will then have a file not found error.
Sorry about that.

Please test with #7 https://mega.nz/file/4JRiTRKQ#oHJ13BVOyA2itWjkV5ic_HSxEdfU3EaCCRuRfH_8EPc
and #8 https://mega.nz/file/4JRiTRKQ#oHJ13BVOyA2itWjkV5ic_HSxEdfU3EaCCRuRfH_8EPc

Use test version of DynDOLOD https://mega.nz/file/sJQR3aBZ#4h06glNhiievee-nuVn_eWWTnBY-iBrTVcU-L0gBmCY which should fix the issues from the bugreports you uploaded.

[sheson]

  On 4/28/2022 at 9:44 PM, Mirari said:

Running DynDOLOD with the Happy Little Trees Addon, Performance Edition. The included 3D Hybrid Tree Lods use an array of prebaked branch textures included in the addon download. DynDOLOD copies these textures into its DynDOLOD_Tamriel.dds texture atlas. 

Most of the branch textures are copied over just fine with transparent backgrounds. But as can be seen in this picture, the LOD branch textures for TreePineForestSnow04 are copied over with very strange artifacts and a colored background, resulting in some crazy looking TreePineForestSnow04's Lods in the game.

I cannot for the life of me figure out why DynDOLOD is messing up this texture specifically.

Additionally, a few of the other LOD trees appear to have invisible branches in game, which reappear when zooming in, indicating the mipmaps are not displaying properly from a distance. But the other trees are fine, and all the branch textures come from this same atlas, which should have one collective set of mipmaps being applied to every LOD object referencing this atlas. So again, cannot figure out why only a few trees would have this issue.

Is this an issue with how the original LOD branch textures are saved? I tried resaving them using BC7 Compression (Linear, DX 11+), with a Uniform Error Metric and Super Sampled Mipmaps, but to no avail. Any help appreciated.

Currently using the latest DynDOLOD 3 from Nexus.

Expand  

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

"But as can be seen in this picture", "why DynDOLOD is messing up this texture"
It can not be seem, because you have not shown the source texture to compare it to.
You did not mention the filename of the texture or which exact LOD mesh filename might be using it.

"mipmaps are not displaying properly"
 What you probably mean is, that those models use textures with badly made mipmaps, created without sufficient alpha coverage.
Typically those textures are being used directly and not from the object LOD atlas. Usually because the UV is not between 0.0 and 1.0.
No texture filenames or which exact LOD meshes using them were mentioned.

[Mirari]

Sorry, first time on this forum, getting the hang of what info to include.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Requested Logs :

DynDOLOD_SSE_Debug_log.txt

https://ufile.io/lmx580r2

DynDOLOD_SSE_log

https://ufile.io/mr94fb12

LODGen_SSE_Tamriel_log

https://ufile.io/ti0l6cvu

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The texture with issues is 'Pineforestsnow04.dds', located in 'textures\lod\HappyLittleTrees\Pineforestsnow04.dds'.

It is used as branch textures for the 3D Hybrid tree passthru LOD 'treepineforestsnow04_232C0CDBpassthru_lod.nif', located in 'meshes\DynDOLOD\lod\trees\treepineforestsnow04_232C0CDBpassthru_lod.nif'.

The texture displays correctly when viewing the 3D Hybrid Tree LOD model in isolation:

When running DynDOLOD with ultra trees enabled, treepineforestsnow04_232C0CDBpassthru_lod.nif is placed in level 4 LOD all over Tamriel, Solstheim, and Forgotten Vale, and these placed trees draw their textures from the respective worldspace DynDOLOD texture atlases.

All branch textures from  'textures\lod\HappyLittleTrees'  are therefore being imported directly into DynDOLOD_Tamriel.dds, DynDOLOD_DLC2SolstheimWorld.dds, and DynDOLOD_DLC01FalmerValley.dds to be used by the placed 3D hybrid trees. Their trunk textures are generated in TexGen. (See image below of Tamriel object LOD Tamriel.4.0.-12.bto)

When Pineforestsnow04.dds is copied to the atlas during DynDOLOD generation, it is heavily distorted, though all other branch textures from 'textures\lod\HappyLittleTrees' are imported normally.

Here is Pineforestsnow04.dds on the right, and its representation in DynDOLOD_Tamriel.dds on the left.

All the other correctly imported branch textures from 'textures\lod\HappyLittleTrees' can be seen in the picture of DynDOLOD_Tamriel.dds I included in my previous post, next to the distorted representation of Pineforestsnow04.dds.

The in game issue can be seen in the image below. Strange looking LOD for TreePineForestSnow04 can be seen on the left, with normal looking LOD for TreePineForestSnow05 on the right.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

As for the mipmap issue,

  On 4/29/2022 at 5:57 AM, sheson said:

Typically those textures are being used directly and not from the object LOD atlas.

Expand  

All the Happy Little Trees 3D Hybrid Trees are drawing their branch textures from the DynDOLOD Texture Atlases, not the original branch textures from 'textures\lod\HappyLittleTrees'. So the issue of invisible distant tree branches is drawn from DynDOLOD_Tamriel.dds, etc. However, after some testing, this appears to be an emergent issue from my attempt to fix the Pineforestsnow04.dds within DynDOLOD_Tamriel.dds.

Using Paint.net, I copied and pasted the original Pineforestsnow04.dds over its representation in DynDOLOD_Tamriel.dds, and resaved the texture with BC7 compression. This fixed 3D Tree LOD for TreePineForestSnow04 in game; however, 3D Tree LOD for dead pine trees started showing invisible branches from a distance. They were visible before resaving DynDOLOD_Tamriel.dds

Something detrimental therefore seems to be happening to the mipmaps when resaving, but only for a few select tree branch textures within the atlas. These were my settings for resaving the texture:

Perhaps these settings are incorrect, or a program with more specific options/parameters is required.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

TLDR, any help figuring out these issues would be greatly appreciated:

1. Why DynDOLOD is distorting Pineforestsnow04.dds on import to the texture atlases

2. Why my edits to the texture atlas to fix this problem cause invisible distant branches

Much thanks

Edited April 29, 2022 by Mirari