Steam version 1.12.x
Installs from Steam, launches and all seems to work with the changes mentioned.
What does not
Nothing, so far
What was not tested
Software/Wine/Direct3D/VideoMemorySize registery key needed to be set to my VID RAM size or the game run out of video ram when a new mission was created. Without this the game crashed whenever a mission was start (right after the sheath is pulled off the sword during mission creation - the sword is the progress bar). Running with a virutal desktop, though that may not be required.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)||Oct 13 2017||2.18-staging||Yes||Yes||No||Platinum||Theodore Darelizer|
|Current||Gentoo Linux x86_64||Aug 27 2013||1.4.1||Yes||Yes||Gold||an anonymous user|
|Show||Ubuntu 11.10 "Oneiric" amd64 (+ variants like Kubuntu)||Feb 18 2012||1.4-rc4||Yes||Yes||Bronze||Matthew Meyer|
|Show||Ubuntu 11.10 "Oneiric" amd64 (+ variants like Kubuntu)||Nov 04 2011||1.3.31||Yes||Yes||Platinum||ConanHUN|
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