-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
[Bug] Ark crashes after a fixed time in the menu after patching #1
Comments
That is very very strange. Could you post the crash log when the patch is removed? |
How can I grab the crash log ? |
Just the log at the bottom of the patcher window. |
and
|
hmmm, after removing patch and re-applying to get that log it no longer crashes. |
Glad to hear it! I'm going to close this issue for now, if you or someone else runs into this issue again please leave a comment. |
Sorry for commenting on a closed issue, but since I found that I'm facing an extremely similar issue as this. And thank you for creating this patch to let ARK runs under ARM macOS, even though this is not a popular gaming platform. In my case, the ARK crashing behavior just looks the same as the one shown in the above recording. The game boots up, plays music and crashes after a few seconds. Also, the time it takes to crash also seems to be the same always. I have tried to verify the game file with Steam, and repatch "ShooterGame.app", but it hasn't made any change. Here below is my patching log(Intel mode):
MacOS crash report: Environment: |
So, prior to patching, the game always crashed as I expect.
After the patch though, the game boots up, plays music and crashes after a few seconds. It seems the time it takes to crash is always the same.
Here's a screen recording of that in action:
crash.mov
And here's a crash dump from the console app:
https://paste.sangelo.space/opifisufep.pl
I don't know weather this is due to the patcher or my M1 mac. I've tried both the Intel and the NVIDIA options.
I am running this on a 2020 13" MacBook Pro
The text was updated successfully, but these errors were encountered: