Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X
Votes
0
Found in
6000.0.22f1
6000.1.0a7
Issue ID
UUM-82984
Regression
No
[APV] Some of the subdivision levels are not shown by default when displaying probes using the Rendering Debugger
*Steps to reproduce:*
1. Create a new project using the Universal 3D template
2. Create a cube at the origin, make it static, make it use lightprobes
3. In the SRP asset, change the Light Probe System from LightProbeGroups to AdaptiveProbeVolumes
4. Create an Adaptive Probe Volume at the Origin
5. Generate Lighting
6. Use the Rendering Debugger and the Probe Volume section to Display Probes
7. Notice how only probes from the smaller subdivision level are shown
8. Use the Max Subdivision Displayed option to manually display all the subdivision levels
\\
*Actual results:*
Only probes from one subdivision level are shown
*Expected results:*
All the generated probes are shown, the Max Subdivisions Displayed should by default include all the subdivision levels, otherwise users might think some probes are missing (while it's only a parameter from the debug view)
\\
*Reproducible with versions:*
*Not reproducible with versions:*
*Can’t test with versions:*
\\
*Tested on (OS):*
\\
*Notes:*
*
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment