PlayableShow Details
Unknown
Enable DX12 (beta) in the game options
DXVK_FRAME_RATE=240 DXVK_HUD=compiler LD_PRELOAD="" %command%
The game is incredibly framey when using another or no proton layer. With GE, I was achieving average frames of about 200 with max graphic settings.
Enabling Shader Pre-caching and Background processing of Vulkan shaders in `Steam Settings > Downloads` fixes stutter.
PROTON_USE_NTSYNC=1 STAGING_SHARED_MEMORY=1 __GL_SHADER_DISK_CACHE=1 __GL_SHADER_DISK_CACHE_SIZE=25000000000 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
Runs very smooth most of the time, with occasional but very significant stutters on all runtimes, even on Proton-GE.
Enabling Shader Pre-caching and Background processing of Vulkan shaders in Steam Settings > Downloads fixed the issue.
Very likely a shader compilation problem, even though my hardware should be more than capable.
The launch options are probably not even needed with Shader Pre-caching enabled, but try it out.
DXVK_HUD=compiler %command%
On Proton versions newer than 8.0-5 (incl. GE) the camera flicks directly up or down if the cursor is moving when returning from anything that lets it move freely, e.g. leaving hero select, closing menu or releasing ping wheel.
Stuttering if shaders are not loaded.
The game runs smoothly even on default proton once shaders have been compiled. Switching to 8.0-5 is only required if you are affected/bothered by the specific issue with camera jumping.
SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 SDL_VIDEO_WAYLAND_SCALE_TO_DISPLAY=1 SDL_VIDEO_DRIVER=x11 gamemoderun %command% -novid -nojoy -high -freq 165
The game runs great on CachyOS
DXVK_HUD=compiler %command%
On versions newer than Proton8.0-5 (incl. GE), camera jumps directly up or down if the cursor is moving when returning from anything that allows it to move freely, e.g. leaving hero select, closing menu or releasing ping wheel.
Stuttering if shaders are not loaded.
The game runs smoothly even on default proton if you wait for the shaders to compile. Switching to 8.0-5 is only necessary if you are affected and bothered by the camera jumping issue.
SDL_VIDEODRIVER=x11 __GL_SHADER_DISK_CACHE=1 __GL_SHADER_DISK_CACHE_SIZE=10737418240 %command%
Actual mouse postion was offested compared to cursor. fixed by setting dispaly to windowed borderless
Had to increase disk cache. I recommened playing in training for a few minutes until everything is cached
DirectX 11 roda liso porem com o DirectX 12 roda estremamente mal.
Os primeiros 5 - 10 minutos de jogo vão ser um pouco travados por conta do compilamento/processamento de shaders porem depois disso o jogo vai rodar liso liso.
STAGING_SHARED_MEMORY=1 DXVK_FILTER_DEVICE_NAME="NVIDIA" LD_PRELOAD="" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 DXVK_HUD=compiler __GL_SHADER_DISK_CACHE=1 __GL_SHADER_DISK_CACHE_SIZE=100000000000 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
Launch options + GE 9-27 were mandatory to make the game playable. On other Proton versions, game either does not launch or runs with awful, unplayable frame drops. Game also compiles an absurd amount of shaders, so you'll need 20-30GB extra space just to account fot that.
(Hyprland) Rarely, the cursor goes out of the bounds of the game, but generally locks back into the game after a couple of times leaving the bounds.
Frequent (Once, or more rarely, twice per long gaming session) permanent freeze that requires you to close the game and re-open it.
Other than the bugs I've mentioned, I've had no other issues with OW2 and it runs fantastically, definitely just as enjoyable as on Windows.
The game lags and stutters slightly, fps drops randomly during matches
I didn't encounter any problems and tried the game for the first time, nice game
DXVK_HUD=compiler LD_PRELOAD="" %command%
Stutter, high memory use
Crash due to system running out of memory.
The RAM usage is very high due to shader compilation. (Much lower on Windows) If you are RAM-limited, you might need to increase Swap size, or else your system could crash. Also, let the shaders compile fully before playing, by waiting in the main menu, practice range etc.
DX12 is unstable and slow for me, just use default DX11. The game has a a lot of shader compilation stuttering during the first minutes of gameplay, even some when using shader pre-caching. My "fix" is to go to the practice range and load every hero once while waiting for the matchmaking.
My experience was more stable and smoother with GE-Proton. Normal Proton runs fine too, but aiming for a high framerate in my CPU limited scenario was easier on GE-Proton.
PROTON_USE_NTSYNC=1 DXVK_HUD=compiler __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 __GL_SHADER_DISK_CACHE_SIZE=100000000000 PROTON_ENABLE_WAYLAND=1 nvidia-offload mangohud %command%
cursor lock was intermittent on X
switched to VKD3D (Use DX12 in settings) and nvidia-offload is a nixos command
PROTON_USE_NTSYNC=1 DXVK_HUD=compiler __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 __GL_SHADER_DISK_CACHE_SIZE=100000000000 PROTON_ENABLE_WAYLAND=1 nvidia-offload mangohud %command%
lack of cursor lock on X sometimes
lack of cursor lock on X sometimes
using proton ge prevented freezes and constant shader recompiling
Runs perfect out of the box.
I didnt need to change everythink, no bugs, no crashes, nothing. Runs just like on Windows with the default proton-cachyos, maybe even better. I played on High Settings with 1440P@240Hz.
Well, if you're experiencing crashes, I’m here to tell you that the solution is finally here. I’ve tested several different distros to see if the game would stop crashing, but I never had any success — until now. I saw a lot of people talking about the dark side of CachyOS, so I decided to try it out and see what the fuss was about. And since it’s based on Arch, I got even more excited — because Arch is life.
Long story short, my Overwatch is now running beautifully, just like it should. I’m using CachyOS’s Proton, with no startup commands. After the shaders finish loading, the game runs smoothly and looks amazing.
gamemoderun %command%
Ás vezes não salva a configurações
Reduzir a resolução resolveu o problema
Jogável
PROTON_ENABLE_WAYLAND=1 DXVK_HUD=compiler __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 mangohud gamemoderun %command%
use Directx 12 not Directx 11
Works great
Overall fun game.
LD_PRELOAD="" gamescope -W 2560 -H 1440 --backend wayland --adaptive-sync --hdr-enabled --force-grab-cursor -f -- env LD_PRELOAD="" gamemoderun %command%
For a few seconds the game has fps drops while processing shaders
The game runs fine with just proton, i use gamescope mainly for the hdr and less fps drops, you need --force-grab-cursor with gamescope or you wont be able to use emotes and voice lines.
Works great on both Proton Experimental and GE Proton 10-4. Steam Overlay and Steam Game Recording doesn't work.
Steam Overlay doesn't work. Steam Game Recording doesn't work.
No gameplay issues or performance degredation. Steam Overlay and Game Recording doesn't seem to work for me, no matter what I try, but my most of my friends say it works for them.
Almost perfect
Slowness on startup, play a warmup game before ranked, or jump into a custom game, for a few mins
no issues except for the first 10 minutes of game (don't play ranked first!) you can see some lags during the first 10 minutes of gameplay.
with vanilla proton i've encountered some issues with framerate. you can do better with DLSS or fsr, but i noted that GE-Proton works way flawlessly.
DXVK_HUD=compiler __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
The game stutters a lot while compiling shaders
I had to set __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 into launch option to avoid cleanup of shader cache. I needed to wait some time compiling shaders so that the game became playable, and when restarting the game, I didn't have to wait some minutes to play an match properly.
PULSE_LATENCY_MSEC=60 %command%
Start command fixes this
Without tinklering sound would be corrupted
gamemoderun gamescope -f -W 1920 -H 1080 -r 60 -- %command%
En X funciona sin problemas en la mayoría de casos, no se tiene que hacer mucha cosa, pero, si pasaste de jugar en X a Wayland, deberías de comprobar que corra de forma nativa en Wayland y no en XWayland, podrías estar jugando con XWayland y aunque no sea notorio para algunos, en competitivo afecta. Busca información sobre tus problemas de latencia e intenta aplicar todo lo mejor posible, investiga muy bien y podrás disfrutar mejor tus juegos; si eres muy casual, sólo te recomiendo usar gamemode.
Game runs great on the latest GE. I would advise turning on Vsync and Reduce Buffering for a more responsive gameplay.
No need for tinkering, game works fine, no bugs, nor graphical issues.
Using another resolution rather than the native one might result in the buttons not being able to be pressed with the mouse , can fix using game scope Ex: gamescope -W 1280 -H 720 -r 75 -- %command%
FPS might start dropping after playing ~1hr
Game starts with Built in Steam Proton 10 Beta but haven't tested gameplay
PROTON_ENABLE_WAYLAND=1 %COMMAND%
Low framerate when using default Proton. By switching to GE-Proton and DirectX12 the game runs at full performance without any frame drops nor crashes.
perfectly enjoyable experience that runs straight from the get go.
DXVK_HUD=compiler __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
sometimes the audio is a bit weird, but manually changing the output device from "automatic" to my headphones fixes that
The game runs as it should, but its heavy on shader resources, taking additoinaly 25GB storage space and up to a few minutes of your precious time compiling them when you start the game on a fresh boot. The launch options mentioned above are for a little indicater showing the compiling process while in game and for skipping the clean up, that way you only have to do that every reboot. The game stutters during the compiling process. I just open up the practice range and let it do its work until its fluent. After that everything works fine.
