Search Issue Tracker
By Design
Unknown (hidden) 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X
Votes
0
Found in
2022.2.0b1
2023.1.0a1
Issue ID
UUM-2495
Regression
No
Crash when generating lighting on Apple Silicon Editor
Reproduction steps:
1. Open the user's attached project
2. Open Window -> Rendering -> Lighting
3. Create new Lighting settings
4. Generate lighting
Expected result: Lightning is generated successfully
Actual result: Crash during lighting generation
Reproducible with: 2021.3.4f1, 2022.1.3f1, 2022.2.0a15
Could not test with: 2020.3.35f1, 2019.4.39f1 (no native Silicon editor)
Reproducible on: MacOS Monterey 12.4 (M1)
Not reproducible on: Windows 10
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note:
There are two different backends for the Lightmapper, one using the CPU and one using the GPU. When creating a new Lighting Settings Asset (or when using the default values) it use the CPU Lightmapper by default, which is incompatible with Apple Silicon.
I have filed a separate bug report for fixing the default LSA on the Apple Silicon architectures to prevent such crashes and issues in the future. Conversely, I will be closing this issue as "By Design", because the CPULM is not supported on Apple Silicon by design.