Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.3.0a6
6000.4.0a1
6000.5.0a1
Issue ID
UUM-115026
Regression
No
Terrain Texture Node Dropdown Menu's options aren't fully visible when selected
Steps to reproduce:
- Open any HDRP or URP Project with Shader Graph Installed
- In the Project Browser create a Shader Graph and open it
- Create a Terrain Texture Node
- Observe the selected option at the bottom of the Node
Actual results: Most of the options aren't fully visible
Expected results: All options are visible in the dropdown menu when selected
Reproducible with versions: 6000.3.0a6
Can't test with versions: 2022.3.66f1, 6000.0.56f1, 6000.1.16f1, 6000.2.2f1 (No Terrain Shader Graph Nodes)
Tested on (OS): 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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
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.5.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.