Fix #116435: Rotate Vector node on a link connects wrong sockets #116550
No reviewers
Labels
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#116550
Loading…
Reference in New Issue
No description provided.
Delete Branch "PratikPB2123/blender:116435-vector-default"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
sock_rotation
has higher priority (6) than the vector socket (4).Hence inserting node between vector-vector link joins thorugh "rotation"
socket (
get_main_socket()
/get_main_socket_priority()
).This can be fixed by making "vector" input socket as default for link.
But this will break the link creation when node is inserted between
rotation-rotation link. It seems rotation is converted to vectors so
perhaps make sense to make "vector" as default socket for link.
I'm unsure about this. It feels like the link chosen should depend on the type of the sockets from the other nodes. For example, a vector link should try to connect to the vector socket, and likewise for rotations, probably regardless of the "default link status" of each declaration. I'm not sure if we have the tools to do that with the current auto-link connection. What do you think?
Might issue related with the fact that link is connected to rotation, instead of vector. So auto-linking should be fixed instead.
This make sense. Right now,
get_main_socket
is returning best_input/best_output socket based onis_default_link_socket
. If default_link is nullptr, it chooses "socket with highest priority" for connection. This looks odd. I can make changes inget_main_socket
so it'll use the socket types of old-link for the new connectionLike this? I'll wait to update the PR
Code Changes
You might as well update the PR, it will be easier to review that code here. The default socket fix doesn't seem right to me, since neither the vector nor rotation input of this node feels "more important" than the other to me.
@HooglyBoogly hi, updated the PR BTW.
Gitea had some issues that day (wasn't sending emails, nor updating PR for some time). So a friendly poke in case you haven't received the mail either 🙂
No rush for the review, take your time.
I actually kinda think that the original fix was correct. This is about dropping the node on an existing link. It doesn't really make sense to insert that node on a link that goes to a rotation socket.
Using the original fix is fine with me if it seems better to Jacques.
I'll update the PR tommorw then :)
bce57da558
tobe400677f5
ok, reverted the change and updated the description as well :)