Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Overwatch 2 (2357570) #7033

Open
2 tasks done
EpicureanGit opened this issue Aug 21, 2023 · 151 comments
Open
2 tasks done

Overwatch 2 (2357570) #7033

EpicureanGit opened this issue Aug 21, 2023 · 151 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues

Comments

@EpicureanGit
Copy link

EpicureanGit commented Aug 21, 2023 •
edited by kisak-valve
Loading

Compatibility Report

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

System Information

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.
4K Overwatch 2

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.
1080p Overwatch 2

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.
@kisak-valve kisak-valve added the Game compatibility - Unofficial Games not expected to work without issues label Aug 21, 2023
@boniek83
Copy link

boniek83 commented Aug 24, 2023 •
edited
Loading

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
Copy link

Wemmy0 commented Aug 25, 2023 •
edited
Loading

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
Copy link

polluxau commented Oct 8, 2023

Screenshot_20231009_104621
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
Copy link

polluxau commented Oct 8, 2023 •
edited
Loading

Screenshot_20231009_104826
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
Copy link

boniek83 commented Oct 19, 2023 •
edited
Loading

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
Copy link

foresto commented Nov 13, 2023

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
Copy link

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

@boniek83
Copy link

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
Copy link

SopaDeMacaco-UmaDelicia commented Nov 19, 2023 •
edited
Loading

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
Copy link

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
Copy link

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
Copy link

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
Copy link

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
Copy link

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
Copy link

AMDHome commented Dec 31, 2023

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
Copy link

foresto commented Dec 31, 2023

webm doesnt work on windows natively

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

@3DMicks
Copy link

3DMicks commented Jan 9, 2024

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
Copy link

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

@3DMicks
Copy link

3DMicks commented Jan 10, 2024 •
edited
Loading

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
Screenshot_20240110_100939
Compiling Shaders
Screenshot_20240110_101038
Finished compiling shaders
Screenshot_20240110_101649
In the middle of a match (Suravasa)
Screenshot_20240110_102415-mm
After the match
Screenshot_20240110_103048-mf

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
Copy link

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
Copy link

3DMicks commented Jan 18, 2024 •
edited by kisak-valve
Loading

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
Copy link

3DMicks commented Jan 20, 2024

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
Copy link

3DMicks commented Jan 22, 2024

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.

@ZeusThundr ZeusThundr mentioned this issue Jan 28, 2024
Open
@TerohsLab
Copy link

TerohsLab commented Mar 2, 2024 •
edited
Loading

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
Copy link
Member

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
Copy link

simifor commented Mar 2, 2024

@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
Copy link

agurenko commented Mar 2, 2024

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

@TerohsLab
Copy link

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.

@kisak-valve kisak-valve mentioned this issue Oct 10, 2024
Closed
@rexpulli
Copy link

rexpulli commented Nov 8, 2024 •
edited
Loading

I've recently encountered a new issue: after about 15 to 20 minutes a few games or map changes the game begins stuttering. The frame drops are severe enough to make the game unplayable. What's unique about this issue is that it's tied to input events from both mouse and keyboard (so it's not fixed by reducing the mouse polling rate for example).
The frame rate only drops when the mouse is moved or any button or key is pressed, it's otherwise perfectly stable and as high as it always has been on my setup. I've tried Proton 9.0-3, ProtonGE 9.18 and Proton Experimental, clearing the prefix and the shader cache.
The only solution right now is to restart the game, but the issue always comes up again.

System information
Log for Proton 9.0-3

In this thread, two other users have reported the same issue on different hardware, distributions and desktop environments, however they ran into it 20 days ago while I'm certain I didn't until today.

EDIT:

I also tried:

  • Rolling back all system packages to a date I know the game worked
  • Re-installing (not verifying) the game
  • Running the game as new user, so a new Steam installation with default settings
  • Disabled the new Steam Recording feature, Shader Pre-Caching, Steam Input and Steam Overlay

Finally, I added the Battle.net launcher as a Non-Steam game and ran the game from there with Proton 9.0-3 and it works fine. So whatever the issue is, it's specific to the Steam version of the client.

@polluxau
Copy link

polluxau commented Nov 8, 2024 •
edited
Loading

well guess it gives me a reason to play ow lol, ill see if i get the same issue

edit: so far no issues

arch, rx 6700, proton experimental,

@rexpulli
Copy link

It appears the issue is not specific to Overwatch 2, other games are affected too. It's being tracked here: ValveSoftware/steam-for-linux#11446. In the mean time, clearing LD_PRELOAD solves the issue.

@Ciberbago
Copy link

Ciberbago commented Nov 29, 2024 •
edited by kisak-valve
Loading

Replying to #7033 (comment)

I need to confirm for other people, this turned out to be a problem with my desktop environment window manager, in this case, mutter from GNOME. And it was fixed in a very recent update. I updated all my system and it just works fine now. I send video proving it:
Working now!

So this was never a problem with proton, steam or overwatch. This was happening in other games too.

@aleex5
Copy link

aleex5 commented Nov 29, 2024 •
edited
Loading

currently in the game it is not possible to reduce the screen resolution because the mouse position not coincides with the one used in the game, hopefully at some point it will be solved, it would be useful to be able to reduce a little the resolution of the game.

@polluxau polluxau mentioned this issue Dec 8, 2024
Closed
2 tasks
@kisak-valve
Copy link
Member

Overwatch 2 (2357570)

Issue transferred from #8301.
@Mx-Angel posted on 2024-12-08T15:27:33:

Compatibility Report

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

System Information

  • GPU: RX 7800XT
  • Video driver version: Mesa 24.3.1-arch1.2
  • Kernel version: 6.6.63-1-lts
  • Link to full system information report as Gist:
  • Proton version: Proton-Experimental

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: steam-2357570-OW2.log

Symptoms

Whilst playing Overwatch 2 if I tab out and try and watch a video or any stream, then the audio for both programs will start to stutter, and my PC will start to stutter as well. Slowing down until nothing moves, I can't open or close anything or make any movements, then it finally crashes. After it crashes I recognize that all my network devices are disconnected and get reconnected quickly after. This also occurs if you never tab out but play around 5 games.

Reproduction

  1. Set Overwatch 2 to use proton experimental
  2. Start game
  3. Try to queue for a match
  4. Whilst queuing tab out the game and start watching video content (either Youtube or a Discord stream should work)
  5. (Can also happen on home screen or in game, I found it mostly happened during queue)

@polluxau commented on 2024-12-08T16:05:06:

Please move your report to this one, as this will count as a duplicate and will be closed, thank you

#7033

@polluxau
Copy link

polluxau commented Dec 8, 2024

Question have you tried using a newer kernel instead?

@Mx-Angel
Copy link

Mx-Angel commented Dec 8, 2024 •
edited
Loading

I haven't tried it yet, but I followed advice from this thread ValveSoftware/steam-for-linux#11446 (comment) in short to set LD_PRELOAD="" in the launch settings for each game then it should stop the issue of constant crashes and audio glitches that I mentioned (#7033 (comment)). It appears to be a problem with the new steam recording feature though I don't understand the specifics.

Edit: After the update on 10/12/2024 it seemed to come back and I have fully disabled steam game recording but kept the launch command

Note: This is currently just a workaround

Edit 2: This workaround appears to have stopped working, at least for myself and may no longer be reliable

@Jafner
Copy link

Jafner commented Dec 11, 2024

Has anyone else encountered trouble with Overwatch 2 fullscreen since yesterday's Season 14 patch?

My symptoms:

  • In the settings under Video -> Video -> GPU, I have my (one and only) GPU listed twice. Once as AMD RADEON RX 7900 XTX and again as AMD RADEON RX 7900 XTX (RADV NAVI31)*. It defaults to the former and changing to the latter doesn't "stick" upon game restart (supposed to apply on restart).
  • The "Windowed" and "Borderless Windowed" display modes do not offer any resolution options.
  • The "Fullscreen" display mode (my preferred), is meant to offer dropdown selectors for "Display", "Resolution", and "Aspect ratio", the first two of which are broken in some way:
    1. "Display" has only one option; "Best Match".
    2. "Resolution" has no options.
  • When in fullscreen mode, my cursor is offset (visual vs. effective) in a way that feels like it's scaling a 1080p window to a 1440p display. Smaller disparity near the top-left, greater disparity near the bottom-right.

I don't think this is caused by Proton, since the issue presents the same regardless of whether I'm using Proton9-3, GE-Proton9-20, Proton Hotfix, Proton Experimental, or Proton8-5.

@simifor
Copy link

simifor commented Dec 11, 2024

@Jafner Doesn't happen on my machine, my gpu is listed once, resolution list is populated, and display has a "display 1". Borderless and windowed indeed do not have a resolution list, but I think this is intended and was that way before this update.
The cursor offset can be manually reproduced by setting a lower than native resolution, so the game might be running at the wrong resolution (and then you are unable to change this as you get no options in the resolution dropdown).

Run the game with the following launch parameter:PROTON_LOG=1 %command%, navigate to the graphics settings and then close the game, this will create the file steam-2357570.log in your home folder. Upload this file, it might give us some more information about what's going wrong.

@Jafner
Copy link

Jafner commented Dec 11, 2024 •
edited by kisak-valve
Loading

Note that despite my uncommon setup, I was not seeing any issues before yesterday's patch. Ran like native.

My Steam systeminfo: 

Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: PRIME X470-PRO
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 5700X 8-Core Processor
CPU Family: 0x19
CPU Model: 0x21
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 4865 MHz
16 logical processors
8 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
BMI1: Supported
BMI2: Supported
F16C: Supported
FMA: Supported
Operating System Version:
"NixOS 24.11 (Vicuna)" (64 bit)
Kernel Name: Linux
Kernel Version: 6.11.10
X Server Vendor: The X.Org Foundation
X Server Release: 12401004
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20241024.105847
Client Information:
Version: 1733265492
Browser GPU Acceleration Status: Enabled
Browser Canvas: Enabled
Browser Canvas out-of-process rasterization: Enabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Enabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Enabled
Browser Rasterization: Enabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Enabled
Browser Video Encode: Disabled
Browser Vulkan: Disabled
Browser WebGL: Enabled
Browser WebGL2: Enabled
Browser WebGPU: Disabled
Browser WebNN: Disabled
Video Card:
Driver: AMD AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 18.1.8, DRM 3.59, 6.11.10)
Driver Version: 4.6 (Compatibility Profile) Mesa 24.2.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 239 Hz
VendorID: 0x1002
DeviceID: 0x744c
Revision Not Detected
Number of Monitors: 3
Number of Logical Video Cards: 1
Primary Display Resolution: 2560 x 1440
Desktop Resolution: 7680 x 1440
Primary Display Size: 23.50" x 13.23" (26.97" diag), 59.7cm x 33.6cm (68.5cm diag)
Primary VRAM: 24576 MB
Sound card:
Audio device: ATI R6xx HDMI
Memory:
RAM: 32000 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 952340 MB
Largest Free Hard Disk Block: 488790 MB
Storage:
Number of SSDs: 2
SSD sizes: 0B,0B
Number of HDDs: 0
Number of removable drives: 0

steam-2357570.log

@Jafner
Copy link

Jafner commented Dec 11, 2024

Searching for the string err in that file reveals several lines seemingly related to failing to get X display information.

51033.987:00e4:00e8:err:xrandr:xrandr14_get_adapters Failed to get adapters
51034.013:00e4:00e8:err:xrandr:xrandr14_get_adapters Failed to get adapters
51056.601:0148:014c:err:xrandr:xrandr14_get_adapters Failed to get adapters
51117.581:0148:014c:err:x11drv:xinerama_get_fullscreen_monitors Failed to get xinerama fullscreen monitor indices.
51117.581:0148:014c:err:x11drv:update_net_wm_fullscreen_monitors Failed to find xinerama monitors at (-32000,-32000)-(-31840,-31976)

@simifor
Copy link

simifor commented Dec 11, 2024 via email

@Jafner
Copy link

Jafner commented Dec 11, 2024

With Proton Experimental:

steam-2357570.log

@simifor
Copy link

simifor commented Dec 11, 2024 via email

@Jafner
Copy link

Jafner commented Dec 12, 2024 •
edited
Loading

Great intuition. I disabled amdvlk (in NixOS via hardware.amdgpu.amdvlk.enable = false;) and ran Overwatch.

It correctly detected only the radv GPU device (AMD RADEON RX 7900 XTX (RADV NAVI31)*) and all fullscreen options worked as expected. Back in business.

Edit: It's worth noting that simply prepending the AMD_VULKAN_ICD="RADV" variable to my game launch options did not prevent the game from seeing both devices.

@Mx-Angel
Copy link

Mx-Angel commented Dec 14, 2024 •
edited
Loading

Replying to #7033 (comment)

This issue I mentioned here has reappeared and I'm not sure why. I had my system monitor up and slowly saw the memory go up to max before starting to stutter and crash. The log file is given below:
steam-2357570.log

Will try the newest kernel and see if there is any difference

Using the newest kernel (6.12.4) the same think happens except now I have constant stuttering and when it maxes out memory it immediately crashes instead of slowly dying. I will stick with the lts kernel for now and see if I can find anything else. This is the log for it:
steam-2357570(stable+9-0-4).log

Edit: It appears to be a memory leak or possibly a race condition (poking into the dark here). I forgot I hadn't updated in a week and decided to do so and that seems to fix the issue, not sure exactly what was causing the issue.

@matthoward123
Copy link

matthoward123 commented Dec 19, 2024 •
edited
Loading

So I cannot run this game without it crashing, most of the time those crashes freezing up my entire pc and I end up needing to hard power off my whole computer. It works for a couple games at least in debug mode, but I can't run it on steam normally without it crashing and I have to reboot. I can't even run PROTON_LOG=1 in launch options, the game won't start up. What commands do I need to run to get help troubleshooting? I'm still quite new to this, so I apologize for providing so little information up front. Just tell me what you need and I'll provide it. I'm on EndeavourOS.

@Mx-Angel
Copy link

Don't worry I am very new to all this as well (on that note if you think I am giving wrong advice correct me and I will fix my messages)

First always check that everything is updated, as that fixed my issue originally.

A proton log would be good, but if you can't even get that working, the issues may be somewhere else. Still I would try disable the screen recording:

To disable it globally

  1. Open Steam
  2. Go to the top right to Steam
  3. Steam > Settings > Game Recording > Recording Off

Per game

  1. Open Steam
  2. Go to game
  3. Settings > Game Recording > Background Recording > Disabled

Set Launch commands

  1. Open Steam
  2. Go to game
  3. Settings > General > Launch Options > PROTON_LOG="1" LD_PRELOAD="" [any extras you may have]

Try launch the game and see if a log appears in ~ and send the .log file

If this fails, I would try run steam from the command line and see if anything pops up immediately, if nothing happens then try run a game and see what error appears and try store it in a file and send it here if there is an issue.

If there are still no problems then I would check dmesg after boot to see there aren't any issues with the kernel.

Otherwise I am not to sure and it may be up to someone more experienced to give better advice. Good luck though.

@simifor
Copy link

simifor commented Dec 19, 2024 via email

@matthoward123
Copy link

matthoward123 commented Dec 19, 2024 •
edited
Loading

Output for uname -a

Linux ephraimsstick 6.12.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 09 Dec 2024 14:31:57 +0000 x86_64 GNU/Linux

Output for inxi -Ga

Graphics:
Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: Micro-Star MSI
driver: i915 v: kernel alternate: xe arch: Gen-12.1 process: Intel 10nm
built: 2020-21 ports: active: HDMI-A-1,eDP-1 empty: none bus-ID: 00:02.0
chip-ID: 8086:9a68 class-ID: 0300
Device-2: NVIDIA GA107M [GeForce RTX 3050 Mobile] vendor: Micro-Star MSI
driver: nvidia v: 565.77 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-09; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
lanes: 8 link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:25a2
class-ID: 0302
Device-3: Bison HD Webcam driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-10:3 chip-ID: 5986:211b
class-ID: 0e02
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.4
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia dri: iris
gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 75 s-size: 1301x366mm (51.22x14.41")
s-diag: 1352mm (53.21")
Monitor-1: HDMI-A-1 mapped: HDMI-1-1 pos: primary,right model: HP VH240a
serial: 6CM0340877 built: 2020 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
Monitor-2: eDP-1 mapped: eDP-1-1 pos: left model: ChiMei InnoLux 0x1521
built: 2020 res: 1920x1080 hz: 144 dpi: 142 gamma: 1.2
size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9
modes: 1920x1080
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland
API: OpenGL v: 4.6.0 vendor: nvidia v: 565.77 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2
memory: 3.91 GiB
API: Vulkan v: 1.4.303 layers: 5 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 3050 Laptop GPU driver: N/A device-ID: 10de:25a2
surfaces: xcb,xlib

@matthoward123
Copy link

matthoward123 commented Dec 19, 2024 •
edited
Loading

Here's my steam log
steam-2357570.log

Correct me if I'm wrong, but it seems like "Overwatch_loader.dll" is the thing that is the problem. Something missing or not working.

@simifor
Copy link

simifor commented Dec 21, 2024

@matthoward123 first I would try to verify the game files, if it still crashes after that, try to change your launch parameters to this PROTON_DISABLE_NVAPI=1 %command%

@matthoward123
Copy link

@matthoward123 first I would try to verify the game files, if it still crashes after that, try to change your launch parameters to this PROTON_DISABLE_NVAPI=1 %command%

I verified my game files and used the launch parameter requested, and the game still crashed.

@matthoward123
Copy link

@matthoward123 first I would try to verify the game files, if it still crashes after that, try to change your launch parameters to this PROTON_DISABLE_NVAPI=1 %command%

I verified my game files and used the launch parameter requested, and the game still crashed.

Any other ideas? I have a console so it's not urgent necessarily, but playing on pc would be vastly preferred so I'm hoping to figure out what's going on.

@matthoward123
Copy link

UPDATE: I've had to hard reboot my system twice now when testing OW2, and when I ran journalctl -k -b -1 for both times I discovered that it crashed because:
Out of memory: Killed process 3827 (Overwatch.exe) total-vm:20556556kB, anon-rss:12037260kB, file-rss:166320kB, shmem-rss:139156kB, UID:1000 pgtables:26192kB oom_score_adj:200
I'm also seeing a lot of messages after that about "split lock detection"
I've tried finding other posts about this but it doesn't seem like an definitive solutions have been found that I can duplicate. Does anyone know how to deal with this memory issue?

@simifor
Copy link

simifor commented Dec 26, 2024 via email

@matthoward123
Copy link

matthoward123 commented Dec 26, 2024 •
edited by kisak-valve
Loading

Replying to #7033 (comment)

Do you mean tweaking settings in-game? I am unable to do that because the game will crash just when I'm looking at in-game video settings for only seconds. I don't understand how the game is using up so much ram when I'm not even playing, how do I fix this out of game, since I can't do it in-game?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Game compatibility - Unofficial Games not expected to work without issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests