Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
5.3.1
Issue ID
1123056
Regression
No
[ShaderGraph] Only one entry in dropdown when choosing color channels for Swizzle node
How to reproduce:
1. Open the user's project
2. Open "New Shader Graph 1" in Shader Graph
3. Create a Swizzle node (Right-click -> Create Node -> Channel -> Swizzle)
4. Attach the color node's output as the input to the Swizzle node
5. Open the "Red Out" dropdown (or any other channel's output) of the Swizzle node
6. Observe available channels
Expected result: options "Red", "Green", "Blue" and "Alpha" are available in the dropdown
Actual result: only "Red" is available in the dropdown
Reproducible with: 2018.3.5f1, 2019.1.0b2, 2019.2.0a4
Could not test with: 2017.4 and older (no shader graph).
Reproducible with package versions: 2.01 to 5.3.1
Not reproducible package versions: 1.1.9 and older
Note: collapsing the node's preview or toggling the node's output (downward arrow at top right of the node when no output is attached) fixes the issue
Comments (1)
-
LooperVFX
Oct 09, 2019 20:23
This is actionable in the close future. Just make "Red", "Green", "Blue" and "Alpha" ALWAYS available in the dropdown menu for now, no major refactor needed. and If those components don't exist, then throw a warning or just default to 0 values.
Shader Graph has been out of preview since 2019.1, 6 months ago and it's not acceptable to have something as essential to shader creation as swizzling be THIS broken and have a very hidden workaround (NOT a fix.) You can mitigate this easily. Thanks.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
This requires substantial improvements to our node changed events to propogate this information to the UI layer. This has been added to the feature backlog.