Noodles connected to vector math node may become invalid but remain connected after mode change #83269

Closed
opened 2020-12-01 08:05:43 +01:00 by Micah Matichuk · 15 comments

System Information
Operating system: Windows 10 20H2
Graphics card: NVIDIA RTX 2070 Super
(Other systems have exhibited identical behavior.)

Blender Version
Broken: 2.91.0

Short description of error
When the vector output of a vector math node set to cross product (or any other mode offering a vector output type) is connected to another node's input, and the mode of the vector math node is changed to one such as dot product offering only a scalar output (or vice versa), the connection between nodes is not completely severed, though the noodle seems to disappear. The invalid connection can cause visual artifacts in the render. If the user clicks on the input of the node that the vector math node was plugged into, and drags, the noodle once again appears, and it is possible to sever the connection or plug it into another input.

Exact steps for others to reproduce the error
The issue can be replicated simply as follows:
Start Blender, open the shader editor (change to world shader or create a material to edit), add a vector math node and plug the default vector-type output into any input (such as "surface" of the world output). Now change the vector math node to a mode with scalar output type, such as dot product. The noodle will disappear. Now click on the input dot where the noodle had ended, and drag. The noodle will reappear.

Another interesting observation is that if the vector math node is moved after its mode is changed, and the invalidated noodle is made to reappear (by dragging its endpoint), its starting point remains at the original location of the vector math node.

In addition, the receiving socket remains "occupied" (in that it will not display the input field as if it was unconnected).

The included .blend contains a vector math node that has both invisible inputs and outputs. To see the noodles reappear, switch the vector math node to "Scale" mode.

phantom_noodles.blend

**System Information** Operating system: Windows 10 20H2 Graphics card: NVIDIA RTX 2070 Super (Other systems have exhibited identical behavior.) **Blender Version** Broken: 2.91.0 **Short description of error** When the vector output of a vector math node set to cross product (or any other mode offering a vector output type) is connected to another node's input, and the mode of the vector math node is changed to one such as dot product offering only a scalar output (or vice versa), the connection between nodes is not completely severed, though the noodle seems to disappear. The invalid connection can cause visual artifacts in the render. If the user clicks on the input of the node that the vector math node was plugged into, and drags, the noodle once again appears, and it is possible to sever the connection or plug it into another input. **Exact steps for others to reproduce the error** The issue can be replicated simply as follows: Start Blender, open the shader editor (change to world shader or create a material to edit), add a vector math node and plug the default vector-type output into any input (such as "surface" of the world output). Now change the vector math node to a mode with scalar output type, such as dot product. The noodle will disappear. Now click on the input dot where the noodle had ended, and drag. The noodle will reappear. Another interesting observation is that if the vector math node is moved after its mode is changed, and the invalidated noodle is made to reappear (by dragging its endpoint), its starting point remains at the original location of the vector math node. In addition, the receiving socket remains "occupied" (in that it will not display the input field as if it was unconnected). The included .blend contains a vector math node that has both invisible inputs and outputs. To see the noodles reappear, switch the vector math node to "Scale" mode. [phantom_noodles.blend](https://archive.blender.org/developer/F9418387/phantom_noodles.blend)
Author

Added subscriber: @Micahchuk

Added subscriber: @Micahchuk

#94730 was marked as duplicate of this issue

#94730 was marked as duplicate of this issue

#93269 was marked as duplicate of this issue

#93269 was marked as duplicate of this issue

Added subscribers: @JulianEisel, @JacquesLucke, @rjg

Added subscribers: @JulianEisel, @JacquesLucke, @rjg

Changed status from 'Needs Triage' to: 'Resolved'

Changed status from 'Needs Triage' to: 'Resolved'
Robert Guetzkow self-assigned this 2020-12-01 12:05:51 +01:00

The hidden connection when switching operations is intentional, however being able to edit it by clicking on the socket it was connected to seems wrong.

@JacquesLucke @JulianEisel Is this the expected behavior?

The hidden connection when switching operations is intentional, however being able to edit it by clicking on the socket it was connected to seems wrong. @JacquesLucke @JulianEisel Is this the expected behavior?

Changed status from 'Resolved' to: 'Needs Triage'

Changed status from 'Resolved' to: 'Needs Triage'
Robert Guetzkow removed their assignment 2020-12-01 12:08:29 +01:00
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Will confirm this for now.
In addition, the receiving socket remains "occupied" (in that it will not display the input field as if it was unconnected).

Will confirm this for now. In addition, the receiving socket remains "occupied" (in that it will not display the input field as if it was unconnected).

Added subscribers: @DEBIHOOD, @iss

Added subscribers: @DEBIHOOD, @iss

Added subscriber: @MysteryPancake

Added subscriber: @MysteryPancake
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Usually duplicate report is expected to be merged in the older one.
But #89387 has more clear instructions with explicit info about the issue.
So I will merge this report into #89387. Thanks for the report!
(Philipp also agreed about this)

Usually duplicate report is expected to be merged in the older one. But #89387 has more clear instructions with explicit info about the issue. So I will merge this report into `#89387`. Thanks for the report! (Philipp also agreed about this)
Member

Closed as duplicate of #89387

Closed as duplicate of #89387
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#83269
No description provided.