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.0a2
6000.4.0a1
6000.5.0a1
Issue ID
UUM-111623
Regression
No
Shader graph template accepts empty values, resulting in broken UI
Steps to reproduce:
- Create a project (Universal 2D)
- Go to the "Project" window
- Click "Create" -> Shader Graph -> Blank Shader Graph
- Select it and double-click
- Go to the "Inspector" tab and select "Use As Template"
- Expand the "Template" section
- Enter space into "Name", "Category", and "Description" fields
- Save it
- Click "Create" -> Shader Graph -> From Template...
- Select the newly created template
- Observe how the template is displayed in the shader graph templates list
Actual results: UI is broken (space and arrow above the template), template is displayed without the name and category. All fields are displayed as optional.
Expected results: Some fields (maybe name and category) should be displayed as mandatory, so that users would be requested to enter main data.
Reproducible with versions: 17.3.0(6000.3.0a2)
Not reproducible with versions: 17.3.0(6000.3.0a1) as templates feature landed only in 000.3.0a2
Can’t test with versions: -
Tested on (OS): M1 Max - Sequoia 15.5
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
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.