Overwatch 2 (2357570)

[EpicureanGit]

Compatibility Report

• Name of the game with compatibility issues: Overwatch 2
• Steam AppID of the game: 2357570

System Information

• GPU: GTX 1070
• Video driver version: NVIDIA 535.86.05
• Kernel version: 5.15.117
• Link to full system information report as Gist: https://gist.github.com/EpicureanGit/3137a7fda8170b704776e289ea523c6d
• Steam Runtime System Information: https://gist.github.com/EpicureanGit/c10f83c76b8926c13e12189903836bbf
• Proton version: 1692281858 experimental-8.0-20230817

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Proton_LOG=1 https://gist.github.com/EpicureanGit/17ffca725b311bd1f78cb621c47e6efe

Symptoms

My cursor doesn't align with the interface after lowering my in-game resolution from my native 4K resolution. Under my native resolution the cursor aligns with the light gray highlighted "2560 X 1440 (60)*" resolution option.

After I changed my monitor resolution to "1920 x 1080 (60)" I had to move my cursor to the left and up in order to highlight the "2880 x 1620 (60)" resolution option.

Reproduction

In-game go to the lower right, select Menu, go to Options, and then go to Video. Then while using fullscreen display mode lower your resolution from your native resolution and apply the new settings.

[boniek83]

I have a problem with game not registering input from mouse. From keyboard only ESC key works - nothing else. Tried Proton 8.0-3, Experimental and Hotfix - all the same behaviour. Sometimes it works though and I have no idea why.

Performance is way lower than on Windows - on Linux I'm geting only around 80-90 fps on 6800 xt.

[Wemmy0]

Performance is pretty good for me. I'm at around 144 fps at 1440p with FSR 2.2 and it looks great. (3060ti, 3700x)

Only issues for me:

• Game can flicker the alt+tabbing or in the gnome activity view
• Cursor sometimes not displaying but still being able to select items (usually fixed by going into esc menu and back out)
• Random FPS lag down to ~70 FPS for like 1 second (very rarely happens)
• Voice chat didn't work for me but started working with the latest Proton GE
• Unable to export highlights or POTGs as video files (even with proton GE)
  • Finished when exporting as webm format but resulted in a corrupted file that can't be played

[polluxau]

idk why this hasnt been reported yet but using either proton experimental (bleeding edge) or proton 8.0-4 the fps is stuck at 40fps but with proton-ge-8-16 the fps is fine

[polluxau]

as you can see here the fps is good here with proton-ge
running fedora 39 beta with kde plasma with mesa 23.2.1

[boniek83]

I have a problem with game not registering input from mouse. From keyboard only ESC key works - nothing else. Tried Proton 8.0-3, Experimental and Hotfix - all the same behaviour. Sometimes it works though and I have no idea why.

Performance is way lower than on Windows - on Linux I'm geting only around 80-90 fps on 6800 xt.

Don't have input problem anymore, but performance is still below expectations with stock proton (only about 90-100 fps on 6800xt radv 23.2.1).

[foresto]

Has anyone managed to get valid .webm saved highlights?

I can see the CPU doing work while the video is encoded, but the resulting files are only ~770KiB. They won't play in any player, and mediainfo says they are only 1ms long.

[agurenko]

@foresto it used to work, but I also tried recently and also got 770 kb broken file

[boniek83]

I have a problem with game not registering input from mouse. From keyboard only ESC key works - nothing else. Tried Proton 8.0-3, Experimental and Hotfix - all the same behaviour. Sometimes it works though and I have no idea why.
Performance is way lower than on Windows - on Linux I'm geting only around 80-90 fps on 6800 xt.

Don't have input problem anymore, but performance is still below expectations with stock proton (only about 90-100 fps on 6800xt radv 23.2.1).

Performance is within expectations on proton-ge 23 (maybe it worked in earlier versions - didn't test), so that's what I'm using now. I have no more problems.

[SopaDeMacaco-UmaDelicia]

The mouse sens via proton is way off from windows. It's sad that valve doesn't invest in input consistency of games played via proton. Vanilla proton doesn't even support raw imput, my KDE mouse sens impacts in-game sens, which is not right. Proton GE fixes that, but the sens is still off from that on windows.

[polluxau]

The mouse sens via proton is way off from windows. It's sad that valve doesn't invest in input consistency of games played via proton. Vanilla proton doesn't even support raw imput, my KDE mouse sens impacts in-game sens, which is not right. Proton GE fixes that, but the sens is still off from that on windows.

X11 or wayland?

[SopaDeMacaco-UmaDelicia]

The mouse sens via proton is way off from windows. It's sad that valve doesn't invest in input consistency of games played via proton. Vanilla proton doesn't even support raw imput, my KDE mouse sens impacts in-game sens, which is not right. Proton GE fixes that, but the sens is still off from that on windows.

X11 or wayland?

KDE Wayland

[polluxau]

The mouse sens via proton is way off from windows. It's sad that valve doesn't invest in input consistency of games played via proton. Vanilla proton doesn't even support raw imput, my KDE mouse sens impacts in-game sens, which is not right. Proton GE fixes that, but the sens is still off from that on windows.

X11 or wayland?

KDE Wayland

If you try x11 its way better

On kde plasma 6 dev they changed how it works under wayland and its a lot better aswell

[SopaDeMacaco-UmaDelicia]

If you try x11 its way better

On kde plasma 6 dev they changed how it works under wayland and its a lot better aswell

Well, in my opinion games like Overwatch 2 and Apex Legends that support raw mouse input should behave the same everywhere no matter what OS or DE you use. The only way it to be better is to be 1:1 compared to windows with no interference from the system settings. And input inconsistency won't attract FPS enthusiasts to Linux.

[polluxau]

If you try x11 its way better

On kde plasma 6 dev they changed how it works under wayland and its a lot better aswell

Well, in my opinion games like Overwatch 2 and Apex Legends that support raw mouse input should behave the same everywhere no matter what OS or DE you use. The only way it to be better is to be 1:1 compared to windows with no interference from the system settings. And input inconsistency won't attract FPS enthusiasts to Linux.

Yes i agree, i play competitive fps games and i am masters in apex, masters on overwatch

Whenever i want the closest mouse input i use x11 or now im using kde plasma 6 wayland, i can easily keep up with my friends who are gm in overwatch and i got a 4k badge today on the new mouse input under plasma 6 wayland on apex. i guess i prefer mouse input on x11 or kdes new approach for mouse input on wayland under plasma 6

[AMDHome]

Has anyone managed to get valid .webm saved highlights?

I can see the CPU doing work while the video is encoded, but the resulting files are only ~770KiB. They won't play in any player, and mediainfo says they are only 1ms long.

Its an overwatch issue. Not a proton issue. webm doesnt work on windows natively

[foresto]

webm doesnt work on windows natively

In that case, has anyone managed to get valid .mp4 saved highlights?

[3DMicks]

Is the game really supposed to be using 10GB+ of RAM? After the game loads initially, it uses ~5GB but after the "Compiling shaders" step finishes, it sits at least above 11GB of RAM.
The game itself is playable (with a performance hit) before this, so I can't imagine it being correct behavior.
I vaguely remember this not being an issue a couple of months ago. I tested Proton 8, Experimental, GE and TKG.

INFO:
Steam Flatpak
Kernel: 6.6.10-arch1-1
DE: KDE Plasma 5.27.10
WM: KWin (Wayland), X11 is the same
NVIDIA: 545.29.06

[SopaDeMacaco-UmaDelicia]

Htop shows 4720MB reserved, max settings, FSR2.2 to 4k max quality. Arch, KDE Wayland, Mesa RADV.

[3DMicks]

Here are some screenshots of how it behaves:

Right after loading the game, the game does actually use 5GB, but I forgot to screenshot the exact moment

Compiling Shaders

Finished compiling shaders

In the middle of a match (Suravasa)

After the match

After closing the game, it takes a while for it to fully exit; longer sessions do end up using a little more memory. The game also does this with swap if you don't have enough memory, in this test it used no swap.

Forgot to mention in the last post that I am using __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 and an NVIDIA Prime system.

Edit: Just checked, and the env var for skipping cleanup does not make a difference; it still behaves the same with and without it.

[Michele1144]

Is the game really supposed to be using 10GB+ of RAM? After the game loads initially, it uses ~5GB but after the "Compiling shaders" step finishes, it sits at least above 11GB of RAM. The game itself is playable (with a performance hit) before this, so I can't imagine it being correct behavior. I vaguely remember this not being an issue a couple of months ago. I tested Proton 8, Experimental, GE and TKG.

INFO: Steam Flatpak Kernel: 6.6.10-arch1-1 DE: KDE Plasma 5.27.10 WM: KWin (Wayland), X11 is the same NVIDIA: 545.29.06

I have the same issue, using Proton Experimental, Proton-GE and Proton 8. On htop "Overwatch.exe" uses 5 GB when opening the game but then after a couple of minutes it drops even under 10 MB, while the memory is in reality being clogged out (using around 20 GB+ being the only open app, 2 GB used on idle) making the game going 2 FPS and the system totally unstable, with difficulties to close the game too. Right now is unplayable. Also, during the brief time of normal usage, Proton-GE achieves 120 FPS+ with no problems while Proton Experimental and Proton 8 are stuck on 20 FPS with the exact settings.

GPU: NVIDIA GTX 1660 Super with 545.29 driver
RAM: 8 GB + 16 GB swap
OS: Fedora Workstation 39 using X11 with GNOME 45
Kernel: 6.6.9
Steam RPM

[3DMicks]

Replying to #7033 (comment)

I can confirm that I also experience a brief period where it hits high frame rates before plummeting down to around 50% of the expected FPS, not thermal or map-related.

Regarding the 20 FPS I can also confirm that, depending on the Proton version, the game gets locked at around 44–47 FPS for me, with the only fix being to delete the prefix. Switching versions also causes this problem. One way I replicated this issue was to use Experimental/GE and then switch to Proton 8.

Another issue I experience is extremely high CPU usage when moving the mouse if I have a high polling rate. With 1000 Hz I get ~35% less FPS, with 500 Hz ~12% less, and with 250 Hz I see almost no difference.

[3DMicks]

Since "Compiling Shaders" appears for the entire period where the RAM usage increases I tested the game without GPL by using DXVK_CONFIG="dxvk.enableGraphicsPipelineLibrary = False" as an environment variable and the RAM issue was mostly gone. Stutters get predictably worse.

Without GPL, the game starts at around 2.5 GB of RAM and increases after playing some matches to around 4.8 GB. The mouse polling rate issue persists.
Since this could be an DXVK issue, I'll try to make an issue on their repo when I can if this isn't Proton/Wine related.

Also, the game's PROTON_LOG=1 are hundreds of megabytes (370 MB at 15 minutes of play) due to a spam that goes like this:
warn:seh:dispatch_exception unknown exception (code=6ba) raised 5 times, then
warn:seh:dispatch_exception EXCEPTION_PRIV_INSTRUCTION exception (code=c0000096) raised once, then
warn:seh:dispatch_exception EXCEPTION_SINGLE_STEP exception (code=80000004) raised ~140k times, then finally
warn:seh:dispatch_exception EXCEPTION_ILLEGAL_INSTRUCTION exception (code=c000001d) raised when I close the game.

Another issue I have is that, sometimes, when the mouse cursor is unlocked (hero selection, pinging, emoting, etc.) the moment it locks again my aim moves all the way up or down, meaning I can't use voice lines in the middle of a fight without the fear of getting completely lost.

[3DMicks]

Replying to #7033 (comment)

I just tested GE-Proton 8-27, 25, 20, 15, 10, 5, and TKG, and they all have the same problems. I also tested GE-Proton 7-55, but the game didn't launch because it couldn't detect Steam.

Given how all of these versions have the same issues, I suspect it was probably a game update that causes them.

[TerohsLab]

After the Wine 9 rebalance of Proton Experimental the game looses window focus after a match and you can't regain it. I can load up the game fine, play a game normally and on the play of the game screen the game just looses focus on its own with no way to get it back.

Proton Experimental was working totally fine before the rebase to wine 9.

I feel like we had a similar problem in the past .. maybe a game specific patch got missed in the rebase?

Still works as expected under Proton 8.

Am using the steam version of the game.

[kisak-valve]

Hello @TerohsLab, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[simifor]

@TerohsLab I played a quickmatch in proton experimental and couldn't reproduce your focus loss issue, does it only happen with specific game modes?

[agurenko]

@TerohsLab I've been playing OW2 with Proton 9 beta and experimental for 4 days now without any difference to previous experimental.

[TerohsLab]

Yeah i can't reproduce it currently. Played 10 quickplay games with logging turned on and it didn't reoccur.

I swear it happened multiple times ( in comp tho ) and through restarts .. and it felt like the same bug that we had before .. the one where would loose window focus on hero death from like 2 years ago.

Hopefully it was just some hickup in Tumbleweed. Once i can nail it down more i will report back.

@kisak-valve https://gist.github.com/TerohsLab/f3a5e1391899eec510909b07a78390fe in case it will become relevant later.

[Etmix]

Replying to #7033 (comment)

You probably need to add the LD_PRELOAD="" fix (add LD_PRELOAD="" to the beginning of your launch params).
Sounds like this problem: ValveSoftware/steam-for-linux#11446

I have to add this to every game at the moment or I get the stuttering after 25 minutes of gameplay.

[CuteSkyler]

I've been experiencing large amounts of shader compilation during gameplay. It will happen randomly/when models are being loaded in. Usually happens when starting the game up anew, loading new characters in, loading new maps in. After having everything load in and compile shaders, the game runs flawlessly. This is including the fact that it "compiles shaders" before boot up, according to Steam.

My current mess of parameters is: DXVK_ASYNC=1 __GL_SHADER_DISK_CACHE=1 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 __GL_SHADER_DISK_CACHE_SIZE=1000000000 LD_PRELOAD="" PROTON_USE_XALIA=0 LFX=1 DXVK_HUD=compiler __GL_SHADER_DISK_CACHE_PATH=/home/user/.steam/debian-installation/steamapps/shadercache/2357570 gamemoderun %command%

Also using Proton GE, it supposedly solved this issue (it did not).
Linux 6.11.0-19, Ubuntu 24.04, Ryzen 9 5950X, RX 7800XT

[waywardfrantz]

Replying to #7033 (comment)

Considering those of us without those parameters are not having this problem, you should probably try removing them.

[CuteSkyler]

Considering those of us without those parameters are not having this problem, you should probably try removing them.

I added the parameters specifically because I had the shader compilation problems, removing them won't solve the issue. I've had it on NVIDIA and AMD cards. Maybe it's a distro issue?

[TerohsLab]

I've noticed similar stuff on a up to date Tumbleweed KDE with 570 nvidia drivers and proton experimental. I only use the LD_PRELOAD="" and not this wall of text as parameters.

Basically download the 16gb shader precache, let steam cook the shaders in the background, launch the game and the first 2-3 matches still stutter while loading new textures. Even with wild pop in's from stuff like my weapon models and stuff.

After those first few matches its fine for hours until i restart the game.

It reminds me of that DXVK bug we had like 2 years ago where it would precache invalid shaders and would override them everytime no matter what.

Found the bug report : https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton7-47

[CuteSkyler]

The current launch-option setup I use is LD_PRELOAD="" DXVK_HUD=compiler gamemoderun %command%, (DXVK_HUD=compiler is for personal preference) based on the advice I got. At first this did nothing to alleviate the issue, but after removing the~/.steam/debian-installation/shadercache/2357570/ folder, it never tried compiling shaders again (in-game or on bootup) and it now runs flawlessly. Maybe because of leftover NVIDIA driver compatability from before I switched GPUs?
Running GE-Proton9-25, Ubuntu 24.04, RX7800XT, Ryzen 5950X

[TerohsLab]

Maybe because of leftover NVIDIA driver compatability from before I switched GPUs?

I mean maybe .. if .. looking at your old command line .. you changed some other parameters of your system like this, then .. maybe. But generally no it should not.

Your new command line looks good tho. Could replace the compiler stuff with mangohud and default gamemode does nothing anymore for most games, so could remove that if you run the default config.

Glad its working for you now tho!

[slagiewka]

In order to isolate issues with DXVK/shader cache you might try the DirectX 12 backend in Overwatch. This will run on VKD3D but I'm not sure if the result shader compile pipeline is different.

[E-D-W-I-N]

In order to isolate issues with DXVK/shader cache you might try the DirectX 12 backend in Overwatch. This will run on VKD3D but I'm not sure if the result shader compile pipeline is different.

How can I enable DirectX 12 in Overwatch? I only have DirectX 11 option when I run game inside Proton
Running Overwatch from Windows (via dualboot) gives me DirectX 12 Beta option, but on Linux I have only DirectX 11 in game's settings

Is there any necessary command line stuff?

[CuteSkyler]

How can I enable DirectX 12 in Overwatch? I only have DirectX 11 option when I run game inside Proton Running Overwatch from Windows (via dualboot) gives me DirectX 12 Beta option, but on Linux I have only DirectX 11 in game's settings

Is there any necessary command line stuff?

The option is definitely present on the latest version, using GE and Ubuntu 24.04. I tried it, but the game wouldn't start up again after selecting it so I avoid using it. Maybe use a specific Proton or Linux version, it could be detecting that something in your system isn't DX12 compatible.

[Dhizaes]

In order to isolate issues with DXVK/shader cache you might try the DirectX 12 backend in Overwatch. This will run on VKD3D but I'm not sure if the result shader compile pipeline is different.

How can I enable DirectX 12 in Overwatch? I only have DirectX 11 option when I run game inside Proton Running Overwatch from Windows (via dualboot) gives me DirectX 12 Beta option, but on Linux I have only DirectX 11 in game's settings

Is there any necessary command line stuff?

I don't know if there is a parameter to force it but in the blog it says it is not DirectX 12, it is DirectX 12 Ultimate, which needs a compatible GPU. If your GPU doesn't compatible with that you probably can't see it. I have RTX 3060, I can see the option and it works without any problem. Maybe you can try to set your VKD3D level to 12.2, even I don't think it will help in this situation.

[polluxau]

Replying to #7033 (comment)

yep, only rtx 20 series, rdna2, arc a series or above support ultimate, my mate on windows who has a 1660ti doesn't have the dx12 option but my rx 6700 and rtx 2060 has the option to use it :P

[E-D-W-I-N]

Is anyone else here experiencing issues with the game freezing after last season started?

Like a year ago (#7033 (comment)) , I'm facing game freezing on Proton-Experimental and Proton-9. I'm on Nvidia with 570.133.07 driver

Here's my proton logs from start of the game to game freeze. I closed the game after 2-3 minutes of freeze through Steam "Stop" button in library

steam-2357570.log

[Cantfirmed]

I have the same freezing problem on two new(-ish) full AMD systems (7900 GRE + 7800x3D, and a Notebook with 7745HS). I now restart the game after 3 games, as a precaution. The freeze happens after playing for 1-2 hours and it sometimes takes the full system(KDE Plasma) down, becoming fully unresponsive and I need to restart my system. If it doesn't take the whole system down then it closes the game after ~20 seconds and also causes all other applications I had running (Firefox, Steam, Discord) to crash. Restarting the game afterwards works, but it has to reload all shaders while playing the game, meaning for 10-20 seconds you won't see much ingame.

I am on Arch/CachyOS KDE Plasma + Wayland always with newest drivers.

OpenGL renderer string: AMD Radeon Graphics (radeonsi, phoenix, LLVM 19.1.7, DRM 3.61, 6.14.2-2-cachyos)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.0.3-cachyos1.2

[E-D-W-I-N]

Replying to #7033 (comment)

Try Proton 8, I had no problem since I switched to it. I guess the freezing problem starts from Proton 9 version

[korsilyn]

I have the same freezing issue too, for about 1-2 months, usually when loading into match, can randomly happen after 1 game or after 10 games or not happen at all.
1 times game unfreezed and recovered, but often it's crashing all my system.
I am on Arch + Wayland (tested Sway and Hyprland)
Kernel: Linux 6.14.3-zen1-1-zen (tested 6.13 too)
CPU: AMD Ryzen 5 5600G
GPU: AMD Radeon RX 6700 XT
mesa: 25.0.4
Proton: Proton-GE 9_27
journalctl errors:

Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32797)
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:  in process Overwatch.exe pid 44184 thread dxvk-submit pid 442>
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00000001007a1000 from client 0>
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301431
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x1
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32797)
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:  in process Overwatch.exe pid 44184 thread dxvk-submit pid 442>
Apr 22 16:10:46 castor kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00000001007a1000 from client 0>
Apr 22 16:10:51 castor kernel: retire_capture_urb: 15 callbacks suppressed
Apr 22 16:10:56 castor kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Apr 22 16:10:56 castor kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Apr 22 16:10:56 castor kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=9870196, emitted seq=9870>
Apr 22 16:10:56 castor kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process Overwatch.exe pid 44184 thread dx>
Apr 22 16:10:56 castor kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Apr 22 16:10:56 castor kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset failure

Will try Proton-8, will update after 1-2 days, if it will work.

P.S.: No crashes for 2 days, ofc it may be pure luck
P.P.S.: No crashes for a week, so Proton-8 fixes the problem. Hope to see a solution to this regression in Proton-10, really want to play natively in wayland :(

[simifor]

I managed to get 2 hangs with my rx 6600, on linux 6.14.2, mesa 25.0.3 and proton 9.0-4.
The first one was while loading into a match, this was the second match of the session, and it only affected the game, there was no issue with amdgpu. After that it took about 15 games across two sessions to get another hang, this one was mid-game and it caused a gpu hang

I haven't yet seen this issue happen with proton experimental bleeding edge, but considering the second one took 15 games, it might be down to luck, has anyone tried this version and gotten it to hang?

[Nyamiou]

I confirm I also have the same issue of Overwatch randomly freezing since last season (I'm on Proton Experimental). I initially tough it was my system or Nvidia driver but I stumble into this thread: https://www.reddit.com/r/linux_gaming/comments/1k7e6bj/overwatch_randomly_crashing_fix/ where AMD users are also affected. And then I found this one https://www.reddit.com/r/SteamDeck/comments/1k655np/overwatch_2_season_16_stadium_crashing_aid_for/ where Steam Deck users are also affected and which talk about this thread also: https://steamcommunity.com/app/2357570/discussions/0/598523502186737670/ were multiple Steam Deck users also report the issue. And then I came here obviously. I think there is enough evidence that this is a widespread issue, even if the freezes don't happen very often.

I guess I'll try Proton 8 to see if the issue still happens but that means no Nvidia Reflex (I'm off for a week, so I might only update about this in two weeks).

[E-D-W-I-N]

I guess I'll try Proton 8

You can also try new Proton 10 beta. Yesterday I played for 6 hours without any issues, no freezes, stutters or anything. Feels great. It will be even better with wayland driver enabled and NTSync support, but we have to wait for it a bit longer

[alasky17]

@E-D-W-I-N We also cannot reproduce any freeze/stutter on 10.0... fingers crossed this is fixed! @Nyamiou @korsilyn @Cantfirmed Please let me know if you still see any freeze/stutter on Proton 10?

[TerohsLab]

No blizzard games work anymore on Tumbleweed 20250501 KDE Nvidia 570.144 with current Proton Experimental.

• WoW ( added via other games on steam )
• OW2
• Hearthstone

Proton experimental added wine mono 10 on top of proton 10, which broke all of your shit.

The games work fine on the proton 10 beta and on proton 9 on steam. @alasky17

[korsilyn]

@alasky17 i am currently on proton bleeding-edge (10.0-200), no crashes so far. Looking at patchnotes, this regression also fixed in proton 9.0-rc2, but I'm playing through battlenet, which now works only on Proton 10 (fix in Proton 10-1 beta) so I can't confirm.

[agurenko]

I'm also trying Proton 10 (10c) for the last two days and no crashes so far.

[Cantfirmed]

@alasky17 I have tried it out, and indeed the crashing issue seems to be fixed. Sadly now my fps seems to be locked to <70 fps when I have had 165+ FPS with Proton GE 8.32 (with normal Proton 8.x I couldn't even launch it). I have tried both Proton 10 Beta branch and Proton Experimental Bleeding Edge. With Bleeding Edge I get around 5 FPS more.

[blakkd]

@E-D-W-I-N We also cannot reproduce any freeze/stutter on 10.0... fingers crossed this is fixed! @Nyamiou @korsilyn @Cantfirmed Please let me know if you still see any freeze/stutter on Proton 10?

I personnally, and some others still do on THE FINALS! Seems related to 2 instances of EAC launching instead of 1.
#7317 (comment)

[polluxau]

@alasky17 I have tried it out, and indeed the crashing issue seems to be fixed. Sadly now my fps seems to be locked to <70 fps when I have had 165+ FPS with Proton GE 8.32 (with normal Proton 8.x I couldn't even launch it). I have tried both Proton 10 Beta branch and Proton Experimental Bleeding Edge. With Bleeding Edge I get around 5 FPS more.

Read through this and see if it fixes the problem

#7033 (comment)

#7033 (comment)

[ClayCore]

I can only get the game to launch once every 20 attempts. The Overwatch.exe process seems to die before I even get to see the window spawning.

System information:

• OS: EndeavourOS
• Kernel: 6.14.4-arch1-2
• DE: KDE Plasma
• WM: KWin (X11)
• CPU: Ryzen 7 9800X3D
• GPU: AMD Radeon RX 9070 XT
• Mesa version: 25.0.4-1
• Proton version: from 8.0-5 to experimental, including Proton-GE

Here's my launch parameters:

DXVK_FILTER_DEVICE_NAME="RADV GFX1201" DXVK_LOG_PATH="/home/claymore/.logs/dxvk" DXVK_LOG_LEVEL="warn" DXVK_HUD="pipelines" PROTON_LOG="1" LD_PRELOAD="" %command%

DXVK log is empty, so I'll attach the one from proton

steam-2357570.log

[korsilyn]

@Cantfirmed i had to recreate prefix to fix fps issue, try this
Also, if you want to backup graphics settings, be sure to copy PFX_DIR/drive_c/Users/steamuser/Documents/Overwatch/

[Dhizaes]

@E-D-W-I-N We also cannot reproduce any freeze/stutter on 10.0... fingers crossed this is fixed! @Nyamiou @korsilyn @Cantfirmed Please let me know if you still see any freeze/stutter on Proton 10?

I personnally, and some others still do on THE FINALS! Seems related to 2 instances of EAC launching instead of 1. #7317 (comment)

Really appreciated the thumbs down when I'm trying to help in case you were facing the same issue... Dumbasses

Overwatch 2 doesn't use EAC.