Fix VisualShaderNodeVaryingGetter
expanded ports adding ".x" to shader
#92847
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
VisualShaderNodeVaryingGetter
type was Vector2/Vector3/Vector4, expanding the output ports and connecting an individual value to a scalar input would add ".x" to the assignment in the generated shader. This was due toVisualShaderNodeVarying::get_port_type
ignoring the port number, and always returning the associated vector type. Added checks forp_port == 0
to return either the vector type, or scalar for expanded ports, matching similar logic in other nodes, likeVisualShaderNodeColorConstant::get_output_port_type
.Fixes #92832