Search Issue Tracker
Won't Fix
Won't Fix in 6000.3.X
Votes
0
Found in
2021.3.56f1
2022.3.66f1
6000.0.57f1
6000.2.4f1
6000.3.0b1
Issue ID
UUM-117056
Regression
No
Disabled dropdowns in Lighting window are inconsistently expanded or collapsed
Reproduction steps:
{}{}1. Create a new project
2. Open Lighting window (Window > Rendering > Lighting)
3. Observe the dropdowns that are disabled
Actual result: Some dropdowns are expanded and some collapsed and expanding/collapsing them is not possible
Expected result: All dropdowns are expanded/collapsed or it could be changed manually
Reproducible with: 2021.3.56f1, 2022.3.66f1, 6000.0.57f1, 6000.2.4f1, 6000.3.0b1
Reproduced on: Windows 11
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
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.