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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
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.