Quoting: sonic2kk

Quoting: FesiugAh.. I see. What I seem to remember, then, is dxvk_async being removed from Proton-GE? Is that still the case?

I believe so, but this has nothing to do with GE-Proton. This downloads the DXVK DLLs and native shared library files, like the kind you would download directly from the DXVK repository. This is not Proton.

The previous dxvk_async is incompatible with DXVK v2.1 and above, so I believe the patches were removed from GE-Proton since they cannot be used by default (unless you manually download DXVK). And this newer dxvk_async which is compatible with DXVK v2.1 and above, technically called dxvk_gplasync, is not included in GE-Proton as far as I know, as per the dxvk_gplasync maintainers note on the ProtonUp-Qt GitHub issue I linked [External Link] (as of October 10th 2023):

> Getting this patch to GE-proton is possibility, but i am in GE discord server and people don't seem to care about this.

I skimmed the changelog for GE-Proton releases since then, and I didn't see mention of re-adding DXVK Async. It may be included, but last I heard, dxvk_gplasync is not in GE-Proton.

And just to reiterate, all of these projects are technically separate from Proton. DXVK is a standalone project that is often used with Wine builds and thus also Proton, but can be used natively (DXVK Native, used by Valve in place of ToGL for Portal and Portal 2 with the '-gamepadui' launch option). If you want to use dxvk_gplasync with a given Wine build that doesn't include it you can install it manually into the prefix *or* into the default_pfx for Proton builds. Lutris and Heroic also allow you to manually select DXVK (and vkd3d-proton) versions.

And also, in case you're looking and see older builds, it's called GE-Proton now.

Quoting: sonic2kk

Quoting: Fesiugdxvk_async? when was that readded? was it? what's up?

Nothing was re-added, nothing was removed to begin with. ProtonUp-Qt always allowed you to download dxvk_async for Lutris, however it now uses the updated fork that is compatible with DXVK 2.1 and above. When DXVK 2.1 introduced Graphics Pipeline (or "GPL") it broke compatibility with the old dxvk_async.

There is a separate dxvk_async fork maintained by someone else that is compatible with newer DXVK versions. ProtonUp-Qt previously used the older version, which is no longer maintained and was superceded by a new dxvk_async fork.

This is specific to DXVK and is not included with Proton, however ProtonUp-Qt allows you to install this DXVK version for use with Lutris and Heroic, which allow you to manually select DXVK version overrides (Lutris temporarily overwrites the D3D DLLs in the Proton version files to accomplish this iirc, since it cannot modify the prefix as it will get overwritten by the DLLs included in Proton).

This isn't included in any Proton version, this is specifically to allow you to download an up-to-date dxvk_async project for use with Lutris and Heroic.

See DavidoTek/ProtonUp-Qt#243 [External Link] for background.

Quoting: PyreticA lot of the comments are talking about the back button not being fixed. Does anyone care to enlighten me about what they're talking about?

Quoting: Guest

Quoting: Sakuretsu

When you play games with anti-cheat regardless of the support status on Steam Deck and desktop Linux, there's always the chance even if you're a legitimate player that you'll somehow get caught up in a ban wave after doing nothing wrong. False positives are a thing that just happens — sadly. Linux isn't alone is this, various games on Windows over the years have had the same issue it just comes with the territory of online gaming.

Good thing I'm not playing that kinda game anymore.

Losing your account with all the things you spent time and maybe even real money on out of the blue without even doing anything wrong looks absolutely unacceptable to me.

Basically... this.

In reality, VAC is even scarier because other than the VAC stain staying on the profile for 7 years (or forever, I don't remember) on the profile, the entire inventory for the game becomes untradable. However, it's a much weaker form of anticheat and I haven't heard false positives arising, like, ever.

However, peppering up existing anticheat like EA does is just absurd.