Node wrangler doesn't work right for the principled bsdf node #98246
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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-addons#98246
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Blender Version 3.1.2Short description of errorusing lazy connect to connect anything starting from the metallic value and down on the principled bsdf node either doesnt work or it connects to the wrong valueExact steps for others to reproduce the error**
Based on the default startup or an attached .blend file (as simple as possible).
with node wrangle enabled,
Shift + alt + rmb and drag the rgb node to anything on the bsdf node starting from the metallic down
untitled.blend
Added subscriber: @billyand
Added subscriber: @pioverfour
Can confirm on latest master. Some subsurface inputs are disabled and thus the count gets offset (Subsurface IOR and Subsurface Anisotropy). I believe this fixes it:
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Confirmed'
The node needs to be in Christensen Burley SSS mode to replicate this issue.
Closed as duplicate of #94290