Linux/Proton: A call to an OS function failed

[itsdnoftheworld]

Hello, I have been having an annoying issue running Dyndolod 3 on my Proton setup related to texconv. While running Dyndolod after successfully generating xlodgen and texgen, I am unable to proceed with generating Dyndolod, as I eventually get a message saying "Could not execute "Z:\home\dillon\Games\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -gpu 0 -y -m 1 -aw 256 -f R8G8B8A8_UNORM -o "C:\users\steamuser\Temp\DynDOLOD_SSE" "C:\users\steamuser\Temp\DynDOLOD_SSE\379794EC272A4EF98BAF93F0B0726085.dds". Then I get a pop-up about Call to an OS Function Failed. No .esp is mentioned.

Since I am on Linux, I don't have UAC or AV on my computer, and after changing permissions of some of the folders, specifically my game folder, mods folder, and the Dyndolod folder I have been able to run it once or twice. However, after changing a texture mod, I have been completely unable to get around this Texconv issue. I believe that Texconv should be running, since I can see it in the task manager and I can see some .dds files being converted. I also was able to run texgen and xlodgen with no issue. In fact I have run Dyndolod successfully earlier today! I have tried placing Dyndolod folder in both my Z: drive (the native Linux system) and my C: drive (the emulated Windows drive), and both run into the same error. I also reinstalled and repaired dotnet and C++, and I was able to run texconv (the official one from Github) with the below output. I also was able to convert images into .dds from the command line. However I could not replicate this with the one downloaded alongside Dyndolod. Is this expected behavior?

I am currently unable to test on Windows since my install is all messed up, but I am just looking to see if there is anything I have missed in troubleshooting. Any advice would be greatly appreciated.
 

Bug Report: https://pastebin.com/B3Te9XG4

SSE Log: https://paste.ee/p/Hhg78

Texconv Test: https://paste.ee/p/6vtVc

[kontotnok]

3 hours ago, sheson said:

What proton version are you using?
Have you installed dotnet48 through winetricks or are you using mono (which version)?

I'm running everything inside heroic launcher (installed by my package manager) using GE-Proton 9.21 outside of steam with the help of UMU-Launcher and yes, I'm using dotnet48 installed through winetricks, appart from that I have vcrun2022, dotnet35, dotnetdesktop6 and 7 and a bunch of packages all called remove_mono internal. I also installed the rest of the vc++ redistributables through the installation .exes provided by microsoft

[sheson]

1 hour ago, kontotnok said:

I'm running everything inside heroic launcher (installed by my package manager) using GE-Proton 9.21 outside of steam with the help of UMU-Launcher and yes, I'm using dotnet48 installed through winetricks, appart from that I have vcrun2022, dotnet35, dotnetdesktop6 and 7 and a bunch of packages all called remove_mono internal. I also installed the rest of the vc++ redistributables through the installation .exes provided by microsoft

Download this .NET 6 version of LODGenx64 https://mega.nz/file/gIBgjTTL#cLvVIkbIHdN9qNdoefVhvl9BDQfOrKh5KWbdQxHiIPE
Rename it to LODGenx64.exe and place it into the Edit Scripts folder.
Then do the same run as before, delete old logs, run xLODGen and just select the one worldspace and terrain LOD meshes selected.
Once the LODGen part starts to show in the messages log you will see it reporting .NET Version: 6.0.x instead of .NET Version: 4.8
Upload new FNVLODGen_log.txt

[kontotnok]

2 hours ago, sheson said:

Download this .NET 6 version of LODGenx64 https://mega.nz/file/gIBgjTTL#cLvVIkbIHdN9qNdoefVhvl9BDQfOrKh5KWbdQxHiIPE
Rename it to LODGenx64.exe and place it into the Edit Scripts folder.
Then do the same run as before, delete old logs, run xLODGen and just select the one worldspace and terrain LOD meshes selected.
Once the LODGen part starts to show in the messages log you will see it reporting .NET Version: 6.0.x instead of .NET Version: 4.8
Upload new FNVLODGen_log.txt

I think this run was successful!!!

Logs: https://paste.ee/p/39Dl2

[sheson]

11 minutes ago, kontotnok said:

I think this run was successful!!!

Logs: https://paste.ee/p/39Dl2

Great. Now generate terrain LOD meshes for all worldspaces to see if it has no errors as well.

[kontotnok]

17 minutes ago, sheson said:

Great. Now generate terrain LOD meshes for all worldspaces to see if it has no errors as well.

Here are the logs, this too was successful I think: https://filebin.net/806drmgsw3q2rl5x

PD: I tried to do a full run, it still crashed but here are the logs just in case they're useful: https://filebin.net/r4sgveh9g9ui1c0r

[sheson]

10 hours ago, kontotnok said:

Here are the logs, this too was successful I think: https://filebin.net/806drmgsw3q2rl5x

PD: I tried to do a full run, it still crashed but here are the logs just in case they're useful: https://filebin.net/r4sgveh9g9ui1c0r

Use this test version of xLODGen https://mega.nz/file/FM4zTILS#MTDiFNgQMngoSyHWNO1f7L9erSNFtgWk7y8kM6hKreI
Delete all old logs.
Only select Lucky38World and only select to generate terrain LOD diffuse and normal textures.
In case that runs through without error, select all wolkdspaces.
This version should not delete any of the temporary *.txt files in C:\users\migu\Temp\FNVEdit\Texconv_*.txt as long as the tool is still open.
Put them all into an archive and then once you closed the tool and it also wrote the FNVLODGen_log.txt add that and bugreport.txt to the archive to upload as well.

[kontotnok]

2 hours ago, sheson said:

Use this test version of xLODGen https://mega.nz/file/FM4zTILS#MTDiFNgQMngoSyHWNO1f7L9erSNFtgWk7y8kM6hKreI
Delete all old logs.
Only select Lucky38World and only select to generate terrain LOD diffuse and normal textures.
In case that runs through without error, select all wolkdspaces.
This version should not delete any of the temporary *.txt files in C:\users\migu\Temp\FNVEdit\Texconv_*.txt as long as the tool is still open.
Put them all into an archive and then once you closed the tool and it also wrote the FNVLODGen_log.txt add that and bugreport.txt to the archive to upload as well.

First run was successful, second one crashed.

Logs: https://filebin.net/nznj4jyywof9nf4u

[sheson]

9 hours ago, kontotnok said:

First run was successful, second one crashed.

Logs: https://filebin.net/nznj4jyywof9nf4u

Repeat the all worldspaces run with this test version https://mega.nz/file/EA5nVD5Q#eOdKKpx3M-MofTaPxNuTQyGnCK9i7iDqwmm9yCt_4J4 and upload new logs and temp folder.

[kontotnok]

1 hour ago, sheson said:

Repeat the all worldspaces run with this test version https://mega.nz/file/EA5nVD5Q#eOdKKpx3M-MofTaPxNuTQyGnCK9i7iDqwmm9yCt_4J4 and upload new logs and temp folder.

Logs: https://filebin.net/19d2yt9wn6o6h7aa

[sheson]

9 hours ago, kontotnok said:

Logs: https://filebin.net/19d2yt9wn6o6h7aa

Do the same with this test version https://mega.nz/file/EZBkhDzK#Y134Dju7ZsZqpC3utCM9i68vXcQ0kltifay5_XHgzWk

[kontotnok]

3 hours ago, sheson said:

Do the same with this test version https://mega.nz/file/EZBkhDzK#Y134Dju7ZsZqpC3utCM9i68vXcQ0kltifay5_XHgzWk

Successful run!

Logs: https://filebin.net/q4sqypu3d9muw4q3

[sheson]

3 hours ago, kontotnok said:

Successful run!

Logs: https://filebin.net/q4sqypu3d9muw4q3

I added a retry of the same command after a brief time if this error happens. Whatever the OS is unhappy about clears up in the meantime... I dot not like that this way we might never find out what the issue really is in this case...

[kontotnok]

27 minutes ago, sheson said:

I added a retry of the same command after a brief time if this error happens. Whatever the OS is unhappy about clears up in the meantime... I dot not like that this way we might never find out what the issue really is in this case...

Damn, maybe it's an issue with umu-launcher? or proton, idk, I'm not giving up tho.

Also I tried to do a full run and honestly I don't even know if it finished correctly, I went to sleep and left it open more than 40 minutes but it stayed there, after I closed it, the window name changed to "Waiting for generator to terminate..." but I waited a lot and it never did, I think the program just crashed, it didn't give me too many logs but I'm uploading them anyways: https://filebin.net/kq4yqwqoj2fce16c

[kontotnok]

Got a successful full run! I generated Objects, Trees and Terrain LOD!!

Here's the logs: https://filebin.net/6crrb0appzm9987d

If you want me to keep testing stuff I'll gladly do so!

[sheson]

On 12/18/2024 at 7:59 PM, kontotnok said:

Got a successful full run! I generated Objects, Trees and Terrain LOD!!

Here's the logs: https://filebin.net/6crrb0appzm9987d

If you want me to keep testing stuff I'll gladly do so!

If you like, redo the test with the released xLODGen beta 129.

In particular it would be interesting to know if LODGenx64.exe compiled for .Net Framework 4.8 is still having issue unlike the .NET 6 version.