
VinLudens
Published
Click "Play" and you're good! Works fantastic with a PS4 controller!
Moving game to different screen required to use windowed mode, move the window, and then go fullscreen again. It did not automatically detect which screen to use.
The game runs incredibly well. I did notice slight stuttering from time to time when using the game's upscaling. The stuttering did not reflect in the framerate / frametime though, hard to tell if it's the game or proton.
Worked right out of the box!
The framerate is at times a bit unstable, even if the system is not running at 100%. Unsure if the game is to blame or not. Tried tweaking the graphic settings to try and resolve the occasionally unstable framerate, but the issue seemed to presist. The game defaults to automatically setting graphic settings, which have overall worked great so far!
Works flawlessly with a PS4 controller!
Works well, avoid too high graphic settings
In tutorial mode the game ran mostly fine at 2k medium-high settings (with upscaling). In multiplayer I had to go 1080p and reduce a few settings to obtain a stable experience.
Many stutters, but it may be due to my internet connection. Surprisingly, lowering graphic settings gets rid of a lot of stutters (which were not present in tutorial mode)
In multiplayer, the performance was considerably worse than in tutorial (offline) mode. It is hard to say if my internet connection is at fault or the game. Lowering resolution and a few settings makes for an overall solid experience.
Extreme stuttering and freezes were mostly ironed out by using the following cache files: https://github.com/bcook254/apex-legends-cache (README contains instructions on how to use them)
Without the additional github repository with apex caches, the game was unplayable with extreme stutters and freezes lasting a few dozen seconds. Turning down graphic settings only occasionally improved things.
Occasional lag, but infrequent enough to not be a major issue
Without the extra cache files, the game was as good as unplayable with big stutters and freezes. Adding the cache files irons things out considerably. It takes a few matches though before it is a fully smooth experience. After that, the game runs really well!
Honestly, I would not have stumbled upon these cache files if it weren't for a recent report here. Here is the GitHub repo in question: https://github.com/bcook254/apex-legends-cache
Occasionally random and persistent drop to 2 FPS until restarting game but otherwise runs super smooth
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 mangohud %command%
Setting the game resolution to anything lower than the screen resolution would make the "fullscreen not fully full". To be fair: After quite some fiddling around it eventually decided to just work, as if there never was a problem to begin with.
After playing for a while (30-60 minutes) the game seems to randomly dip to 2 fps after opening a menu (mainly the upgrade menu from what I see). Only reliable way to resolve it is to go to main menu and hop back in (luckily it almost always occured in a safe area for me).
Getting the game to show up on a second screen was quite a challenge. Getting it to properly go fullscreen with a resolution lower than the screen resolution proved challenging as well. Both problems eventually fixed themselves after trying the same thing over and over again. The random yet persistent dips to 2 fps are quite detrimental however, and do require going back to the main menu at the very least (if the game even remains responsive) to fix it again. It seems to begin after interacting with the upgrade menu in a safe area. Apart from this, the game runs really well!
PROTON_ENABLE_NVAPI=1 gamemoderun mangohud %command%
It seems that videos playing in-game (most notably: on "screens"; in the death screen; on animated "holograms") do not appear at all. Also textures tend to flicker from time to time, but nothing too offending.
Game's window seems to have lost focus from time to time and caused a massive FPS drop down to 2-8 FPS and the game became almost completely unresponsive (probably my WM is to blame). The issue seems to be completely resolved by using gamemoderun
.
Without gamemode, my game would occasionally drop FPS and become unresponsive, most likely due to the window losing focus and I could not get the focus back. The only way to fix it is to pray that a save occured recently enough, and battle your way through the pause menu, and then back to the main menu. From there it works fine again. I have not faced this issue anymore after introducing gamemoderun
; seems to work pretty great now!
DXVK_ASYNC=1 mangohud %command%
Cannot bring game to 2nd screen. Should be done from "Configure Binary Domain" but the change in question never persisted.
The sensitivity feels awkward at times (using mouse), but the game itself might be to blame.
Heavy stuttering by default. As mentioned in another report, setting DXVK_ASYNC=1
solved the issue for the most part, and only occasional and very slight stutters remain. It may take a few minutes after the game is launched, but feels overall very smooth nonetheless!
The stutters were a big dissapointment, but they are luckily fixable for the most part. Also, the game itself seems capped at 60fps; it does not seem to be a linux related "issue".
Game just doesn't launch
I tried different proton versions but to no avail. Probably linked to every other report here thus far.
Runs out of the box with Proton 6.3-8. Proton 7.0-1 seems to run the game slightly better but requires multiplayer to be disabled.
PROTON_ENABLE_NVAPI=1 mangohud %command%
Occasional but small FPS drops. After fast traveling the game stutters quite a lot however and needs to be restarted.
On Proton 7.0-1 the game freezes completely at random points in time (usually within 10-30 minutes) and needs to be force killed. As proposed by another report, switching to single player mode seems to resolve this issue.
Did not try on Proton 7.0-1 but with Proton 6.3-8 it works pretty well. However, I have one of two friends with whom I cannot be in the same session for too long, as then either me or him keep disconnecting.
DLSS upscaling was not available out of the box for me, only FSR and linear. To enable DLSS, PROTON_ENABLE_NVAPI=1
was required, as mentioned by other reports.
Works great! Hotfix seems to have fixed the crashes reported here, and coop works wonderfully!
In windowed mode the game would display a white border around the screen. Switching to fullscreen solves this.
Game only crashed 1 time in two hours when a friend tried to join for the first time in the middle of the extraction cutscene.
Hotfix seems to have fixed the issues, I really have not experienced anything unusual or unexpected in terms of crashes. To be fair, I haven't started the game before the hotfix, but it worked pretty much flawlessly out of the box!
You MUST NOT have the game in fullscreen when launching. If you put it in fullscreen when closing the game, you will be stuck in a black screen upon the next launch. I edited the config file to disable fullscreen, since I was not able to get into the game to disable it. Make sure to set fullscreen = false in the config file.
Config file: /steamapps/compatdata/553850/pfx/drive_c/users/steamuser/AppData/Roaming/Arrowhead/Helldivers2/user_settings.config
Borderless Window leads to a white border around the screen.
Fullscreen leads to the game not launching the next time.
Works really well, minus the windowing quirks. Also performance feels like it should be a little better, but nothing too distracting.
Worked really smooth out of the box with no tinkering whatsoever!
I played the demo version. Steam automatically put me into proton instead of using the native build though (maybe native was not available for demo, I don't know)
Fullscreen and performance issues are simple enough to fix, runs very smooth after that
Fullscreen exclusively went to laptop screen, not external monitor. Manually moving window to exertnal monitor triggered the white screen issue. Fixed by disabling fullscreen in-game, and creating window rules (in the window manager) to maximize the game window and remove borders.
Reducing AA had a small impact. Enabling "low resolution buffers" solved the issue (without it, GPU usage would be very unstable, varying between 50% - 100+%).
Works great with a controller as well! Sadly no playstation controller buttons prompts.
The only real issue encountered so far were the frequent freezes and stutters when the game is loading, which can be annoying.
Game did not launch with proton no matter which version (7.0-2, 6.8-3, 5.13-6) so I had to resort to the native version.
Mouse clicks did not work in the main/pause menus. Plugging in a controller seems to fix this issue (not tried repeatedly).
The game seems to freeze for a few seconds when it's loading in-game. It happens rather frequently and can get annoying.
Game doesn't launch with proton. Native version seems to have performance issues (even though my hardware can handle the game with ease at max settings).
Force proton and you're good to go.
The sensitivity seemed tied to the FPS. Hard to say if that's the game or not. Haven't noticed similar behaviour in other games so far.
Installation broke, so I had to reinstall. But after that the game finally worked with regular proton (had to use GE before). Seems to run much smoother as well now compared to a few months ago with GE!
Works right out of the box!
It seems that alt+tabbing out of the game makes button bounds higher than they should be.
Very unstable fps. The game feels rather smooth despite that.
Game runs pretty solid despite seemingly unstable fps. I am curious if using proton will solve this (so far it always solved unstable fps issues on the few other native games I tried).
Doesn't launch when forcing to use proton. USE NATIVE VERSION instead!
Tried launching the game with proton instead of native, to see if performance would improve. Sadly, launching the game makes steam say the game is running without anything happening. The native version works just fine though, so just stick with that!
Worked out of the box! Simply click "Play" and you're good to go!
FPS drops while traversing during the prolog and during intense combat.
PROTON_ENABLE_NVAPI=1 mangohud %command%
The window which opens before the actual game (checking for updates, etc) seems to dislike when you focus another window on your desktop after some time and turns black. To solve that, minimize said window, unminimize it, and do not focus a window other than that one (if you do, just repeat the steps).
Also some minor trouble getting fullscreen to work properly for the actual game. After some back and forth in the settings it decided to work. Works great now!
The game seemlessly transitions from single to multiplayer by grouping you up with other coop players. No issues to be reported in the little time I spent playing coop.
The game runs incredibly well on my machine (performance wise). You will notice some rather hefty sutters when the game seems to be loading in the background though, but the game itself might be at fault here. I remember similar stutters back when I played it on PS4.