WINE: Wine Is Not an Emulator

API call translation is often very inexpensive and, particularly in the case of DXVK for graphics calls, sometimes actually results in faster code if the underlying API implementation is more performant than the original Win32 equivalent – see Elden Ring launch day performance on Linux vs. Windows for an example of this.

You’re confusing Proton with community efforts like Lutris. Proton is a package of technologies (Wine, DXVK, Vessel), not a configuration manager. Each individual game gets an identical, isolated runtime environment without any bespoke modifications except for downloading precompiled shaders (if available).

It’s certainly true that Proton has hardcoded quirk flags for specific applications, but these are exceptions which prove the rule – there are <200 of these compared with thousands of Verified status games. Almost always, Valve prefers to fix the upstream Wine/DXVK bug rather than hacking around it. Any hacks which Valve does ship are in the Proton source code, not per-game environment scripts.

[…] but that’s more of a commercial benefit I think

For me, this is the primary benefit of a rice cooker. Having warm, cheap, filling food on demand at any time is fantastic. I am so lazy and my little rice buddies are always ready to go when I can’t be bothered.

Unfortunately, kbin instances are unavailable via Lemmy right now due to hosting problems on kbin’s side of the equation (see Kbin Codeberg #101). This will probably be fixed soon, so keep an eye on that issue for progress.

Even if it were working, however, there’s actually something of a required ritual that you’ll need to go through when subscribing to an external community which your instance is not already federated to (i.e.: communities where nobody on SDF is currently subscribed). Here are the steps you’ll need to follow:

1. In the community search, paste in the following pattern: !community@instance.domain (e.g.: !technology@beehaw.org)
2. Press [Enter], wait for the search to finish (it’s normal to see no results)
3. Wait a few minutes
4. Refresh the search page and search for the common name this time (e.g.: “Technology”)
5. The community should appear and be available for subscription now

FWIW: There are plans to improve this unintuitive workflow in the future (see Lemmy Backend Github #2951).

If these steps don’t work, it’s possible that the community may simply be too new. You’ll sometimes need to wait an hour or so after a community has been created for it to start being available on external instances.