Search Issue Tracker
Active
Fixed in 6000.0.29f1, 6000.1.0a5
Votes
0
Found in
6000.0.26f1
6000.1.0a2
7000.0.0a10
Issue ID
UUM-86779
Regression
Yes
[HDRP] Assertion printed when Maximum Reflection Probe count is higher than 64 due to k_MaxCubeReflectionsOnScreen when Raytracing is enabled
Steps to reproduce:
1. Open the attached user's project "ReflectionProbeTest.zip"
2. Open "OutdoorScene.unity" scene
3. Go to Quality -> HDRP in the Project Settings
4. Ensure Realtime Raytracing is disabled in the rendering section of the HDRP Settings
5. Enter Play Mode
6. Notice there is no exceptions or asserts in the console log
7. Go back to the Quality -> HDRP section in the project settings
8. Enable Realtime Raytracing in the rendering section of the HDRP Settings
9. Notice assertions messages in the Console
Expected results: No assertion printed in the Console window
Actual results: Assertion error is printed in the console when Raytracing is enabled with higher than a 64 reflection probe limit value
Reproducible with: 2023.3.0a11, 6000.0.26f1, 6000.1.0a3
Not reproducible with: 2022.3.52f1, 2023.3.0a10
Testing Environment: Windows 11 23H2
Not reproducible on: no other environment tested
Notes:
-Assertion error:
Assertion failed UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
-These assertions are occurring in line 173 in WorldLightManager.cs as the k_MaxCubeReflectionsOnScreen constant is set to 64 but the maximum reflections on screen can be as high as 128 and in this project it's set to 96
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
- Property fields overlap in the Override window when comparing changes
- "Timeflow Animation System" custom package appears twice in the Package Manager
- Sprite Atlas Override for iOS setting remains disabled when saving its change to enabled
- Increased Memory usage when Update Mode 'On Demand' Realtime lights are used and DX12 API is selected
- Shader warnings in URP ShaderGraph when using the Normal From Texture node
Resolution Note (fix version 6000.1.0a5):
Out of bounds asserts were not using the proper array's max value.