Search Issue Tracker
By Design
Votes
0
Found in [Package]
12.x
Issue ID
1334062
Regression
No
[ShaderGraph]When convert a color node into property, the color property appeals as "Color(4)" when drag it into the graph
Reproduces in 11.0.0
Repro Steps:
1. Create a color node in a shadergraph.
2. Right-click convert the color node to property.
3. The color property within the graph displays as "Color(4)"
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Resolution Note:
I talked with Tracy offline about this, but this is just some confusion with how the UI currently presents things. For multi-element types (like vector, color, etc...) the count of the number of elements are displayed after the name as `(element count)`. This is also the same syntax used to display duplicates. So if you have a 2nd color property it'll show as `Color(1)(4)`. This behavior is consistent across all other nodes types as shown in the attached gif with a vector3.