DynDOLOD 3.00 Alpha 180

[sheson]

25 minutes ago, Gerkesiz said:

I need best quality so i changed quality to 0 for best quality but lowered LOD to 4. What im asking is for high quality visual should i use quality 0 and LOD32 on lodgen? 

https://dyndolod.info/How-LOD-Works
Terrain LOD is separated into 4 LOD levels [..] The LOD levels are named 4, 8, 16, 32 based on the number of cells for the edge length. For example LOD Level 4 covers 4x4 cells, LOD Level 8 covers 8x8 cells etc.

Reading Terrain-LOD-Readme.txt and https://dyndolod.info/Help/xLODGen and if paying attention to the xLODGen interface it is obvious that the Settings dropdown is not a selection which terrain LOD level is being generated. That is what the Specific Chunk  checkbox and dropdown is for.

The SSELODGen_log.txt you uploaded shows that terrain LOD meshes and textures for all LOD levels have been generated.

[tamrieltwo]

10 hours ago, sheson said:

I am assuming you are asking why references using the base record TREE:37000D62 do not have 3D tree LOD.
The tree report snippet you posted already explains why:
3D LOD model not found cg4_tree_elm01_8B64A258

https://dyndolod.info/Help/Ultra-Tree-LOD#Generating
https://dyndolod.info/Help/3D-Tree-LOD-Model
In order to match 3D tree LOD models to full models, the filenames of the 3D tree LOD models contain the CRC32 checksum of the full model. With both the filename and the CRC32 checksum, shared archives of 3D static LOD models for trees can be created without having to worry about load order or overwrite order as each version will have a unique LOD filename. For example, the filename for a full model tree with the filename treepineforest01.nif and a CRC32 checksum of 8E204123 becomes treepineforest01_8E204123passthru_lod.nif.
Check ..\DynDOLOD\Logs\DynDOLOD_[GAME MODE]_Tree_Report.txt for the 3D tree LOD model filenames that are being looked for. There will be an entry like 3D LOD model not found treeaspen01_XXXXXXXX. That means the filename is should be treeaspen01_XXXXXXXpassthru_lod.nif.

A 3D tree LOD file with the filename cg4_tree_elm01_8B64A258passthru_lod.nif was not found.

Thank you. The mod author had out of date CRC32 values in the passthru_lod.nif filename. I have alerted them.

Edited October 15, 2023 by tamrieltwo

[tamrieltwo]

What can cause tree trunks to be split like this? I get it with Billboard3, but if I use Billboard4 it is a lot less noticeable. Also, I have ticked "Ultra".

Edited October 15, 2023 by tamrieltwo

[sheson]

4 hours ago, tamrieltwo said:

What can cause tree trunks to be split like this? I get it with Billboard3, but if I use Billboard4 it is a lot less noticeable. Also, I have ticked "Ultra".

Read the first post https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs and/or which TexGen and DynDOLOD log and debug log to upload when making posts.
Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make useful screenshots with more informative console.

[tamrieltwo]

4 hours ago, sheson said:

Read the first post https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs and/or which TexGen and DynDOLOD log and debug log to upload when making posts.
Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make useful screenshots with more informative console.

Here's one example of a 3D Hybrid LOD that I made. There's a gap in the tree trunk. This gap looks the same in Nifskope as it does ingame. 

Trunk LOD textures from texgen:

picea02_trunk_textures.rar

3D Hybrid LOD mesh output (above screenshot):

picea02_0889f3e2passthru_lod.nif

Crown 3d model:

picea02_0889f3e2passthru_lod.nif

Trunk 3d model:

picea02_0889f3e2_trunk.nif

Full original model:

picea02.nif

I used this guide to make the 3D Hybrid LODs: https://dyndolod.info/Help/3D-Tree-LOD-Model

My hybrid.txt:

Quote

GameMode=HYBRID
FlatNif=.\template4.nif
PathData=..\..\..\..\TexGen_Output\Textures\DynDOLOD\LOD\Trees\nature of the wild lands 2.0 - deleted 3d lods\
PathInput=.\nature of the wild lands 2.0 - deleted 3d lods\
PathOutput=.\output\

Is this a problem with LODGenx64.exe or template4.nif, perhaps? Or maybe a problem with the trunk textures?

[sheson]

1 hour ago, tamrieltwo said:

Here's one example of a 3D Hybrid LOD that I made. There's a gap in the tree trunk. This gap looks the same in Nifskope as it does ingame. 

Trunk LOD textures from texgen:

picea02_trunk_textures.rar 470.6 kB · 0 downloads

3D Hybrid LOD mesh output (above screenshot):

picea02_0889f3e2passthru_lod.nif 248.95 kB · 0 downloads

Crown 3d model:

picea02_0889f3e2passthru_lod.nif 246.42 kB · 0 downloads

Trunk 3d model:

picea02_0889f3e2_trunk.nif 223.08 kB · 0 downloads

Full original model:

picea02.nif 479 kB · 0 downloads

I used this guide to make the 3D Hybrid LODs: https://dyndolod.info/Help/3D-Tree-LOD-Model

My hybrid.txt:

Is this a problem with LODGenx64.exe or template4.nif, perhaps? Or maybe a problem with the trunk textures?

This happens because the 3D trunk of the full model is not centered around x, y = 0, 0.

Simply move the planes manually by adjusting the Translation x, y values of each BSTriShape.
For example y = 20 for BSTrishape 5 and 13 and x = -5 for BSTriShape 9 and 17 in picea02_0889f3e2passthru_lod.nif

 

[tamrieltwo]

36 minutes ago, sheson said:

This happens because the 3D trunk of the full model is not centered around x, y = 0, 0.

Simply move the planes manually by adjusting the Translation x, y values of each BSTriShape.
For example y = 20 for BSTrishape 5 and 13 and x = -5 for BSTriShape 9 and 17 in picea02_0889f3e2passthru_lod.nif

 

Amazing, works perfect, thanks

[tamrieltwo]

1 hour ago, sheson said:

This happens because the 3D trunk of the full model is not centered around x, y = 0, 0.

Simply move the planes manually by adjusting the Translation x, y values of each BSTriShape.
For example y = 20 for BSTrishape 5 and 13 and x = -5 for BSTriShape 9 and 17 in picea02_0889f3e2passthru_lod.nif

 

 

I have this 3D Hybrid LOD where the size of the gap doesn't vary linearly, so it can't be corrected properly with a simple x/y/yz Translation. If I eliminate the large gap in the middle via Translation, then the top parts of the trunk will crossover. What would your advice be?

[sheson]

6 minutes ago, tamrieltwo said:

 

I have this 3D Hybrid LOD where the size of the gap doesn't vary linearly, so it can't be corrected properly with a simple x/y/yz Translation. If I eliminate the large gap in the middle via Translation, then the top parts of the trunk will crossover. What would your advice be?

Find the best translation, so it looks good when hopefully most of the trunk is hidden behind the crown.
Or edit the full model to have a straight trunk.
Or keep the 3D of the trunk and optimize/decimate it and make its UV stay inside 0.0 and 1.0 (if beneficial create a TexGen rule to generate a stitched 2x2 version so UV can stay between 0.0 and 2.0)

Edited October 15, 2023 by sheson

[MisterMorden]

Sheson, just back to say 155 did fix the issue I was having with the M.O.I.S.T. trees in the swamp.  Thank you for the help with that!

[ErikSteiner]

I was able to run TexGen and DynDOLOD successfully. The following versions were used:

• Steam Proton 8.0-4
• Windows Version set to Windows 10
• installed additional software in the prefix
  • Microsoft Visual C++ Redistributable packages for Visual Studio 2015, 2017, 2019 and 2022
  • .NET SDK 7 7.0.402

I had to set the following settings to get the programs to run. TexGen in particular was very sensitive, and I had to set virtually all parameters.

TexGen_SSE.INI:

[TexGen]
LockTexconv=1
RenderSingle=1
RenderTexturesSingleThread=1
TexconvAdapterIndex=-1

DynDOLOD_SSE.ini:

[DynDOLOD]
TexconvAdapterIndex=-1

 

There is a visual error with the DynDOLOD program. If it is set to Windows 10, then the text under "Mesh and Reference rules" is not displayed. If you click on it, the blue selection of the line is displayed for a short moment, but then disappears again, so that the area remains white. I suspect that the font color here is just white? Maybe you have an idea about this. Because the rest of the text is displayed. The problem can be solved if I set DynDOLOD to Windows 7.

There is another error with DynDOLOD. If the program runs as Windows XP, then the closing dialog does not appear, but the program closes after the run. Nevertheless, the following can be read in the logs:

[38:29] LODGenx64.exe generated object LOD for Tamriel successfully
[38:29] Created a summary of log messages C:\Modding\DynDOLOD_3.00-Alpha-155\Summary\DynDOLOD_Index.html.
[38:29] Save DynDOLOD plugins, save plugins and zip output, exit DynDOLOD without saving, check the log? If 'Check log' is selected, the DynDOLOD plugins will be saved and the log can be checked.
[38:29] Saving C:\Modding\DynDOLOD_3.00-Alpha-155\DynDOLOD_Output\DynDOLOD.esm
[38:31] Saving C:\Modding\DynDOLOD_3.00-Alpha-155\DynDOLOD_Output\DynDOLOD.esp
[38:35] Saving C:\Modding\DynDOLOD_3.00-Alpha-155\DynDOLOD_Output\Occlusion.esp

The error seems understandable to me. If there is an error when starting DynDOLOD, the message window always appears with the link to the website. This also does not appear under Windows XP. Instead, the log says that at least Windows Vista is needed to display the dialog. The reason why I set DynDOLOD temporarily on Windows XP was that, as described above, the text is not displayed correctly under Windows 10.

 

Don't get me wrong, I just want to share with you and the community my findings about the tools on Linux.

Edited October 17, 2023 by ErikSteiner
added additional information

[sheson]

45 minutes ago, ErikSteiner said:

I was able to run TexGen and DynDOLOD successfully. The following versions were used:

• Steam Proton 8.0-4
• Windows Version set to Windows 10
• installed additional software in the prefix
  • Microsoft Visual C++ Redistributable packages for Visual Studio 2015, 2017, 2019 and 2022
  • .NET SDK 7 7.0.402

I had to set the following settings to get the programs to run. TexGen in particular was very sensitive, and I had to set virtually all parameters.

TexGen_SSE.INI:

[TexGen]
LockTexconv=1
RenderSingle=1
RenderTexturesSingleThread=1
TexconvAdapterIndex=-1

DynDOLOD_SSE.ini:

[DynDOLOD]
TexconvAdapterIndex=-1

 

There is a visual error with the DynDOLOD program. If it is set to Windows 10, then the text under "Mesh and Reference rules" is not displayed. If you click on it, the blue selection of the line is displayed for a short moment, but then disappears again, so that the area remains white. I suspect that the font color here is just white? Maybe you have an idea about this. Because the rest of the text is displayed. The problem can be solved if I set DynDOLOD to Windows 7.

There is another error with DynDOLOD. If the program runs as Windows XP, then the closing dialog does not appear, but the program closes after the run. Nevertheless, the following can be read in the logs:

[38:29] LODGenx64.exe generated object LOD for Tamriel successfully
[38:29] Created a summary of log messages C:\Modding\DynDOLOD_3.00-Alpha-155\Summary\DynDOLOD_Index.html.
[38:29] Save DynDOLOD plugins, save plugins and zip output, exit DynDOLOD without saving, check the log? If 'Check log' is selected, the DynDOLOD plugins will be saved and the log can be checked.
[38:29] Saving C:\Modding\DynDOLOD_3.00-Alpha-155\DynDOLOD_Output\DynDOLOD.esm
[38:31] Saving C:\Modding\DynDOLOD_3.00-Alpha-155\DynDOLOD_Output\DynDOLOD.esp
[38:35] Saving C:\Modding\DynDOLOD_3.00-Alpha-155\DynDOLOD_Output\Occlusion.esp

The error seems understandable to me. If there is an error when starting DynDOLOD, the message window always appears with the link to the website. This also does not appear under Windows XP. Instead, the log says that at least Windows Vista is needed to display the dialog. The reason why I set DynDOLOD temporarily on Windows XP was that, as described above, the text is not displayed correctly under Windows 10.

 

Don't get me wrong, I just want to share with you and the community my findings about the tools on Linux.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug to upload when making posts. Typically provide the debug log for every time different settings are used.
Provide the  output from official Texconv without any parameters that shows the detected adapters.

"TexGen in particular was very sensitive" is not a useful error report. Half the settings apply to Texconv and not TexGen.

The tools use TaskDialog, which was introduced with Windows Vista. Windows 7 would be the minimum requirement for everything, including the .Net Framework 4.8.
The mesh rules uses a ListView, same as xEdit for the referenced by tab. Does that work?

I do not need to change anything in my old Ubuntu test setup from 2021 with Proton 5 and wine 7 to see the ListView

[ErikSteiner]

47 minutes ago, sheson said:

"TexGen in particular was very sensitive" is not a useful error report. Half the settings apply to Texconv and not TexGen.

I do not need to change anything in my old Ubuntu test setup from 2021 with Proton 5 and wine 7 to see the ListView

I have just created a prefix with wine-8.0.2. And completely outside of Steam and Proton. Simply wine from the system installation.

In it, I installed MO2 which brings "Microsoft Visual C++ Redistributable packages for Visual Studio ...". Then I installed the "DynDOLOD Resources SE" and generated the billboards with TexGen. After this I started DynDOLOD and indeed the merge area was displayed correctly. However, it turned out that wine creates the prefix by default with Windows 7. If I switch the DynDOLOD application to Windows 10, I can replicate the visual error.

I therefore assume that in your winecfg either the entire prefix or the application is set to Windows 7. So we would both be right, wouldn't we?

 

Quote

Provide the output from official Texconv without any parameters that shows the detected adapters.

I attached them from the example below.

 

Quote

The tools use TaskDialog, which was introduced with Windows Vista. Windows 7 would be the minimum requirement for everything, including the .Net Framework 4.8.

That describes my observations. So that, the generation fails if you try it on Windows XP.

 

Quote

The mesh rules uses a ListView, same as xEdit for the referenced by tab. Does that work?

Unfortunately, I am unable to find that tab. Is there anything special required, in order to get it?

 

Quote

Half the settings apply to Texconv and not TexGen.

I thought that already, that they are forwarded. You can also see this during execution in htop/btop. I just didn't want to give the impression that I would use other versions or procedures.

DynDOLOD_SSE_Debug_log.txt DynDOLOD_SSE_log.txt

[sheson]

2 hours ago, ErikSteiner said:

I have just created a prefix with wine-8.0.2. And completely outside of Steam and Proton. Simply wine from the system installation.

In it, I installed MO2 which brings "Microsoft Visual C++ Redistributable packages for Visual Studio ...". Then I installed the "DynDOLOD Resources SE" and generated the billboards with TexGen. After this I started DynDOLOD and indeed the merge area was displayed correctly. However, it turned out that wine creates the prefix by default with Windows 7. If I switch the DynDOLOD application to Windows 10, I can replicate the visual error.

I therefore assume that in your winecfg either the entire prefix or the application is set to Windows 7. So we would both be right, wouldn't we?

 

I attached them from the example below.

 

That describes my observations. So that, the generation fails if you try it on Windows XP.

 

Unfortunately, I am unable to find that tab. Is there anything special required, in order to get it?

 

I thought that already, that they are forwarded. You can also see this during execution in htop/btop. I just didn't want to give the impression that I would use other versions or procedures.

DynDOLOD_SSE_Debug_log.txt 84.57 kB · 0 downloads DynDOLOD_SSE_log.txt 641.43 kB · 0 downloads

The DynDOLOD debug log only contains the last session, which just shows you opening and close it. The DynDOLOD log does not seem to show any entire generation session either. Upload the TexGen debug log that hopefully contains the entire generation of the textures.

I do not see the original Texconv output that shows the discovered adapters?

the Referenced by tab is shown at the bottom on records that are used by other records and requires the tool to build the reference cache.
For example 00013002 has 37 referenced by entries for the vanilla game.

[ErikSteiner]

I see my mistake. This happened when I tried to test different Windows versions and the effect onto the visibility of ListView.

• TexGen_SSE_Debug_log.txt
• TexGen_SSE_log.txt

Thank you very much for the explanation of the .NET Framework and the technique behind your tools. This will help me in using it under Linux. I already noticed, that TexGen will not work very well under "Windows XP", so I will try to install dotnet48, and maybe I can omit those entries under [TexGen]/[DynDOLOD].