Search Issue Tracker
Fixed in 12.0.0
Votes
0
Found in [Package]
10.2.2
Issue ID
1328756
Regression
Yes
[Shadergraph] Default inputs for keyword nodes is vec4s even though they become floats when the node is plugged in
Reproduces in 10.2.2
Doesn't reproduce in 7.3.1
Repro steps:
1. Create a boolean or enum keyword
2. Drag it onto the graph
Expected results: the inputs are Floats/Vector1s
Actual result: the inputs are Vector4s, even if when you plug the output of the node into something, the inputs becomes Floats/Vector1s
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [VisionOS] Animating a material property results in artifacts when the app mode is set to RealityKit and shader modifies the Vertex Shader
- "DirectoryNotFoundException" is thrown and Shader Graph does not open when opening a .shadegraph from a long path
- “Full Screen Pass Renderer Feature_Old GUID” text is cut off in Renderer Features window
- "Undo: Already found nextRootTransform, but with different state cached" error thrown when undoing changes made to the Hierarchy using a script
- "No GUI Implemented" is displayed when using PhysicsMask with a CustomEditor
Add comment