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].

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 DynDOLOD_SSE_log.txt

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.

Thank you. I will take a look at it. I am currently using the latest version of Texconv. You may have seen that I filed a bug report for Texconv. Texconv could not handle spaces in path names. I guess that your diff does not yet contain these changes, but your latest version of DynDOLOD does? I know your statement about "don't take other Texconv versions, but the one that comes with DynDOLOD." Don't be angry with me for that. I am currently on the trail of something where TexGen64 hangs after about an hour under Linux. As soon as I know more, I will provide logs etc. Maybe now you understand a bit my questions and my actions? In this respect, I would like to make as little work for you as possible.

Sorry, but I don't have a problem. I can understand that many here report problems without providing logs, etc.. I just wanted to get into the conversation. Are the customizations to Texconv publicly viewable?

Thank you. Why did you send me the link to the forum? It this the wrong thread?

I recently tried out DynDOLOD under Linux with Proton. I would like to know, what is the source of Texconv.exe and especially the x64-Version of it? I found the official repository, but this is missing the x64-Version.