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

Apple Silicon and macOS 12+ Compatibility #3

Open
sambilbow opened this issue Dec 10, 2022 · 2 comments · May be fixed by #4
Open

Apple Silicon and macOS 12+ Compatibility #3

sambilbow opened this issue Dec 10, 2022 · 2 comments · May be fixed by #4

Comments

@sambilbow
Copy link

sambilbow commented Dec 10, 2022

  • The plugin isn't compatible with M1/2 Silicon architecture.
  • The LeapMotion controller isn't compatible out-of-the-box with macOS Monterey and higher.

I've submitted a PR: #4 with added instructions to the README.md for those coming to this package with the above devices/OS. I will include them below too, just in case the PR doesn't get merged.

macOS users on Monterey (macOS 12) or higher EXPERIMENTAL

Follow these archived instructions to get the LeapSDK to recognise their device. Included below for ease:

  1. Connect the LMC to the Mac
  2. Open the "Recalibrate Device" window, and leave it open
  3. Reboot your Mac
  4. LMC should now show as connected!

macOS users with Apple Silicon CPUs EXPERIMENTAL

Run Max 8 using the Rosetta Translation Environment.

@sambilbow sambilbow linked a pull request Dec 10, 2022 that will close this issue
@ivan-ef
Copy link

ivan-ef commented Aug 3, 2023

New SDK for m1 is released. Any plans for update?

@JulesFrancoise
Copy link
Owner

Hello,

Unfortunately, I don't use the Leap Motion anymore, and I do not have access to a M1 machine to do the upgrade.
Feel free to open a pull request with an update, or to contact me if you wish to take over maintenance.

Best,
Jules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants