Do not confuse anti-cheat runtimes with Proton#64
Open
PaletzTheWise wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
I ran into an issue where anti-cheat runtimes, whose names start with "Proton " (BattlEye and EasyAntiCheat), were being confused with actual Proton and their identified version happened to be the highest among Proton candidates.
This led to a failure of lens-server.exe, since these runtimes do not contain Proton, and I would get the error message
or
I tried uninstalling EasyAntiCheat in Steam but nothing happened. So I tried moving its folder away from ~/.local/share/Steam/steamapps/common/ and that did the trick. Then BattlEye became the preferred candidate, so I moved it too. This workaround fixed the issue but it would likely resurface later since I do need those runtimes for the multiplayer games that use them.
Therefore, I have undone the workaround, confirmed the issue is back and made the code change to remove any candidate that contains "Runtime", which fixed the issue again. (Note: These are, in fact, the first four lines of rust I have ever written.)
I used Santeri's instructions (https://github.com/santeri3700/vive-pro-2-on-linux/blob/master/STEAMVR.md) to deploy the driver both with and without the fix.