dkfljaslkdfh

Hi! I'm having the same issue, now with Dyndolod. This is strange, because I was having the same issue with xLODGen, but now it's working fine. It's exactly as described in the OP. The only thing that changes is the mod being processed at the time. Can you take a look at the logs, please? bugreport: https://paste.ee/p/z6QJ6 log: https://paste.ee/p/zaiPI Thank you! EDIT: I forgot to mention that the tools are on a drive outside of the MO2 and the system folders. Also, I'm using the x64 version. I tried with the x86 and it worked with a clean install of the game, but with the full mods it stopped without giving me an error, it just hanged.

Hey! Thank you for helping me! I was able to generate the files just restarting xLODGen every time it failed. I'm using a 1TB SSD with ext4 file system, 32GB of RAM, and I created a swap file of 6GB. The swap definitely helped with TexGen, but not with xLODGen. I tried both versions of the exe. The output directories were set according to the STEP instructions, in exclusive folders, separated from the game. I didn't try the other options you mentioned because in the end, it worked. And now I have a bigger problem, Dyndolod is making fun of me! But I'll try to solve the problem on my own before asking for help. Thanks again!

Hi! I'm trying to run xLODGen, but it fails after some time, showing different errors every time. The most common is "A call to an OS function failed", with TexConv64.exe. I tried following the suggestions I found here: But nothing worked. I'm on Archlinux, tried proton GE, 8, 7 and 6 via Steam. I compressed the logs all in this file: https://1drv.ms/u/s!AhMlyqThKuq1k4wj_uXXq-s2PgXOAg?e=X3SeWG