Search Issue Tracker
Fixed in 7.0.0
Votes
1
Found in [Package]
5.16.1, 6.9.0
Issue ID
1170465
Regression
Yes
Shader Graph freezes when a new property is added via Blackboard
How to reproduce:
1. Open the attached project ("case_1170465-Shadergraph freeze.zip")
2. Open the "Water General" Shader Graph
3. Add any new property to it via the Blackboard and save it
Expected results: Shader Graph window continues to work without issues
Actual results: Shader Graph window freezes
Reproducible with: 2019.2.0b10, 2019.3.0a10
Does not reproduce on 2017.4, 2018.4, 2019.1 as those branches do not support required package versions
Reproducible with package versions: 5.10.0, 5.16.1, 6.7.1, 6.9.0
Does not reproduce with package version: 5.9.0, 6.5.2, 6.5.3
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
Tomyn
Oct 09, 2019 03:54
So got anyone having this issue while using a version of shader graph earlier than 7.0, I found the freezing up only happens when you rename your properties. It's still not convenient but if you add all your properties first to test them you'll at least be able to continue working. You'll still unfortunately suffer the freezing as you rename each one afterward.
juliano09
Sep 20, 2019 14:10
Version 6.9.1
Unity 2019.2.5f1
juliano09
Sep 20, 2019 14:03
Hi, I'm Experiencing this issue too, it became almost impossible to keep the workflow. Please fix that!
NickDWilliams
Aug 09, 2019 16:06
I also agree that this fix should be implemented as soon as possible, given that it heavily complicates the workflow of Shader Graph for everyone. Additionally, is there a way to know when 7.0.0 is intended to be released?
Tracecat
Aug 02, 2019 08:16
Depending on when shader graph 7.0 will be released, it might be very important to have this fixed in 6.9.x versions too. As my pre commenter already stated, it is a quite serious workflow issue.
pfc
Aug 01, 2019 12:45
Any news on when this will be backported? Since this happens in LWRP release versions on 2019.1 and 2019.2 it's a pretty heavy workflow issue.