Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.4
2019.1
2019.2
2019.3
2020.1
2020.2
2020.2.0a17
Issue ID
1261335
Regression
No
[LightProbes][Prefabs] Blue highlight(Override Indicator) is missing for "Light Probe Group"
Blue highlight(Override Indicator) is missing for the "Light Probe Group" component in the inspector, Refer the attached video
Steps to reproduce:
1. Create a new project
2. Hierarchy > Create > Light > Light Probe Group
3. Make a prefab of Light Probe Group
4. Hierarchy > Light Probe Group > Inspector
5. Edit Light Probe Properties
Actual result:
Blue highlight is not available for Light Probe Group
Expected result:
Blue highlights should be available for the Light Probe Group
Occurring on:
2020.2.0a17, 2020.1.0b15, 2019.3.15f1, 2019.2.13f1, 2019.1.11f1, 2018.4.24f1
Environment:
Occurring on Windows 10 & Mac 10.15.
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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Resolution Note (2020.2.X):
This bug is part of a larger refactor of Light Probe editing tools.