Old versions from 1.0 to 1.2
Completed singleplayer war-campaign, worked flawlessly.
I also played e few other games and it worked too, so I assume that singleplayer does work completely and bugfree (as it is).
What does not
What was not tested
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Gentoo Linux||Jan 24 2021||5.0.3||Yes||Yes||No||Platinum||K1773R|
|Show||Debian 10.x "Buster"||Feb 27 2018||3.2||Yes||Yes||No||Platinum||Alexander Schlarb|
|Show||Ubuntu 16.04 "Xenial" i386 (+ variants like Kubuntu)||Jun 06 2017||2.0.1||Yes||Yes||Platinum||Jaroslav Smutek|
|Show||Ubuntu 14.04 "Trusty" i386 (+ variants like Kubuntu)||Nov 19 2015||1.7.55||Yes||Yes||Platinum||Jaroslav Smutek|
|Show||Linux Mint 16 "Petra" x86_64||Mar 08 2014||1.7.13||Yes||No||Garbage||an anonymous user|
This should work for any app, if you have Intel + AMD or AMD + AMD with open source drivers.
If you have laptop with hybrid graphics cards. You can launch game with command:
env DRI_PRIME=1 vblank_mode=0 wine ~/path/to/your/exe/file
In case of using command, you get swich to powerful graphics card and disable vsync for more FPS.
If you have Mesa drivers 17.x.x or more, you can use this command:
env DRI_PRIME=1 mesa_glthread=true vblank_mode=0 wine ~/path/to/your/exe/file
Last command is most best in performance that you can get in this moment, you can use it for any wine application that you need. But argument mesa_glthread=true may not always work, so if your app crash, remove it.
For Steam users, you can set environment variable of any applications in properties.
DRI_PRIME=1 mesa_glthread=true vblank_mode=0 %command%
(It will work only with native Steam for Linux) For Wine, you have to start Steam or game with those arguments