MagneticIce

I myself have been carrying out a fair amount of testing around the "A call to an OS function failed" error so I figured I would share my findings. Firstly, this is specifically an issue with Texconv and as such it also effects other software that uses Texconv such as Wabbajack. Secondly, this error only occurs on versions of wine with the staging patches applied to it (i.e. wine-staging, proton etc.). The basic version of wine without the staging patches can be used to run both Texconv and Dyndolod without issue (at least as of wine version 9.22). Thirdly, it seems like this error may only occur on specific distributions of Linux but I haven't done enough testing to confirm this. Fourthly, this error occurs at random. I tried running Texconv on the same texture file over 200,000 times using a bash script and found that, with a probability of around 1 in 4000, Texconv would fail and would not produce any output. When Texconv failed, the following attempt to run Texconv always succeeded so I suppose one failure doesn't affect the odds of another failure occurring.