Search Issue Tracker
Fixed
Won't Fix in 6000.3.X, 6000.4.X
Fixed in 6000.5.0a5
Votes
0
Found in
6000.3.0b10
6000.4.0a5
6000.5.0a1
Issue ID
UUM-127026
Regression
No
Thumbnail section has shrunk to a very narrow row in the Shader Graph Templates window
Steps to reproduce:
- Create a project (Universal 2D)
- Go to the "Project" window
- Click "Create" -> Shader Graph -> From Template...
- Select "Empty Shader Graph" and click "Create"
- Select the newly created graph in the "Project" window
- Go to the "Inspector" section
- Check "Use As Template"
- Add graph name, description, icon, and thumbnail
- Save all the changes
- Click "Create" -> Shader Graph -> From Template...
- Observe how the new template with its data is displayed in the window
- Return to the "Inspector" section
- Update the description section. Make it much, much longer
- Click "Create" -> Shader Graph -> From Template...
- Observe how the "Thumbnail" section changed
Actual results: The thumbnail section has shrunk to a very narrow row
Expected results: The thumbnail section has to stay stable
Reproducible with versions: 17.5.0 (6000.5.0a1), 17.4.0 (6000.4.0a5), 17.3.0(6000.3.0b10)
Not reproducible with versions: -
Can’t test with versions: -
Tested on (OS): macOS - Tahoe 26.1
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
- Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
Resolution Note (6000.4.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.
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.