Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.0b13
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-67989
Regression
No
[APV] "System.NullReferenceException" error is thrown when Generating Lighting with Adaptive Probe Volumes with Additive Scenes
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the Lighting window (Window > Rendering > Lighting)
3. Press the “Generate Lighting” button in the Lighting window
4. Observe the Console window
Expected result: No errors are thrown in the Console window
Actual result: “System.NullReferenceException: Object reference not set to an instance of an object“ error is thrown in the Console window
Reproducible with: 6000.0.045f1, 6000.1.0b13, 6000.2.0a8
Couldn’t test with: 2021.3.36f1, 2022.3.60f1, 2023.2.16f1 (due to Adaptive Probe Volumes feature not existing)
Reproducible on: Windows 11 Pro (22H2), macOS 15.3.2 (M1 Max)
Not reproducible on: No other environment tested
Notes:
* Issue behaviour seems to vary between systems and Unity stream.
** 6000.0, 6000.1 and 6000.2 throw a NullReferenceException if a scene is unloaded
** 6000.0.45f1 has additional problems when baking with all scenes enabled. This breaks the Scene view and eventually leads to a crash
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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.