Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.37f1
2022.3.23f1
Issue ID
UUM-69548
Regression
Yes
“Unable to fall back to CPU lightmapper.” errors in the Console when opening a project on a Virtual Machine
Reproduction steps:
1. Setup an Apple Silicon VM environment and open it
2. Create a new project from a template
3. Observe the Console window
Expected result: A project is created without errors
Actual result: “Failed to find a suitable OpenCL device, baking cannot use GPU lightmapper.” and “Unable to fall back to CPU lightmapper.” errors in the console
Reproducible with: 2021.3.37f1, 2022.3.18f1, 2022.3.23f1
Not reproducible with: 2022.3.17f1, 2023.1.0a10, 2023.2.17f1, 6000.0.0b15
Couldn’t test with: 2023.1.0a1 - 2023.1.0a9 (see internal notes)
Reproducible on: macOS 14.4 (M2 Pro (Virtual))
Not reproducible on: macOS 14.4.1 (M1 Max)
Note: Reproduces with built-in, URP and HDRP render pipelines
Comments (1)
-
LilGames
Feb 28, 2025 04:20
Also 2022.3.49
Seen in Unity Build Automation service logs for failed iOS builds
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
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
- Scene View Camera overlay preview goes out of Scene View bounds when the Scene View is resized vertically
- UI GameObjects are not positioned at 0,0,0 when creating them while Scene view is active
- Mesh Filter and Mesh Renderer property icons are difficult to see on blue highlight when selected in Animator window
Resolution Note:
Auto mode baking initialize the baking backend + even if there are no lightmaps. It is complicated and risky to change this code. A workaround is to not use auto mode or not use Apple VMs with paravirtual GPUs. Bare metal macs work fine.
Given the risk to introduce regressions when changing this code, we are closing this bug again.