Search Issue Tracker
Won't Fix
Won't Fix in 6000.2.X
Votes
0
Found in
2021.3.44f1
2022.3.49f1
6000.0.22f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-83352
Regression
No
[HDRP] Light Anchor "Common" field can't be collapsed or expanded by clicking the name of the field
How to reproduce:
1. Create a new HDRP Unity project
2. Create an Empty GameObject and add a "Light Anchor" Component in the Inspector
3. Navigate to the "Common" field
4. Try expanding the field by clicking the field's name
Expected result: The field can be expanded by clicking on the name of it
Actual results: The field can be expanded only by clicking the small arrow
Reproducible with: 2021.3.44f1, 2022.3.49f1, 6000.0.22f1
Reproducible on: macOS Sequoia 15.0 (M1)
Not reproducible on: No other environment tested
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- 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
Resolution Note:
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.2.X):
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.