Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RA3 binaries are not the same (binary incompatible) #33

Open
zokker13 opened this issue Feb 22, 2018 · 0 comments
Open

RA3 binaries are not the same (binary incompatible) #33

zokker13 opened this issue Feb 22, 2018 · 0 comments
Assignees
@zokker13
Labels
bug

Comments

@zokker13
Copy link
Owner

Seems like the ra3 versions for at least RA3 native and origin are different.

The native (from the CD):

λ sha512sum.exe ra3_1.12.game
8df67e5abb95b2066c9e4cbf63c5574af6bb348874bb4c962c6925cd2d82d391f93b7d45cb3365797dd8e8965a894e41a3a74db36cd8e3cf077825fe96d785af *ra3_1.12.game

The origin:

λ sha512sum.exe ra3_1.12.game
1b7218fc20db8d8fe6884ebac0c900cdcdb496b059d4d643e611817415bcba2dbc350ace57252c387b88b65cef5015c1d7f6dad035aa72b4948a603403838a84 *ra3_1.12.game

This means all memory sensitive data needs to be distinct.
Best to find the process at runtime and fingerprint it somehow and use that fingerprint as base to work.
@zokker13 zokker13 added the bug label Feb 22, 2018
@zokker13 zokker13 self-assigned this Feb 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zokker13 zokker13

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zokker13