Search Issue Tracker
Fixed in 9.0.0-preview
Votes
0
Found in [Package]
4.10
Issue ID
1209567
Regression
No
[ShaderGraph] Opening node search window is unnecessarily slow
Steps to reproduce:
1. Download attached project.
2. Open New Shader Graph
3. Right Click -> New Node
Result: Node search window opens after about 500ms to 1000ms
Expected: It is a very common operation and should not be noticeable. Less than 500ms, prefferably less than 300ms
It happens on empty project with HDRP template. Not sure what is the impact for big projects.
Tested on development machine with i9-7960X CPU, impact on laptops will be even greater
Version 2019.3.0f5 (209f7fb30bd5)
Sat, 04 Jan 2020 04:12:01 GMT
Branch: 2019.3/staging
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Add comment