Search Issue Tracker
Fixed in 1.7.0
Votes
0
Found in [Package]
1.6.1
Issue ID
1296401
Regression
Yes
Oculus XR plugin on Apple M1 chip crashes editor
Adding the Oculus XR Plugin 1.6.0 or higher to a project will crash the editor while adding the package when running on a M1 based Mac.
A similar crash occurs when importing the Oculus integration asset.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 1.7.0):
The Mac audio spatializer library currently uses instructions that Rosetta 2 does not support on M1 based Macs. Until this is resolved, we're removing the Mac spatializer library. On non-M1 based Macs, you can get the spatializer library from the Oculus integration asset.
If you currently have a project that isn't loading because of this issue, you can manually remove/update the Oculus XR Plugin in Packages/manifest.json. If you have the Oculus integration asset installed, you might need to remove the AudioPluginOculusSpatializer.bundle from your Oculus assets folder.
This workaround is in place in the 1.7.0 of the Oculus XR Plugin.
An updated plugin which solves the issue is included in 1.10.0 of the Oculus XR Plugin.