Xbox One Controller works, but mouse movement is very slow.
For some reason it works without experimental but I had to turn it on after a week of not using any tweaks. Otherwise, no significant issues and greatly better performance than Windows.
-dx11
If you have Intel ARC just set the environment variable DXVK_FILTER_DEVICE_NAME= followed by "your card ID" under Heroic advanced option and you ready to go.
gamemoderun %command%
The game will not launch without proton
Works perfect!
Nothing needed to be done. Just clicked play and got to building! :)
Game works well. Pointer has a tendency to slide off some of the in game pc screen menu options.
Runs like a charm
Alt-tabing seems to behave a little funny, but might be the game
Tabbing out of fullscreen froze the game for about 5 seconds every so often
Launches but No image
When I launch the game my screen freezes on the frame it was at. Everything else in the system continues to work fine though.
The game works well, no trackpads may be a dealbreaker for some.
Everything I tested worked, I could perform 3dmark ingame, save the game, etc... Only problem I found is when a I apply graphic settings.
mangohud %command%
I have 2 monitors, when graphics settings are applied, it switched to my other monitor back and forth
When a I apply graphic settings, game jumped from one monitor to the other
gamemoderun mangohud %command%
Played for 2 hours, no problems spotted.
Works Great OOTB
Not a particularly powerful system, so some sacrifices had to be made for the game to be playable, but it works without any significant bugs Out-Of-The-Box.
Game runs semi-perfectly
Game sometimes crashes when you tab out. It's a rare occurrence though
Se lance sans soucis, mais est un peu plus gourmand que lorsqu'il est lancé nativement sous Windows
PROTON_USE_WINED3D=1 %command%
Le jeu rame un peu plus que sur sous Windows, et les temps de chargements sont clairement plus long. Rien qui ne soit rédhibitoire à l'expérience du jeu ceci dit.
I managed to used 3DMark normally within the game, so I guess this isn't an issue on my config.
J'ai pu utiliser 3DMark normalement dans ma partie, je suppose que ma config n'a pas de problèmes avec ça.
Launching directly without forcing Proton had the game launching and crashing before it even created a window. With Proton everything worked perfectly.
3DMark in this game is a cruicial aspect. If it doesn't run, gamers will not play on Linux
Installed Windows Media Foundation
3DMark in the game does not run. Even though WMF is installed.
We need more streamlined way to handle video codecs. I've tried with Proton-GE-Proton7-30 as well. No joy.
The Slowdown Was an Issue, but I Can Live with It.
The game kept getting slower as it went along, even reaching a point where my animated desktop wallpapers on my two other monitors(via Wallpaper Engine and a KDE Plugin) actually stopped. When I closed the game my system was completely unresponsive, forcing me to reboot.
Overall the game installation and setup was a breeze. Only the eventual slowdown was an issue. So simply play for an hour, save, restart, and you should be good.
Worked Out-of-the-Box
No problems whatsoever.
Be sure(for Arch-based distros with Nvidia cards.) that you have the lib32-nividia-utils package installed.
PROTON_USE_WINED3D=1 %command%
Had to toggle fullscreen on and off for decent framerate. (Also had to switch from the Executive Workshop to one that is less intensive.) Odd given the hardware.
Occasionally, there are some FPS hiccups.
gamemoderun mangohud %command%
With my setup, the GPU is getting sacrificed at 1440p at decent looking settings.
Also recommended is the FPS Boost mod.
Missing text in menus is fixed by installing a specific font through winetricks. Not sure which one because i installed all of them :/
Wine GE fixes the 3DMark blackscreen problem in-game, and Proton GE should too.
The default layout does not take advantage of the trackpads for a game that relies heavily on point and clicking.
You cannot run 3DMark in-game, which stops you from completing many contracts.
Cannot use 3dmark on vanilla proton. Also crashed on exit afterwards. Had to start with a clean prefix and run GE
There was a lot of stuttering but I blame it on the low-end hardware of this laptop.
It's worth noting that I always use Proton experimental so I can't say for sure how well this will work on stable versions of Proton
