AndyMcNab
Published
Works - For me required Proton GE 7.3 (7.0 launches but EAC is _broken_), inconsistent launching to ALT+Tab, minor stutters but untweaked.
Occasionally I have to ALT+Tab out and back to the game because the screen is black but can hear the intro video/menu.
Stuttering despite pre-caching all Vulkan shaders prior to launch
If you accidentally close IBus (keyboard language selector) you cannot log in to your EA account on the Steam overlay. [This isn't a bug with the game, rather the Steam overlay in general].
Performance is genuinely surprisingly good, stutters are likely fixable with time. Not yet tested in a live match. I consider typical gamers wouldn't put up with having to mess around with custom Proton builds nor guessing with ALT+Tab most times you launch to get the game to display. For everyone else who isn't lazy or on an input limted device (like the Steam Deck might be, since you have no means of ALT+Tabbing), this is fine.
Proton-7.0rc6-GE-1 GloriousEggroll
VK_ICD_FILENAMES="/opt/amdgpu/etc/vulkan/icd.d/amd_icd64.json" VKD3D_CONFIG=dxr %command%
Seems like key-press circular animations for key hints are drawn behind the icons/too tight a radius where these are normally visible around the outside of the icons
Selecting secondary screen changes properties to match on the default monitor (Same issue as faced in other titles, like GTA:V etc). Mouse gets stuck to left hand side when secondary monitor is disabled and launch in fullscreen mode. Toggling to windowed mode allows the mouse to function better. Possible this is an Xorg/MATÉ desktop issue - i.e. 'Main monitor' is not the left-most in frame buffer.
Stuck to left hand side of screen
Mostly keeping above 50FPS regardless of resolution and quality settings but not hitting smooth 144FPS meeting max refresh of monitor when run naitvely on Win10.
Slow first loading is to be expected, sitting at 21% for a good 20+ minutes though felt a bit slower than on Win10 - Just be patient, it will get past it. This is not a Proton issue.
Garbage tier ever since Proton-5.x
Not helped by broken launcher/required applications (Not Valves fault) but the installer script for Proton-6.x / Experimental expects to install a build of DirectX that isn't even bundled with the game files, so it ends up stuck and has been broken for a good 4 months at this point AFAICT. Nor do later builds of Proton-GE-6.20 / 6.21 work either.
Overridden VK_ICD_FILENAMES to use correct ICD profile JSON file: /opt/amdgpu/etc/vulkan/icd.d/amd_icd64.json
Proton-6.21-GE-2
Wrong screen used, selecting 1 or 2 makes no difference, doesn't remember between launches. So best to simply use windowed mode and run just smaller than your native resolution. Mouse X&Y is also permanently offset even in fullscreen mode plus glitchy for using the menus/map. Use the keyboard for navigation and simply keep retrying to click on items on the map by quick double clicking.
Highest settings for shaders/particle effects is marginally worse than native Windows AFAIK
If I set shader effects below normal it can end up a complete white-wash with the lighting being blown out of proportion.
Works with one minor fix to the launch arguments
Similar to GTA:V due to the large number of files needed setting the launch command with No ESYNC: "PROTON_NO_ESYNC=1 %command%" solves the infinite loading screen of nothingness upon first starting the game. Thank me later.
VKD3D_VULKAN_DEVICE=0 %command%
Works with envvar fixes
Currently DoA regardless of Proton version
At time of writing, my understanding is it is DoA for running under Proton for anything other than the Steam Deck or particular hardware+software combinations but it's early days yet.
In my case, none of the recent Proton releases nor Proton-GE up to GE7-24 seemed to work. I am aware of GE7-26 but none of the release changes are likely to address the issues here with such a recent release.
Issue raised with Valve on Proton GitHub: https://github.com/ValveSoftware/Proton/issues/6017
Give it some time and input from Valve + developer (if necessary) to reply to an existing issue raised
Works after envvar overrides + AMDGPU-Pro Vulkan ICD for VKD3D RT to detect
VKD3D_FEATURE_LEVEL=12_2 VKD3D_CONFIG=dxr11 VKD3D_SHADER_MODEL=6_6 VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json %command%
VKD3D_FEATURE_LEVEL=12_2 VKD3D_CONFIG=dxr11 VKD3D_SHADER_MODEL=6_6 VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json %command%
Does not work out-of-box but a few envvar overrides and packages correctly satisfied VKD3D RT requirements
Possible to get it working if you persist with Ubisoft Connect, launching the game itself is at least possible in single player mode.
Proton-7.0rc6-GE-1 GloriousEggroll
Must to change the launcher to start Ubisoft Connect, set the launch options to: "C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\UbisoftConnect.exe"
Let it update a dozen times, log in and hope that it presents you the option to "Link account with Steam.
If you miss the opportunity, delete your prefix directory do the above again and add the switch, '-uplay_steam_mode' like so: "C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\UbisoftConnect.exe" -uplay_steam_mode
When entering vehicles, the mouse will snap to view 180 degrees the wrong way and you cannot change the 3rd person view. Press M to open the map and exit again, mouse will be released.
Given the local single player runs a server, the physics seems to run a bit behind the client so you get juddery collision detection with vehicles when diving along. Other than that all fine.
Must use custom, non Valve, Proton build
Version required at time of writing: Proton-GE-6.21-GE-2
Proton-6.21-GE-2
Does not obey the primary screen set by window manager. Not game specific, this is a wine and-or window manager issue I presume - I use MATÉ.
