Search Issue Tracker
Fixed in 2022.2.17f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a13
Votes
0
Found in
2022.2.7f1
2023.1.0b4
2023.2.0a2
Issue ID
UUM-29010
Regression
Yes
Baking fails and sometime crashes Unity when baking lightmaps with imported .glb models
How to reproduce:
1. Open the attached project “LightbakeBugs.zip“
2. Open Scene “SampleScene“ (Assets/Scenes)
3. Open the Lighting window (Window>Rendering>Lighting)
4. Press “Generate Lighting“
Expected result: The Lightmap is baked
Actual result: Baking fails with infinite "Failed to find geometry with hash 00000000000000000000000000000000 for removal." errors in the Console, or single “Light baking could not be started because input extraction failed (FailedCreatingMeshData)“ error in the Console, or Unity crashes (depending on Unity version)
Reproducible with: 2022.2.0a15, 2022.2.7f1, 2023.1.0b4 (Error “Light baking could not be started because input extraction failed (FailedCreatingMeshData)“), 2023.2.0a2 (Unity crashes)
Not reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.0a14
Reproduced on: macOS 13.0.1 (Intel)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 2022.2):
This is working as designed now in 2022.2.17f1 (crash / input extraction error is fixed and the auto mode bake is stuck with a meaningful error)