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.

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

Minecraft don't working on Apple silicon (M1) #604

Open
MrDogPL opened this issue Sep 10, 2021 · 7 comments
Open

Minecraft don't working on Apple silicon (M1) #604

MrDogPL opened this issue Sep 10, 2021 · 7 comments
Labels
wontfix This will not be worked on

Comments

@MrDogPL
Copy link

MrDogPL commented Sep 10, 2021

The game crashes at random time error code: 0. (I know that Minecraft works on roseta, but I guess you can fix it) Os: macos big sur 11.5.2

@kyleplo
Copy link

kyleplo commented Sep 22, 2021

I'm not sure if this is possible, since this project depends on the fact that Minecraft is already compiled for Intel processors as some Android devices have Intel processors, while there are no Android devices that use Apple Silicon processors, so Minecraft has not been compiled for them. It may be possible with Rosetta though.

@ChristopherHX
Copy link
Member

since this project depends on the fact that Minecraft is already compiled for Intel processors

No. Linux arm32/64 works and has even less bugs in Minecraft 1.17.

Apple silicon is not emulatable, while linux / windows arm64 is.
I need access to a m1 mac (remote CI is probably enough) or there will be no progress.

@ChristopherHX ChristopherHX added the wontfix This will not be worked on label Oct 24, 2021
@moskadev
Copy link

moskadev commented Oct 25, 2021

@ChristopherHX Do you need someone to help you with your testing? I'm getting my new Mac tomorrow under their SoC. This would be a great advance for many users

@ChristopherHX
Copy link
Member

@moskadev

Do you need someone to help you with your testing?

Yes, but this launcher is potentially far far away from working on m1 so it would need much help and a lot of testing.

I have no idea how apple new security model of m1 behaves, it far more hardend than x86_64. I would need to experiment on actual hardware.

It is confirmed to work under rosetta 2.

  • The first step is to mmap an android shared library, this doesn't work at all.
    • mcpelauncher-linker panics due to an error of the mmap call
  • Would the android code run or does the process panic?
    • x86_64 panics once the fs register is accessed by the android stack protector => this launcher replaces the call
  • apple/m1 no executable and writeable pages at least not at the same time, need to patch the linker to switch between write,noexec and exec
    • restrictions to game modding
  • Do we need codesigning to gain code generation entitlement? I read something about this

@ghost ghost mentioned this issue Feb 5, 2022
@CasperOng
Copy link

The problem also occur in M2, M1 Max and M1 Ultra. I didn't test anything about M1 Pro but I guess the problem still happened.

@gopipolsani
Copy link

gopipolsani commented Dec 19, 2022

For me on M2 MacBook Pro 13 inch with MacOS Ventura it works flawlessly under rosseta 2. But it hogs a lot of battery since its running under rosetta, is there any native Apple Silicon support?

@iMonZ
Copy link

iMonZ commented Oct 24, 2023

Hey any news here? Would like to uninstall Rosetta 2?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

7 participants