[Solved] Overwatch exits during gameplay

I’m not familiar with PopOS, but I know it’s Ubuntu-based. glibc version you can check with “ldd --version” in the terminal. That wine tkg release was compiled against glibc 2.32, therefore if your version is lower (likely 2.31 or perhaps even lower) it’s not going to run and you’d have to either compile it from source against your system’s own glibc or update the library, if such update is available. The most recent version is 2.33, but I don’t know how long for does PopOS hold package versions back. Ubuntu 20.10 has version 2.32 available though and the latest PopOS version is based on that, unless you’re running the LTS release, which would make it 20.04 and therefore 2.31.

The package name should be libc6, but I haven’t worked with apt-based distributions for a while (running an Arch-based server and Fedora-based desktop), so I’m not aware of current Ubuntu dependency hell.

Yeah, I’m using 20.04 LTS and seems it has 2.31


This one seems to be the last version precompiled against 2.31, you could try that. Building wine-tkg from source can be a mess if errors pop up, so wouldn’t recommend it (but you can try if you’d want to).

That doesn’t launch either. I’m starting to think I might just be stuck until the next more official update comes out to fix it :c

Bad news. 5.22-tkg crashes randomly as well.

@MoonBurst I had also a kinda similar problem to yours. My game did not run with latest Lutris DXVK 1.81L. I was messing around with the Wine Prefix because of this crashing issue and while I was doing that I probably messed up something in it that caused this. I moved my game folder to somewhere else and run the Overwatch install script from Lutris again to create a fresh Prefix after that I moved back and verified my game files. Now DXVK 1.8.1L works perfectly maybe same thing can work for you.

Also Wine-tkg dev compiles them on Arch Linux so if you want to use his binaries you have to be on a rolling distro to get the same libraries as the dev (preferably something Arch based) if not you have to compile them yourself or find someone that compiled it on the same Ubuntu base as yours. Compiling Wine shouldn’t take too long on a modern system, so I suggest you to give it a try.

@Synthkrieg Lutris Wine 5.7-11 it is then. Performance hit aside the game is very playable for me at least. Voice com also works too.

@Synthkrieg I have yet to experience a 5.22-tkg crash :thinking:

UPDATE: YUP, 5.22-tgk also crashes RIP

Wine-tgk can’t be compiled on the OpenSUSE Tumbleweed rolling distro. Instead do the following:

  1. Download the *tar.zst of the build you want
  2. Extract it
  3. Cut and paste everything in the “usr” folder into the root folder and delete the now empty “usr” folder.
  4. Rename the wine folder to remove the “-x86_64.pkg” at the end of the folder name
  5. Cut and paste the wine folder to your “lutris/runners/wine/” directory
  6. Run Lutris and click on the “Manage Wine Versions” button and you should see your newly listed runner.
  7. Change Overwatch’s runner to that runner and everything should be fine.

Downloading and running a prebuilt binary can also result in library incompatibilities. The issue you have linked is from a PKGBUILD which is Arch’s build system.
https://github.com/Frogging-Family/wine-tkg-git/tree/master/wine-tkg-git You should follow these instead. If you have installed all the build dependencies it should compile just like normal Wine.

@Awsim Please see this comment. Yes, it technically can be compiled on Tumbleweed, but the resulting Wine build will not run. This issue goes back to 2019 and the repo owner has stated “For some reason wine built on Debian/buntu works everywhere, but when you build it on other distros it’s hit or miss. Seems to be a miss for OpenSuse TW

Also, if “Downloading and running a prebuilt binary can also result in library incompatibilities.” as you say, wouldn’t any prebuilt lutris-wine binaries have this same issue?

That’s the thing about modified Wine, it’s black magic. Mainline Wine I can compile wherever, it works. Modified wine in my personal experience mostly just doesn’t. When I tried to compile 6.8-tkg before the COPR maintainer published a working build it just segfaulted on me mid-build. Not a dependency issue, just a “lol no, the end”.

As for the OW issue, I’ve noticed that whenever the crash occurs, it’s always along with some action happening ingame. Once it crashed on me when I was hit by a Doomfist, once it was during an intense teamfight, etc. It’s always some sound or perhaps shaders, something happening. I mean I haven’t tested running it idle for hours and the crashing does occur seemingly entirely on random, but it’s a correlation.

Also played for over 2 hours on 6.8-tkg yesterday without a hitch. Whatever it is, it’s beyond me.

@Asudem thanks for the heads up I get it now.

@Synthkrieg I once got a crash during the end game stats screen and also during the main menu but I can’t confirm the main menu one because I left the game on for like 1 hour at the main menu and when I came back the game was gone. Since I didn’t see that personally I can’t confirm it but worth mentioning.

Also I got a play session for around 2-3 with 6.8 tkg but the thing crashed the other day. I don’t think 6.8 tkg delays the crash. We are just lucky to trigger it late.

Can anyone make sense of the coredumps or the game crash logs (if it generates one, I don’t think it does generate in this case). Or maybe Wine logs or DXVK logs? I didn’t find anything useful out of mine.

Hey, I am on Manajro. OW is crashing for me as well. I didn’t even play the game. I was in queue for quick play. I had Second crash in middle of fight. I am newbie. I can help but just tell me where to grab logs or some useful information. I am running OW on lutris 6.4

          PID: 38787 (Overwatch.exe)
           UID: 1000 (ondra)
           GID: 1000 (ondra)
        Signal: 11 (SEGV)
     Timestamp: Mon 2021-05-17 20:19:57 CEST (11min ago)
  Command Line: C:/Overwatch/_retail_/Overwatch.exe -uid prometheus
    Executable: /home/ondra/.local/share/lutris/runners/wine/lutris-6.4-x86_64/bin/wine64-preloader
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-net.lutris.Lutris-ee2864b9703b4d39b4f0956c67ad8e22.scope
          Unit: user@1000.service
     User Unit: app-net.lutris.Lutris-ee2864b9703b4d39b4f0956c67ad8e22.scope
         Slice: user-1000.slice
     Owner UID: 1000 (ondra)
       Boot ID: 4d8359570a95497ba0292e9d41dc7884
    Machine ID: 559db0a997684a01bcb72ebd1eb5d07a
      Hostname: ondra-pc
       Storage: /var/lib/systemd/coredump/core.Overwatch\x2eexe.1000.4d8359570a95497ba0292e9d41dc7884.38787.1621275597000000.zst (truncated)
       Message: Process 38787 (Overwatch.exe) of user 1000 dumped core.
                
                Stack trace of thread 38882:
                #0  0x00007f38b415e2bf n/a (n/a + 0x0)
                #1  0x0000000000000000 n/a (n/a + 0x0)
Refusing to dump core to tty (use shell redirection or specify --output).

Game froze on me after around 20 minutes in the menus.

Has anyone seen any issues of this brought to developers anywhere on any WINE repos? I guess technically since we have no information to report with the issue there’s nothing they could theoretically work on. I realize the Lutris forms are a peer support group, so no devs are going to see what we post here. I just feel like we’re all staring at the same brick wall with no idea how to progress.

I switched to the following and have played for upwards of 12 hours without a crash. It took some work to get it to set up, since it didn’t want to reinitialize right away, but these settings aren’t crashing for me. But have some minor performance hits, still very playable.
DXVK 1.8.1L
Lutris Wine 5.7-11

Anyone here survive the massive ban sweep?

I’m perma banned. :c send help. My appeal is sent out, but I’m very concerned.

Me too. I had a feeling this was the case. Ugh.

To be honest, I’m glad I’m not the only one. Hopefully there’s enough that they take notice and fix it.

:grimacing: Not entirely sure they’d do that but here’s my 0.01% chance of hope…