PlayableShow Details
Unknown
DXVK_HUD=compiler __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
When booting the game, if the game is not in focus when it starts, you will click through the game and go to the window "below" it.
After roughly 2-3 matches your player starts heavily jittering. In-game FPS counter drops significantly, but stays at 130+ (down from 300+) Even though the FPS is listed as 130+, the gameplay experience is more 15 FPS Strangely enough, Only your first person animations and camera movement is at this 10-15 FPS.
If you hold still completely, you can see other players and the map itself move in the listed fps. And the game UI still moves at full FPS
(Video Available)
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1
I had a problem with the camera, it kept looking up
Last season (16) broke my player's camera, now I can only look up
DXVK_HUD=compiler __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
The game is playable as is, but there are a number of issues that require some tinkering.
Here's the issues and their correspoding fixes summarized:
- Poor performance during the first 5-10 minutes of gameplay due to shaders recompiling every game launch. The
__GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1env variable fixes the issue - The game freezes or crashes randomly, usually after spawning/respawning. Selecting Proton 8.0 prevents these crashes from happening
- Poor performance overall, fps lower than 60 and random stutters. Deleting the game's wine prefix (usually located at
$HOME/.local/share/Steam/steamapps/compatdata/APP_ID) fixed this for me
Also the DXVK_HUD=compiler env variable toggles a helpful shader compilation status overlay at the bottom-left corner of your screen
STAGING_SHARED_MEMORY=1 __GL_SHADER_DISK_CACHE=1 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 __GL_SHADER_DISK_CACHE_SIZE=100000000000 %command%
I don't remember what the shared memory env var does, but the rest get rid of the constant recompiling of shaders on every launch. (Crashing during comp is very fun without these)
Game ran at 144 fps 1080p even on my old 1060. Can push around 250-270fps on my current 2070 now. LatencyFlex is no longer required on NoVideo cards, as the game (proton?) let's you enable Nvidia Reflex now.
It works without any issues if you use the latest proton GE 8 (8-32). No crashes and no performance issues on my system.
mangohud game-performance %command%
For the people that don't know or are not using CachyOS, the game-performance command it's similar to the Feral's gamemode, so be aware and use whatever the option for your system is.
When using the latest versions of GE 9 (from 25 to 27). The game was crashing a lot for some reason as some people have mentioned. One day the game crashed on every second round i played, it was awful. The errors I was getting were related to "the device has been lost". Changing the Proton GE version to 8 was the solution, I've been playing for a week a couple of matches, and now in the weekend i was able to play for a couple of hours in one sitting and apparently the crashes are gone. So give it a try.
And in regard of using steams proton, it works but I was having fps issues like if the fps were capped, I have 2 monitors both at the same 144hz so it may be related to that but not sure.
gamemoderun __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
Sometimes exits fullscreen by itself midgame
Crashes after 3-4 games. Often due to "rendering device lost". Whole system freezes and requires system reboot, as simply waiting for the freeze to end and relaunching the game makes it blackscreen (only audio works when it freezes)
It definitely requires some tinkering to get it working, but when it does, it runs just fine.
Huge stuttering at startup while compiling shaders, but it usually goes away after 5 min of playing.
Tried through Steam, Lutris and Bottles. So far, the most stable results were with bottles using GE proton, so stay away from competitive play at first to check if everything is stable enough.
On first launch, The game WILL compile shaders on-the-fly. Be prepared for some INSANE stuttering for about 15 minutes!
Models and particles tend to take longer than usual to load, at least on first launch.
From what I can tell, the game does not pre-compile shaders. When you first install the game, stay in Practice Range and wait until they finish compiling. (It took ~15 minutes for my compilation to finish)
Once shader compilation is done, the game will run as it does on Windows (smooth, lag-free)
Although the game still stutters a bit, it's generally playable after this point.
So far, I've had the game crash one time (while it was minimized).
I hope this game gets the ability to pre-compile shaders soon...
deactivate Steam Overlay. runs perfectly fine after. otherwhise it will launch in window mode showing you the cursor at a wrong location always.
Core functionality works just some special functions refuse to work (TTS, Ingame Voicechat, Saving Highlights)
MANGOHUD_CONFIG=“cpu_temp,cpu_power,gpu_temp,gpu_power mangohud %command%
-wih my 5080 it ran like a charm -with my old 1080Ti the game feels laggy (and i switched tmp back to W11) Maybe a problem with the old GPU Architecture
-TTS not working -Exporting game highlights fails with unknown Error 6-04 -Ingame Microphone doesnt get audio
Ran quite well
lag at fist boot
just sit in practice range for a bit (about 5 minutes) until game does not feel laggy
Long time on Vulkan shader building
FPS increased to 90 (with lowest 1080p; on Windows it was below 30). That was last year. But performance degraded now, only go to 80 max, frequently at 45-60.
gamemoderun %command%
Frequent crashes on proton 9 (or proton 9 GE). Framerate locked at 60 on normal proton, even though monitor supports higher. Switching to proton GE fixed this.
Runs well enough
Prebuilding shader cache doesnt finish. Noticable lags the first few minutes playing a map for the first time while shader cache is seemingly being built in realtime.
SDL_VIDEODRIVER=x11
Issus with pointer capturing with both fullscreen and borderless window.
Using SDL_VIDEODRIVER=x11 and gamescope --force-grab-pointer fixed the issue for the most part. Still comes up every so often, but clicking back into the window fixes it. Only happened for me when using extra monitors.
Performance is pretty bad for the first few minutes of playing. Load up the training room for like 5-10 minutes and the issue goes away on its own.
Damned thing eats all ram, something related to shaders, and DirectX. Launching vai Sarek-Async resolved the ram gluttony.
protonsarek async
Crashed entire system, ate all my ram
gamescope -w 1920 -h 1080 -W 1920 -H 1080 -b -r 144 -- %command%
Just need to tinker with Proton version and gamescope settings in launch options.
Use LD_PRELOAD launch option and turn off Steam Overlay for all games via steam preferences to avoid stuttering after ~30min.
LD_PRELOAD="" PROTON_USE_XALIA=0 %command%
After playing for ~30 minutes (around 2 games) there would be horrible stuttering when moving the mouse. Standing still and killcams had no issues.
Initial load time is somewhat slow
Sporadic crashes. Ranges from several within a few days to weeks without any.
Runs beautifully. Average frametimes between 0.8 - 2 ms. Individual frametimes rarely exceed 8ms.
__GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 LD_PRELOAD="" MANGOHUD_CONFIGFILE="$HOME/.config/MangoHud/wine-Overwatch.conf" mangohud obs-gamecapture %command%
Very few competitive shooters allow Linux. I'm really happy my favorite does.
gamemoderun %command%
It works smoothly some of the time, and has major FPS drops that make the game unplayable at other times.
gamemode %command%
You just have to load shaders in practice range for like 3 minutes then its done, i always get a stable framerate.
mangohud %command%
The steps thats I ran on my Debian SID: 1. Enable i386 arch: dpkg --add-architecture i386; 2. Configure winehq (from official site) and install with recommends: apt install --install-recommends winehq-staging; 3. Install the following drivers/packages: apt install vulkan-tools vulkan-validationlayers mesa-utils mesa-opencl-icd mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers steam-devices mangohud; 4. Finally the steam itself (downloading from official site): dpkg -i steam_latest.deb.
severe lags at the beginning of the game, then a little bit better, but still impossible to play
PULSE_LATENCY_MSEC=60 %command%
w/o launch options
this is in steam version mouse problems and dropframes problems
on wayland when game fullscreen somethimes it makes the mouse out of the game i mean you cannot press anything in the game with the mouse i think this is solveable by using proton-ge and removing the $DISPLAY envronment to enable wayland driver
on wayland when game fullscreen somethimes it makes the mouse out of the game i mean you cannot press anything in the game with the mouse i think this is solveable by using proton-ge and removing the $DISPLAY envronment to enable wayland driver
fps is so low and the alot of drops even when joining the same maps a cuple of times
In the first minute some heroes take a bit to appear. But when you leave spawn everything is fixed. Nothing that makes it unplayable.
During the first minute it is a bit slow, but before you leave spawn it's fixed
Occassionally wipes out the graphics driver and takes half the system with it. Haven't personally bothered to investigate why though there are plenty of tinker suggestions below you can try.
The game installs and runs, but ever since the latest update, it will invariably crash 25-30 min into a session.
LD_PRELOAD="" LFX=1 gamemoderun %command% PROTON_USE_XALIA=0 %command%
Crashes
At a time when the game needs all the players they can get, the new instability is deeply disappointing. Even with the suggested flags, the game crashes. Enabling or disabling pre-caching does nothing, absolutely zero.
Other people will say that they used a specific proton version, but again, this does not matter. I've tried rolling back 2-3 versions as well as using experimental. The issue is systemic and will spawn a zombie process on your PC that can't be killed without a reboot.
Sometimes Alt-Tabbing will leave a dropdown menu at the top left that can only be removed if you right click on a cinnamon program like on the Nemo file manager's title bar.
Go to the practice range first to check your frame rate. It'll probably be low but if you wait a bit for your shaders to compile (about 3 minutes), the frame rate will go up by like 300%.
Sometimes the game wont capture my mouse and if i click it click on the windows below the game. Just a restart fix it
Game runs almost at max setting (1440p 60fps) (no fsr)
NVidia reflex will crash the game after a game. Using ProtonGE make it ok to use NVidia Reflex without any issues
I recommend after adding specific launch options, installing GameMode and switching Proton
LD_PRELOAD="" LFX=1 gamemoderun %command% PROTON_USE_XALIA=0 %command%
After about 30 minutes of gameplay, game started to extremely stutter
Extreme stuttering
Game works fine out of the box, no issues or glitches, but if you want to play without problem for longer then ~30 minutes, you'll have to install GameMode (wiki.archlinux.org/title/GameMode) and add your user to "gamemode" group, set launch options and switch Proton version to 9.0-4. In my case, switching it boosted overall performance.
After that steps I have very stable and responsive gameplay.
MANGOHUD=1 __GL_SHADER_DISK_CACHE=1 __GL_SHADER_DISK_CACHE_SIZE=100000000000 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 __GL_SHADER_DISK_CACHE_PATH=/home/david/.cache/games/ow2 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia DXVK_HUD=compiler %command%
The cursor doesn't align with the UI when the in-game resolution doesn't match the monitor's.
After certain conditions, the camera might move to point upwards. This happens seemingly randomly (a one-time thing after switching a character), and also during tasks such as re-plugging a mouse (moves the camera upwards periodically until the game is restarted).
Shaders re-compile on each game boot without downloading pre-cached shaders or explicitly setting shader cache environment variables.
Works with no major issues most of the time. Always make sure you're playing at your monitor's native resolution, minimise any external factors that might trigger a bug which points your in-game camera upwards, and download pre-cached shaders or set shader cache environment variables if necessary.
