Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
7.0.1
Issue ID
1184248
Regression
Yes
[Shader Graph] Inline Color Node's value is too intensive
How to reproduce:
1. Open user's attached 'Shaders Playground HDRP.zip' project
2. Close Maintainer window
3. Open 'Simple Dissolve' Scene
4. Enter Play Mode
5. Observe the Game View
6. Open 'Simple Dissolve' Shader Graph
7. Right-click mouse on the Color node -> Convert To Property
8. Click Save Asset
9. Observe the Game View
Expected result: GameObject does not bloom
Actual result: GameObject blooms
Reproducible with: ShaderGraph 7.0.1 (2019.3.0a12, 2019.3.0b4, 2020.1.0a5)
Not reproducible with: Shader Graph 6.9.1 (2019.2.7f1), Shader Graph 6.5.3 (2019.3.0a11)
Could not test: 2017.4.32f1 because Package Manager is not introduced, 2018.4.9f1, 2019.2.0a1 due to Shader Graph, LWRP errors, pink textures
Note: Reproducible on Windows, macOS
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
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
This is a duplicate of issue #1212235