Search Issue Tracker
Won't Fix
Won't Fix in 6000.1.X
Votes
0
Found in
6000.0.22f1
6000.1.0a7
Issue ID
UUM-83356
Regression
No
[HDRP] "Light Anchor" tool has no Tooltip explaining its functions
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. In the Scene view, navigate to the "Tools"
4. Hover on the tool under the "LA" field (Light Anchor)
Expected result: The tool has a Tooltip explaining its work
Actual results: The tool throws a default Tooltip of the whole "Tools" bar
Reproducible with: 6000.0.22f1
Can't test with: 2021.3.44f1, 2022.3.49f1 (No tool)
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- 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
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.1.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.