Material Node Groups bug connections with shortcut "F" #46702

New Issue

Marcin Hryniewicz · 2015-11-05T13:11:38+01:00

Marcin Hryniewicz commented

2015-11-05 13:11:38 +01:00

System Information - Intel Core i5-4590 CPU 3.3GHz 16 RAM
Operating system: Windows 8.1 64, and graphics card: NVIDIA GeForce GTX 760

Blender Version
Broken: 2.76b f337fea

Short description of error
Material Node Groups bug connections with shortcut "F"

Exact steps for others to reproduce the error

Make Group Node
Select Node Output with Shift
Select Group Output Node with Shift
Press "F" - first pair connected
Repeat step 2 and 3 for next nodes
Nodes not connected and can not even connect manualy
bug_nodes.blend

**System Information - Intel Core i5-4590 CPU 3.3GHz 16 RAM** Operating system: Windows 8.1 64, and graphics card: NVIDIA GeForce GTX 760 **Blender Version** Broken: 2.76b f337fea **Short description of error** Material Node Groups bug connections with shortcut "F" **Exact steps for others to reproduce the error** 1. Make Group Node 2. Select Node Output with Shift 3. Select Group Output Node with Shift 4. Press "F" - first pair connected 5. Repeat step 2 and 3 for next nodes 6. Nodes not connected and can not even connect manualy [bug_nodes.blend](https://archive.blender.org/developer/F252689/bug_nodes.blend)

Marcin Hryniewicz commented

2015-11-05 13:11:38 +01:00

Changed status to: 'Open'

Marcin Hryniewicz commented

2015-11-05 13:11:38 +01:00

Added subscriber: @MarcinHryniewicz

ronan ducluzeau commented

2015-11-05 15:52:56 +01:00

Added subscriber: @zeauro

ronan ducluzeau commented

2015-11-05 15:52:56 +01:00

No such problem on linux.
Maybe it is a misunderstanding.

Output of a nodegroup is just a representation outside group of ouput of a node inside group.
So, entry socket of Group Output node can only correspond to one output of a node inside group.

One output of a node can correspond to several outputs of nodegroup.
But one output of nodegroup cannot correspond to several outputs of different nodes inside the group.

So, if you want to replace node output in a socket of Group Output node, you have to use shift F.
And if you want to add a new output to Group Output, you have to make a connection with transparent , ghost socket of Group Output node or to select Group Output node and add it into Interface Panel in N column.

Do you have a problem with one of these last steps ?

No such problem on linux. Maybe it is a misunderstanding. Output of a nodegroup is just a representation outside group of ouput of a node inside group. So, entry socket of Group Output node can only correspond to one output of a node inside group. One output of a node can correspond to several outputs of nodegroup. But one output of nodegroup cannot correspond to several outputs of different nodes inside the group. So, if you want to replace node output in a socket of Group Output node, you have to use shift F. And if you want to add a new output to Group Output, you have to make a connection with transparent , ghost socket of Group Output node or to select Group Output node and add it into Interface Panel in N column. Do you have a problem with one of these last steps ?

Marcin Hryniewicz commented

2015-11-05 16:20:44 +01:00

I try to visualise problem here: https://youtu.be/WtC68jVKPTM

Sergey Sharybin commented

2015-11-06 14:03:50 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-11-06 14:03:50 +01:00

It always helps a lot to put down step-by-step instruction in words rather than putting video with some insane fps. It's really hard to see what's exactly you're doing and from the provided steps i can't reproduce the issue either.

So please make sure the instructions of reproducing the bug ire all clear.

It always helps a lot to put down step-by-step instruction in words rather than putting video with some insane fps. It's really hard to see what's exactly you're doing and from the provided steps i can't reproduce the issue either. So please make sure the instructions of reproducing the bug ire all clear.

Campbell Barton commented

2015-11-12 14:15:04 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2015-11-12 14:15:04 +01:00

Even though its not easy to follow, I think I see whats going on... Though I can't redo the error.

Bastien Montagne commented

2015-11-20 12:38:09 +01:00

Added subscribers: @JulianEisel, @mont29

Bastien Montagne commented

2015-11-20 12:38:09 +01:00

Could reproduce quite easily with given file - not sure it’s totally a bug, but would be nice to get it working though.

Issue is the following: 'output' node in a group has some kind of 'virtual' input socket, in addition to all already created ones, which automatically creates/adds a new output socket to the group when you drag a connection to it. This does not work with the F shortcut.

Maybe @JulianEisel could be interested implementing this? Does look like a short & fun UI task. ;)

Could reproduce quite easily with given file - not sure it’s totally a bug, but would be nice to get it working though. Issue is the following: 'output' node in a group has some kind of 'virtual' input socket, in addition to all already created ones, which automatically creates/adds a new output socket to the group when you drag a connection to it. This does not work with the `F` shortcut. Maybe @JulianEisel could be interested implementing this? Does look like a short & fun UI task. ;)

Julian Eisel self-assigned this 2015-11-20 16:16:51 +01:00

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Material Node Groups bug connections with shortcut "F" #46702