Search Issue Tracker
In Progress
Under Consideration for 6000.2.X, 6000.3.X
Fix In Review for 6000.4.X
Votes
0
Found in
6000.2.1f1
6000.3.0b1
6000.4.0a1
Issue ID
UUM-116573
Regression
Yes
"AssertionExceptions" are constantly spammed into the Console when in Volume of Rendering Debugger Camera is set to "ScreenCamera" or "SceneCamera" and any Component is chosen
How to reproduce:
1. Create a new 3D URP Sample project and open the "TerminalScene" scene
2. Go to Window -> Analysis -> Rendering Debugger -> Volume
3. Set the "Camera" field to the "SceneCamera" (or "ScreenCamera")
4. Set the "Component" field to anything
5. Observe the Console
Expected results: No errors are thrown
Actual results: "AssertionException: Assertion failure. Value was Null" errors are constantly spammed
Reproducible with: 6000.2.0b3, 6000.2.1f1, 6000.3.0b1
Not reproducible with: 6000.0.56f1, 6000.2.0b2
Reproducible on: Ubuntu 24, Windows 11
Not reproducible on: macOS Sequoia 15.6 (M1)
Note: The issue is reproducible with either "ScreenCamera" or "SceneCamera" across different projects but never with both of them
First lines of error:
AssertionException: Assertion failure. Value was Null
Expected: Value was not Null
UnityEngine.Assertions.Assert.Fail (System.String message, System.String userMessage) (at /home/bokken/build/output/unity/unity/Runtime/Export/Assertions/Assert/AssertBase.cs:29)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment