OW 2 on Linux

linuxoverwatch.md

This guide is completely irrelevant! You no longer need to follow anything here—doing so may actually harm performance rather than helping it. Please tell whoever linked you here that they need to maintain their own guide, if they want to help people set up newer versions of DXVK / etc.

⚠️ People on debian (apt) based systems running into the glibc version error and instead of using lutris flatpak wanting to build caffe yourself: don't - See Frogging-Family/wine-tkg-git#773 for details.

edit: i created a caffe build targeting glibc 2.31 - works flawlessly (with fsync disabled)
https://github.com/Inve1951/wine-tkg/actions/runs/3214416798

run ldd --version to see if you can use it

Big problem on the steamdeck/steamOS atm is that DXVK shaders whether async or normal don't save between OW2 Lutris sessions. You will have to go thru the game stuttering like crazy at 10fps every. single. time.

No idea why this happens. Somehow something isn't able to access the cache properly. Permissions issue?

@genericuser001 if you change the DXVK version, it will reset your shader cache. try leaving it as async (make sure you confirm it’s actually working by using the environment variable!). if it still doesn’t work, join the discord and i can help you out there.

very good i love it

I'm on archlinux I downloaded and did every steps but the one that doesn't work is when I put the dxvk-async folder inside the lutris dxvk main folder I still don't get the option to chose the asynx version

"Your rendering device has been lost!"
The hell is this.
Literally no other game does this, i'm so mad because i lost so many games due to this crash.

Is there any way to cache the shaders or anything so that whenever I load the game I don’t have to wait 20 minutes to get to playable framerates? I have esync and fsync disabled already

@ryleu You don't seem to understand. I accept that changing DXVK will reset the cache. That is NOT what is happening here. The shader cache straight up- does not work on OW2. You will go thru the stuttering all over again, on subsequent fresh boots into the game, as 3D elements slowly pop into view, despite your shader cache already sitting in the wine folder.

For whatever reason on Steamdeck- the shader cache for OW2 isn't working right.

@genericuser001 I understand now. We’re currently working on a solution, I’ll make sure to mention you if we get it sorted.

@KNobles It won’t show up in the drop-down, you have to manually paste it in.

@UnfuntionalLadder we’re working on a solution, I’ll let you know once we find one.

@ryleu You don't seem to understand. I accept that changing DXVK will reset the cache. That is NOT what is happening here. The shader cache straight up- does not work on OW2. You will go thru the stuttering all over again, on subsequent fresh boots into the game, as 3D elements slowly pop into view, despite your shader cache already sitting in the wine folder.

For whatever reason on Steamdeck- the shader cache for OW2 isn't working right.

yep, I'm having the same problem on my laptop.

For clarity, this solution doesn't remove the initial cache loading required (13 minutes) when you boot the game, correct? I'm on Steam Deck and every boot requires a long compile session. Thank you!

The caffe runner does not work in Ubuntu 20.04 using the ppa for lutris. I read somewhere about using flatpak but that runs impossibly slow (1 frame per second). Any ideas?

The caffe runner does not work in Ubuntu 20.04 using the ppa for lutris. I read somewhere about using flatpak but that runs impossibly slow (1 frame per second). Any ideas?

For anyone using Ubuntu 20.04, you can download the caffe version built on 20.04 from here.

@darkuni that is correct. it removes the ongoing stutter after the “compiling shaders” message in the bottom left goes away

In summary, if someone got random crashes, you can try to disable both esync and fsync and clear the cache of shaders. In my case it removed all random crash issues. I launched the game for 24 hours and still 0 crashes for a week.

Is there any progress with recompiling shaders issue?

DXVK Async don't work for me

@PoSayDone no, not at the moment. i’m also still working on compiling data for the memory leak issue. things have slowed down quite a bit, and GE and the others still haven’t gotten a chance to look into what’s going on, afaik.

edit: dxvk async doesn’t mean you don’t have to compile shaders. all it does is reduce the performance of compiling shaders while you play.

edit2: i stand corrected. there are people (who are much smarter than me) working on it :)

GE boys are working on it currently. https://www.reddit.com/r/SteamDeck/comments/xxexad/comment/iton0rq/?utm_source=share&utm_medium=web2x&context=3

Oh boy, no way, I'm switching to Windows to play in this time

@Miltonr87 it has been working for a while. the guide is actually fairly straightforward at this point, you only need to download and extract one extra thing.

BTW, this is fixed with GE. Right now, only Wine (Lutris) version is available, but I tested it myself. It works. No shader issues for 13 minutes, no crash. I'm waiting, personally, for the Steam GE Proton version to be released this weekend so I don't have to use Lutris, Bottles or anything other than a simple non-steam game entry.

it has been working for a while. the guide is actually fairly straightforward at this point, you only need to download and extract one extra thing.

Thanx mate!

@darkuni fixed

@Miltonr87 you now pretty much don't have to do anything extra

Is it normal to have cache recompiling each time I start the game? dxvk 2.0 async

Is there something worked on to fix launcher startup to have it launch each time normally?

It seems that async shader compiling do not work with this setup, did it on Bottles and its running much better

I think its not supposed to stutter when async is working, just is to pop the shaded models in the screen instead.
If the message "Compiling shaders" appears on the game, then dxvk-async needs to reinstalled/troubleshooted

@bruwyvn that is correct. You can use the environment variable mentioned in the guide to make sure DXVK Async is working. Make sure you also have DXVK_ASYNC=1