Kepos
Published
No native, no Proton run.
On Linux native the game didn't start, so I switched to Proton (6.3-4). Then I was questioned to install Battle Eye, which didn't work so the game won't start at all. Do not try to install the Battle Eye multiplayer spy, otherwise your installation will not start.
Refused to start at first try due to directX11 error popup. So I tried 'PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 %command%' and all worked quite well. Videos sometime stutter a bit and loading times between planets are a bit longer than in Windows.
Works quite well on LM19.1 with Proton support. While loading music sometimes got silent, no crash.
Launcher issue still not fixed. The launcher still starts only once! Needed to backup dowser.exe and rename AowPF.exe -> dowser.exe - This will outmanouver the broken PDX launcher and the game starts without any mods.
Tested with SD client so far, as amdgpu-pro with vulcan is not supported yet on LM19.1.
Launcher starts and game started often but had crashes several times. First crash was at starting game while I changed localization to other than EN, so I only use EN for now. Game started for me with 'PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 PROTON_FORCE_LARGE_ADDRESS_AWARE=3 PROTON_LOG=4 %command%' startup option. Changed settings and started PvE game...crash on battle queue, while AW was still active. Had to do a full restart, which I recommand for any new attempt, otherwise you'll get crash before login. Obviously the Proton/Wine wrapper uses Windows XP, as I found out by viewing crash log. Probably there is an option to change this toward Windows 7 or 10 I do not know yet. Well, SMAA doesn't work for me in any version. With disabled AA I can join Alabino booting camp, probably also some battles, which isn't usefull until it runs more stable. But this time it crashed for me on leaving battle. It seems I need to get amdgpu-pro graphic drivers with vulcan running and/or have to fix settings to fit more toward my openGL surrounding.
After managing to install AMDgpu with Vulkan support on my Linux Mint system, I was able to change from OpenGL with major upgrade in graphic details settings. No need to tweak any longer, game starts and runs like native with HD client.
There are some issues, like really annoying command and movement delay, which also had been with OpenGL, so I guess it is the Proton wrapper to cause it. Informations have to be catched up and be processed by Wine/Proton before they are sent, which causes minor delay. Sometimes game hangs on exit, but not very often. So, the game is playable with the given delay issue, which makes fast vehicles no real fun at the moment, but it's totally playable with standard tanks.
I played Armored Warfare on Steam for a while now and it is amazing how far Proton has updated. Currently I'm playing with latest AMD mesa (+opencl) and Vulkan drivers without any issue. If you don't mind changing files, you could even switch to your already existing My.Com accounts if you rename steam_api.dll in game folder to something else. Using Proton 6.3-4 runs like native to me. Only re-installing of Microsoft parts showed me some Windows origin UI, but had no influence on the game itself.
First try crashed game, but I added 'PROTON_USE_WINED3D11=1 %command%' to start options for next try and game starts and runs without a problem now.
protontricks -c 'mkdir ../../compatdata/359320/pfx/drive_c/users/steamuser/Local\ Settings/Application\ Data/Elite\ Dangerous\ Launcher_evidencehere' 359320
The former reports are a little bit inaccurate, so here is my 3 step-by-step introduction:
First you have to install 'winetricks' from your repository.
Second, I followed the offered MKDIR command in terminal from: https://github.com/redmcg/wine-mono/wiki#with-protontricks with adoption of the path to my very own system.
Third, started the game without any issue on Steam. No need to install wine or mono or anything else for me on Arch Linux with latest mesa (don't forget about opencl) + Vulkan drivers.
Used 'PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 %command%' for starting options. Game starts and runs without major issue. In ship design game stuttered but without crash. As I am using mods, this may have caused it.
Had the same 'shader model 3.0' error and tried to find OPTIONS.txt at '~/.steam/steam/steamapps/compatdata/660160/pfx/drive_c/users/steamuser/My Documents/My Games/FieldOfGlory2', but it was not there. I found a quite good hint at 'https://steamcommunity.com/app/660160/discussions/0/1744479063998845036/' to simply build that file if you do not find it. I included 'RezX xxxx (width of yr current display setting) | RezY yyyy (height of yr current display setting) | Fullscreen 0' and the game started like a linux native.
With usual unspecific Proton, I did get an Unity error. I had to switch to 6.3-4 for full support.
First bare test brought a crash, so I tried 'PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 %command%' in starting options. Game starts and runs without a problem. Graphical details may be little less than in Windows, but that's a AMD driver issue.
Motor Town runs on Linux like a native.
Multiplayer runs without any issue.
Steam Experimental worked; no starting commands worked -> CTD on start; on server login EasyAntiCheat wasn't able to find files
game 'would' run, but the EasyAntiCheat blocked me
Test without starting option didn't work. 2nd try was with 'PROTON_USE_WINED3D11=1 %command%' but brought me only to the game launcher, while starting game lead me into a black screen. On 3rd test I used 'PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 %command%' and launcher and game worked. There is one little issue, when I start game from launcher I first get into a black screen, but after a while when I click somewhere the game menue shows up. Rest works as intended.
Game crashed on startup and I was not able to kill the process in Steam client. Manually ended it in System Monitor, but needed Steam client to restart to catch it.
After bare try and crash I tried now another time with 'PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 %command%' active and game starts and runs without a problem.
Would be nice, if one could change or delete former report. Otherwise I have more than one active.
Game starts and runs with 'PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 %command%' but unfortunately the graphic quality is far from satisfying. Videos stutter sometimes. On battlefield, colors are kind of psychodelic and woods and bushes seem to be only dark. Probably it needs some more tweaks, but it could also be open amd graphic driver to cause it.
Game crashes on all tries. First bare attempt brought game to end without notice at startup. Second I tried to change starting options 'PROTON_USE_WINED3D11=1 %command%' but got error popup about missing directX11 dependence from game code. Plus, I got several popups about missing fonts. The third test with 'PROTON_NO_D3D11=1 %command%' brought the same error messages. Fourth test with 'PROTON_NO_D3D11=1 PROTON_NO_ESYNC=1 %command%' produced hangup. Steam shows the game is running, but nothing happens. Can't even kill the app and Steam isn't able to end it. Restart necessary.
Other players noted that it was playable with Proton support. It seems some of the latest patches has broken it. Game runs, but I can't get beyond (failed) intro, which only shows a black screen.
Former missed videos, which prevented the game from starting, are now replaced by a test pattern with very loud noise, but you could click them away with one click.
Linux native
Information from the developer: currently the Map Editor DLC is not Linux compatible, the rest of the DLC are
On first try, game crashed on start and the whole Steam client crashed with it. On second try, I got a notice about missing directX files. Latest AMD driver is installed, Vulcan is installed. I wasn't able to get the PRO version to activate on Linux Mint, so the systems keeps running with open drivers. As far other testers reported, Nvidia graphics/drivers seem to work.
First attempt crashed, so I gave it another try after a while. Can't add to my first 'borked' report, so I write a new one.
After a while I read about the proton starting options and gave it a try. First I used 'PROTON_USE_WINED3D11=1 %command%', but the handling was cluncky and some features like changing ship color not working. In my second try I used 'PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 %command%' and game starts and runs without a problem. Due to open drivers the details of ship and scenery aren't too nice, but acceptable.
The new Aspyr-Launcher works quite fine but only for the base game.
Problem is, the huge workshop section is not working for Linux. There is no guarantee, that any MOD will run on Linux. Testing and re-starting the whole game for every single MOD you add is a nightmare.
More harming is, that DLC doesn't have native support for Linux too. If you try to start a game with DLC (Rise & Fall 2019 in my case), you can't choose any settings in the menu any longer and game freezes in that view.
Linux support by Aspyr took ~1 year after release to come, each DLC may need the same time to get a workaround.
Launcher and game start with 'PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 %command%' while it really takes long to wait at loading screen. It seems to be frozen, but underneath the system is still loading. No problems found further.
Runs quite fine with bare Proton start. No fixes, no starting options. Even mods with passive SKSE (Skyrim Script Extender) seem to work. Only problem is the already anounced 'end game' bug, where the app freezes.
Warlock II comes with native Linux support out-of-the-box. Game runs without a problem, except the graphical details are way more basic then on Windows.
It seems the generic AMD gpu driver shrinks down the options for graphical details, so it is more a driver issue then a game related one. My LinuxMint 19.1 does actually not support installation of amdgpu-pro.
First I tried Proton 6.3-8, but I had the same issue as reported from other players. Popup of a terminal at start, but without any progress. Then I switched to Proton Experimental, where some kind of code is seen at the terminal and the game startes. So far no other issue, game runs like native.
First bare attempt crashed with directX-error, so I added 'PROTON_USE_WINED3D11=1 %command%' in starting options and game starts and runs without a problem.
Proton 5.13-6 started Launcher for me
After testing several Proton versions, I managed to start the launcher with Proton 5.13-6 and the following starting command: ''PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=2 PROTON_FORCE_LARGE_ADDRESS_AWARE=3 PROTON_LOG=4 %command%'' -> unfortunately the Launcher brought up a notice, that I cannot play, because my Steam account (email) is already in use with a Wargaming.net account. So...from my view, they seem to actively block the use of already played accounts. Reason might be to earn good money from fresh accounts.
