Search Issue Tracker
Duplicate
Votes
0
Found in
2019.4.20f1
2020.3
2021.1
2021.1.11f1
2021.2
Issue ID
1343876
Regression
Yes
Lightmapper gets into an endless cycle of errors when changing Scenes after baking in previous Scene
How to reproduce:
1. Open the user's attached "BakeBugTest.zip" project
2. Right-click on "Scene 1 (not loaded)" and press "Load Scene"
3. Right-click again and press "Set Active Scene"
4. Press Generate Lighting in the Lighting Tab
5. Right-click on "Scene 1" and press "Unload Scene"
6. Repeat 2-3 steps for "Scene 2 (not loaded)"
7. Observe the Console log
Expected result: No errors in the Console log
Actual result: "Failed to reserve memory for scene-based lightmaps" and "Integrate failed on Write Lighting Data job." errors are thrown in the Console log and importing is stuck
Reproducible with: 2019.4.20f1, 2019.4.28f1, 2020.3.12f1, 2021.1.12f1, 2021.2.0b1
Not reproducible with: 2018.4.34f1, 2019.4.19f1
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #1337508