Search Issue Tracker
Fixed in 507ca2d
Votes
0
Found in [Package]
4.3.1
Issue ID
1270615
Regression
Yes
[Shadergraph] Best fit for terms typed in the searcher is no longer selected after 7.x.x
Repro steps:
1. Open a shadergraph
2. Create a vector 1 node
3. Drag the edge out from the vector 1 node onto the graph
4. When the searcher pops up, type in "prev"
Expected result: "Preview" is an easily accessible result
Actual result: the results are drowned out by a bunch of nodes with (Preview) in the title, and you have to scroll all the way to the bottom to get to the one you want
Note: the same thing happens with "Color" "Lerp" and other terms; simply typing these and pressing enter would create the correct node, but this is no longer the case after 7.x.x/19.4. This is a major workflow regression and should be fixed in all currently supported versions after 7.x.x if possible.
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
- UI becomes unresponsive when using AppUI Navigation and Event System is attached
- Freeze/crash with multiple StackTraces when opening a specific project
- Crash on TypeContainer<int>::rtti when deleting a Render Texture that is used by the Main Camera
- Multiple ArgumentExceptions are thrown when adding a VisualTreeAsset with Sprite Glyphs to a UIDocument
- Color Node Alpha slider displays incorrect value when viewed in Shader Graph
Resolution Note (fix version 507ca2d ):
Resolved by this PR which was merged in today: https://github.com/Unity-Technologies/Graphics/pull/3555