dhewg

Oh, sorry for the late reply, I missed this! That's mesa code, which definitely is a job for @axeldavy :)

About GTA, can you please paste a verbose debug log when this is happening? `WINEDEBUG=d3d9nine wine ...` The battlefield issue sounds like a job for @axeldavy though :)

Sorry for the late reply. I don't think I've seen that error. Do you still get that or could you solve it. If not we need more info: - what...

The lib32/bin32 paths come from `release.sh`. That script builds 32 and 64bit binaries and adds `nine-install.sh` to easily install the built binaries from those paths. No system lib/lib32/lib64 paths are...

Hm, nope, it looks like `nine-install.sh` isn't part of that rpm: https://build.opensuse.org/package/view_file/openSUSE:Factory/wine-nine-standalone/wine-nine-standalone.spec?expand=1 Are you mixing release tarballs from here (maybe over wintricks?) with that rpm? That probably won't work

It depends on how you installed this package. If you use winetricks or the bundled nine-install.sh, the checkbox in ninewinecfg should just work. For automation you can use its cmdline...

Maybe the game runs out of address space. Proton has `PROTON_FORCE_LARGE_ADDRESS_AWARE` to fix affected games. I don't recall if wine-staging has a way to force it, but you can always...

Do you still get that error with recent versions?

Is this still the case? Generally, we do ship a 64bit d3d9.dll, and the few 64bit dx9 games do work with that.

The paste site doesn't work atm, can you please add the log here in a code block (starts and ends with three backticks, see also the "M" help icon on...