Search Issue Tracker
In Progress
Fixed in 6000.2.11f1, 6000.3.0b9, 6000.4.0a4
Fix In Review for 2022.3.69f1, 6000.0.62f1
Votes
0
Found in
2022.3.66f1
6000.0.57f1
6000.2.3f1
6000.3.0b1
6000.4.0a1
Issue ID
UUM-116667
Regression
No
"NullReferenceException" error is thrown on a new project when creating a new project after exiting a project with Light Batching Debugger window docked
Steps to reproduce:
- Create a new Unity project using the Universal 2D template
- Open the Light Batching Debugger window (Window > 2D > Light Batching Debugger)
- Dock the Light Batching Debugger window
- Close the Editor
- Repeat step 1
- Observe the Console window
Actual results: "NullReferenceException: Object reference not set to an instance of an object" error is thrown
Expected results: No errors or warnings are thrown
Reproducible with versions: 2022.3.66f1, 6000.0.57f1, 6000.1.16f1, 6000.2.3f1, 6000.3.0b1
Fixed in: 6000.2.4f1
Tested on (OS): macOS Silicon Sequoia 15.6.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment