Search Issue Tracker
Fixed
Fixed in 2022.3.11f1, 2023.1.14f1, 2023.2.0a22
Votes
0
Found in
2022.3.9f1
2023.1.0b11
2023.2.0a16
2023.3.0a3
Issue ID
UUM-33050
Regression
No
Light Probe Group Visualizations are still shown when Probe Volumes are enabled
*Repro:*
# Create a project using 2023.1.0b11 and HDRP
# Ensure that the Light Probe system is set to "Light Probe Groups" from the assigned render pipeline asset
# Create a Scene and a basic Light Probe Group
# Ensure that "Light Probe Visualization" is enabled from Workflow Settings in the Lighting Window
# Generate Lighting to see the visualizations
# Now go to the assigned render pipeline asset and change Light Probe System to "Probe Volumes"
# Generate lighting again
!image9.png|width=658,height=495!
*Observed:*
# Light Probe Group visualizations are now shown on-top of the Probe Volume system, which is incorrect.
# In complex Scenes, the additional debug overlay can make the Scene unreadable
# The UI to disable the visualizations is automatically hidden when Probe Volumes re enabled, meaning that the debug view cannot easily be disabled
!image.png|width=364,height=382!
*Notes:*
"Likely no check for SupportRenderingFeatures.overridesLightProbeSystem in the rendering code in LightProbeVisualization.cpp. I think this particular visualization starts in DrawLightProbeGizmoImmediate. It all happens on C++ side"
This issue is already fixed on the URP side, so is HDRP specific.
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
- 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
Resolution Note (fix version 2023.1.14f1):
Verified as fixed with new type and typesetting
Resolution Note (fix version 2022.3.11f1):
Verified as fixed in latest 2022.3/staging