Search Issue Tracker
Fixed in 6.7.2
Votes
0
Found in [Package]
6.7.1
Issue ID
1191570
Regression
Yes
Shader Graph freezes when creating a new field with custom name
How to reproduce:
1. Open the "shadergraph_is_broken.zip" project
2. Open the "New Shader Graph1" Shader Graph
3. Press + on the Fields Window
4. Select Color
5. Name the new field
6. Press Enter
Actual result: ShaderGraph freezes.
Expected result: ShaderGraph doesn't freeze.
Reproducible with: 2019.2.0b1(ShaderGraph 6.7.1), 2019.2.10f1 (ShaderGraph 6.9.0), 2019.3.0b7 (ShaderGraph 7.12), 2020.1.0a9 (ShaderGraph 7.12).
Regression introduced in: 6.5.4 - 6.7.1.
Not reproducible with: 2018.4.11f1 (ShaderGraph 4.10), 2019.1.14f1 (ShaderGraph 5.7.2), 2019.2.0b1 (ShaderGraph 6.5.3).
Notes:
- On ShaderGraph 6.9.0 the freeze is permanent, while on ShaderGraph 7.12 freezes only for some time.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 6.7.2):
The fix for permanent freeze is in ShaderGraph 6.7.2.
The minimal freeze on later versions are caused by Editor/Shader compilation.