Search Issue Tracker
Won't Fix
Won't Fix in 6000.3.X
Votes
0
Found in
6000.0.23f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
Issue ID
UUM-83866
Regression
No
[UI] Labels to enable or disable Columns for Reflection Probes Clipping Planes do not match actual Column Labels
Steps to reproduce:
- Open any Project
- Add a Reflection Probe to the Scene
- Navigate to Window > Rendering > Light Explorer and choose "Reflection Probes" at the top
- Right click any of the Column Labels and observe that "Near Clip" and "Far Clip" can be disabled
- Observe columns "Near Plane" and "Far Plane" in the Light Explorer
Actual results: Columns for clipping planes are labeled as "Near Plane" and "Far Plane" in the Light explorer, but right clicking to enable or disable these columns is labeled as "Near Clip" and "Far Clip"
Expected results: Dropdown options for enabling clipping plane columns are labeled as "Far Plane" and "Near Plane"
Reproducible with versions: 6000.0.23f1 (New Column Labels were introduced)
Not reproducible with versions: 2021.3.44f1, 2022.3.50f1 (Columns were labeled differently)
Tested on (OS): Windows 11, Ubuntu 24.04
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.