Search Issue Tracker
Fixed in 9.x
Votes
1
Found in [Package]
2018.4
2019.3
2019.3.0f4
2020.1
Issue ID
1209047
Regression
No
[Shader Graph] Unresponsive editor when using large (40+ nodes) graphs
Steps to reproduce:
1. Download and open "Bug" project
2. Select "EXAMPLESHADER" in the Project window
3. Press "Open Shader Editor" in the Inspector window
4. Undock the Shader Graph window and place it next to Unity Editor
5. In the Editor, press Play
Expected result: Entering Play mode doesn't take 30 seconds, Shader Graph window doesn't stay blank for 30 seconds
Actual result: Shader Graph window stays unresponsive for around 30 seconds, Play mode loading takes around 30 seconds to load
Reproduced with: 2018.4.15f1, 2019.2.18f1, 2019.3.0f1, 2020.1.0a18 ("Shadergraph" package versions 0.1.17.preview - 7.1.7)
Could not test with: 2017.4 (No package manager)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on mono_log_write_logfile when more than one copy of bee_backend is running
- NativeList<T>.ParallelWriter.AddNoResize() causes memory corruption when used in a [BurstCompile] IJobParallelFor on Web builds
- Realtime reflection probe changes light strength when removing light sources using URP WebGL
- Objects near the screen edge are not culled when using GPU Occlusion Culling
- InvalidCastException is thrown when hovering over a Tilemap with a saved Random Brush pick containing empty cells
Add comment