Proton
Proton copied to clipboard
ValveSoftware
Overwatch 2 (2357570)
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:
- [x] that I haven't found an existing compatibility report for this game.
- [x] 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.
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.
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
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
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
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).
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.
@foresto it used to work, but I also tried recently and also got 770 kb broken file
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.
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.
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?
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
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
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.
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
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
webm doesnt work on windows natively
In that case, has anyone managed to get valid .mp4 saved highlights?
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
Htop shows 4720MB reserved, max settings, FSR2.2 to 4k max quality. Arch, KDE Wayland, Mesa RADV.
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.
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
Replying to https://github.com/ValveSoftware/Proton/issues/7033#issuecomment-1890753226
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.
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.
Replying to https://github.com/ValveSoftware/Proton/issues/7033#issuecomment-1901743831
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.
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.
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.
@TerohsLab I played a quickmatch in proton experimental and couldn't reproduce your focus loss issue, does it only happen with specific game modes?
@TerohsLab I've been playing OW2 with Proton 9 beta and experimental for 4 days now without any difference to previous experimental.
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.
i see that with the latest proton experimental(bleeding edge) the fps is back to normal on mesa 24 under arch,
let me know if anyone else is also getting normal fps without using proton-ge under an amd card on latest mesa with latest proton experimental(bleeding edge)
Got the crash on camera : Uploading steam-2357570.zip…
https://filetransfer.io/data-package/FHUFZDHH#link