Scrubby
Published
EA just announced end of support for linux and deck
Worked out of the box once proton 7 was enabled. I also installed a fix for 21-9 displays which I obtained from WSGF. The exe swap worked.
Crashed once in around 5 hours so far
Campaign does not work - multiplayer not tested
PROTON_USE_WINED3D=1 gamescope -W 2560 -H 1080 %command%
Game asks for MFC42 to be installed
The game launches, and the tutorial seems to work although I did not finish it.. The character creation works, however during the first mission when you choose the first dialog option that appears the game crashes. The error log is no longer reporting an obvious error after installing MFC42 as well as enabling "PROTON_USE_WINED3D".
No issues at all, perfect experience out of the box
The mouse cursor is not detected until you click once inside of the game window, which can lead to accidentally clicking buttons.
Runs as flawlessly as this game can. Controller was detected no issue. There are slowdowns at times when things get really crazy but that also happens on windows. MDickie W.
PROTON_USE_WINED3D=1
Installation of MFC42 is required.
Playing the GOG version through heroic, installation of the windows component "mfc42" is required to get to the launcher, and adding "PROTON_USE_WINED3D=1" in the environment variables is also required. Heroic makes installing the mfc part very easy, just click on the winetricks button.
WINEDLLOVERRIDES="xrRender_R2.dll" PROTON_USE_WINED3D=1 DXVK_FRAME_RATE=1 %command%
The default file "user.ltx" is corrupted by default and contains duplicate entries, the second block of text must be manually deleted for the game to launch.
Additionally, enabling UMU for steam runtime was required in Heroic to get the GOG version to launch.
The shadows are broken on wide and ultrawide displays by default. While ingame open console with "~" and type "r2_sun_near 1" to fix it. Addtionally, while not a bug the headbobbing can be nauseating for some, open console again and type "cam_inert 0.01" to reduce it, or change to a value of 0.00 to disable it.
When gamescope is enabled the cursor stops being detected entirely.
The GOG version of the game runs fine once all is said and done, however it took me a few hours to get this actually functional. Maxed out settings at constant 60 fps with no further issues that I've seen.
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json %command%
There is a bug with some (AMD?) systems where after a game pause the framerate will drop considerably to where it is unplayable. Switching the amd gpu driver to AMDVLK instead of RADV not only fixes this issue completely, but I saw higher framerates in general when using that driver. This driver seems to stutter intensely when first loading in assets, but that's a one time thing for the first time you visit a planet, actual gameplay was a smooth constant 60 aside from that.
gamescope -W 2560 -H 1080 -- %command%
When tested on zorin alt tabbing could crash the game, gamescope fixes it. Have not tried disabling gamescope on Garuda to test this.
I've been playing the beta for the next major release and it's been perfect. No unusual slowdowns, only the typical long drive lag. Additionally, hosting multiplayer worked perfectly from my linux pc meanwhile my windows friend was unable to host.
The mod manager (when not running the beta branch, as it is not yet updated for that) also works perfectly, just put it in the games directory and open it with protontricks.
gamescope -W 2560 -H 1080 %command%
Alt tabbing can crash the game, gamescope fixes the issue, however when running via gamescope you cannot paste from the clipboard into chat, making trading from warframe.market annoying.
Game runs great and feels fantastic. I just have to open it without gamescope to trade with other players since gamescope blocks the clipboard, but that is the only annoyance I have come across.
