Overwatch 2 rendering device lost

[Timmyz03]

crossover 23.7 + cxpatcher 0.4.9 (for battlenet fix), Macbookpro 16inch M1 Pro

Battle.net works, overwatch opens fine (with the usual 6ish minutes of loading time to get stable fps in menus). however when trying to load into training ground, the game completely freezes (hero selecting works, but trying to actually load into the map breaks), and then crashes with an error saying rendering device lost

ran with dxvk and msync enabled (I tried esync and the same issue persisted)

crossover 23.6 and cxpatcher 0.4.6 worked (I was playing on Nov 30th, before the Battlenet update), not sure exactly what is causing the issue, crossover 23.6-->23.7 or cxpatcher0.4.6-->0.4.9 or battle.net

[Timmyz03]

another detail is that yesterday with crossover 23.7 and cxpatcher 0.4.8, OW2 could work by running through steam, so this issue is likely a battlenet/cxpatcher 0.4.8->0.4.9 issue, but I am not sure

[italomandara]

I'll fix this in the next release, it's because we reverted to an older MoltenVK version to fix some other issues try this: "MVK_CONFIG_RESUME_LOST_DEVICE" = "1" in your bottle's cxbottle.conf

[Timmyz03]

do I put this at the very last line?

edit: Thankyou so much! I just tried it and the game would work now, however there is way more stuttering and flickering that was not present in any previous version (game ran with similar fps as before but there are lag spikes and freezes, along with flickering with map assets, im assuming this would be fixed once the next release with proper moltenvk gets released?

[italomandara]

do I put this at the very last line?

edit: Thankyou so much! I just tried it and the game would work now, however there is way more stuttering and flickering that was not present in any previous version (game ran with similar fps as before but there are lag spikes and freezes, along with flickering with map assets, im assuming this would be fixed once the next release with proper moltenvk gets released?

I will give an option to chose the baseline moltenvk + ue4 patch (the one you have now) and the latest MoltenVK with the latest fixes + ue4 patch

[Timmyz03]

out of complete curiosity (forgive if im asking dumb questions), why both options, wouldn't the latest version (if bug free), always better than older versions? I guess it boils down to how should I determine which version of moltenVK to use for each game

[italomandara]

out of complete curiosity (forgive if im asking dumb questions), why both options, wouldn't the latest version (if bug free), always better than older versions? I guess it boils down to how should I determine which version of moltenVK to use for each game

because isn't been tested enough , it's the very latest changes so it might be unstable, but might also fix lots of bugs

[Timmyz03]

thankyou so much, I truly appreciate your work and help, looking forward to future releases and would update on any bugs I find!!

[Timmyz03]

interestingly, the issue went away today when I retried. and I have 0 idea what might have fixed it, now running crossover 23.7+cxpatcher 0.4.9 straight up works with 0 issues (with no bugs that I could notice). Just thought to update this here

[Gcenx]

https://github.com/italomandara/CXPatcher/releases/tag/V0.4.10