Search Issue Tracker
By Design
Votes
0
Found in
2021.3.24f1
2022.1.24f1
2022.2.17f1
2023.1.0b14
2023.2.0a12
Issue ID
UUM-34939
Regression
No
Enabling Per Axis Control for HDRP reflection probes sets all Blend Distance fields to 1
Steps to reproduce:
- Open the attached project ([^HDRP-LightingBug01.zip]);
- Open the OutdoorsScene;
- Select the existing Reflection Probe GameObject in the scene;
- Set Blend Distance property to 0 (or any other value but 1);
- Tick the Per Axis Control flag.
Expected result:
- Per Axis Blend Distance fields use the same value which was set in the Blend Distance property prior.
Actual result:
- Per Axis Blend Distance fields always default to the value of 1.
Notes:
- Observed in 2022.1.24f1 on Windows;
- Affects reflection probes in HDRP only.
- This issue can prove frustrating when placing many reflection probes in the scene.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Implementing this suggestion would result in losing the ability to switch between independent global and per axis blending values. It would be perceived as a regression in functionality.