-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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] Fire Emblem Engage crashes on macOS Silicon #4548
Comments
Could you please add the current Ryujinx version at the time you compiled your build? |
I removed the mods in order to see if it was a romfs mod issue but nah, literally the same error. |
Does it happen on #4480 ? |
I just tried to compile your PR (testing on arm64 and it provided only x64 bin) and I got a different exception this time with FE Engage
|
That means the app doesn't have the hypervisor entitlement, you probably didn't compile it properly and the signing step failed for some reason. |
I compiled it with the very same method as I used for the main branch... that's odd |
As gdkchan suggested, it's an issue related to the hypervisor entitlement, since it seems to be an issue related to the user I close it. |
I'm running into this too on current master. I compiled as per the README, with |
My build log:
|
If you just want to build it to play games, you can use the build script inside the Personally I just I never had entitlement issues with either method. |
Thank you! :] |
Description of the issue
Fire Emblem Engage 1.X.0 crashes with the app built from source code. Downloading the prebuilt version works instead. Tested without any mods/save/shaders (literally clean) and it still crashes (it had all correct keys and firmware installed)
Reproduction steps
Build from source code, install it as you are supposed to do, try to open the game.
Log file
Crash log when loading romfs mods
OS
macOS 13.2.1
Ryujinx version
1.1.1
Game version
1.X.0
CPU
M1 Pro
GPU
M1 Pro
RAM
16GB
List of applied mods
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered: