In Node editor, Groups name does not change #70364

Closed
opened 2019-09-29 19:19:36 +02:00 by Dev · 8 comments

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.5063

Blender Version
Broken: version: 2.81 (sub 12), branch: master, commit date: 2019-09-21 08:48, hash: ef45d1c8cd
Worked: (optional)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.5063 **Blender Version** Broken: version: 2.81 (sub 12), branch: master, commit date: 2019-09-21 08:48, hash: `ef45d1c8cd` Worked: (optional) **Short description of error** [Please fill out a short description of the error here] **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)]
Author

Added subscriber: @Awesome_dev

Added subscriber: @Awesome_dev

#70365 was marked as duplicate of this issue

#70365 was marked as duplicate of this issue
Author

Description
I was creating nodes and when i assigned them to group and joined group to all 3 "color" of 3 shaders name of node from group was "color" but when i removed "color" from group to "roughness" of 3 shaders name of node of group joined to "roughness" of 3 shader was still "color".

Steps to reproduce

1 Assign any 2 or more than 2 same nodes to a mesh.

2 Join them to a group.

3 Join color of nodes to group.

4 Cut group nodes and join same node from group to roughness or anything else to all shaders.

**Description** I was creating nodes and when i assigned them to group and joined group to all 3 "color" of 3 shaders name of node from group was "color" but when i removed "color" from group to "roughness" of 3 shaders name of node of group joined to "roughness" of 3 shader was still "color". **Steps to reproduce** 1 Assign any 2 or more than 2 same nodes to a mesh. 2 Join them to a group. 3 Join color of nodes to group. 4 Cut group nodes and join same node from group to roughness or anything else to all shaders.
Author
[bug.blend](https://archive.blender.org/developer/F7780079/bug.blend)
Author

This comment was removed by @Awesome_dev

*This comment was removed by @Awesome_dev*
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Philipp Oeser self-assigned this 2019-09-30 11:03:35 +02:00
Member

Not sure I understand correctly:

  • when you first connect a socket to a new group input socket, its suggested name is derrived from the connected socket, true (this is just a suggestion made for you).
  • once it already has a name, this wont change if you connect something new to it.
  • in general, you are free to name these sockets whatever you want (e.g. "MyColor")

image.png

As you can still drag a socket of your choice to a new group input socket (to get the suggested name) and remove the other one, and as there are scenarios where you definitely want to keep your custom name, I would not consider this a bug.
(It is a feature request at most and I personally would not want to have this changed.)

I will close this as not a bug, but feel free to comment again if issues persist...
https://wiki.blender.org/wiki/Reference/Not_a_bug
If you still want this as a feature request, you can use other channels for it, thx.
For requests and feedbacks please visit: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

Not sure I understand correctly: - when you first connect a socket to a `new` group input socket, its suggested name is derrived from the connected socket, true (this is just a suggestion made for you). - once it already has a name, this wont change if you connect something new to it. - in general, you are free to name these sockets whatever you want (e.g. "MyColor") ![image.png](https://archive.blender.org/developer/F7781519/image.png) As you can still drag a socket of your choice to a `new` group input socket (to get the suggested name) and remove the other one, and as there are scenarios where you definitely want to keep your custom name, I would not consider this a bug. (It is a feature request at most and I personally would not want to have this changed.) I will close this as not a bug, but feel free to comment again if issues persist... https://wiki.blender.org/wiki/Reference/Not_a_bug If you still want this as a feature request, you can use other channels for it, thx. For requests and feedbacks please visit: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
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
3 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#70364
No description provided.