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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 507ca2d ):
Resolved by this PR which was merged in today: https://github.com/Unity-Technologies/Graphics/pull/3555