add fix for Gray Zone Warfare EAC hash errors after subseqent launches#537
Open
ProjectSynchro wants to merge 1 commit into
Open
add fix for Gray Zone Warfare EAC hash errors after subseqent launches#537ProjectSynchro wants to merge 1 commit into
ProjectSynchro wants to merge 1 commit into
Conversation
Set cache files to read-only to prevent the game from modifying them after first launch, which invalidates Easy Anti-Cheat hashes.
ProjectSynchro
changed the title
Contributor
Author
|
Looks like CI failed due to another issue unrelated to this change. |
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
1 participant
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.
For some reason when you launch the game under Proton these two cache files are either changed or regenerated in some way which causes EAC to boot you from the game after subsequent launches.
0xaf497c273f87b6e4_0x7a22fc105639587d.dat0xb9af63cee2e43b6c_0x3cb3b3354fb31606.datThe best way to get around this is to set those two files as read only so the game won't invalidate it's own EAC hashes.
I have manually applied this fix for the last few patches and the filenames haven't changed.
Obviously this is a symptom of some syscall not behaving as expected or being implemented incorrectly on the Wine side of things but this should resolve the issue until that is either looked into or resolved.