Node wrangler viewing feature doesn't work if output is already connected. #47892

New Issue

test · 2016-03-22T19:43:04+01:00

test commented

2016-03-22 19:43:04 +01:00

System Information
Windows 10,AMD 5450

Blender Version
Blender 2.77,Hash: 22a2853

Short description of error

When I try to view an output using the node wrangler addon when it is already connected to something it doesn't work. (ctrl+shift+LMB)

Exact steps for others to reproduce the error
For instance:Add a noise texture and connect the factor to the displacement output,now click ( ctrl + shift + LMB) the color output view correctly but if you try to view the factor it wont work.

**System Information** Windows 10,AMD 5450 **Blender Version** Blender 2.77,Hash: 22a2853 **Short description of error** When I try to view an output using the node wrangler addon when it is already connected to something it doesn't work. (ctrl+shift+LMB) **Exact steps for others to reproduce the error** For instance:Add a noise texture and connect the factor to the displacement output,now click ( ctrl + shift + LMB) the color output view correctly but if you try to view the factor it wont work.

test commented

2016-03-22 19:43:04 +01:00

Changed status to: 'Open'

test commented

2016-03-22 19:43:04 +01:00

Added subscriber: @omar-1

Olson Burry commented

2016-03-22 22:01:43 +01:00

Added subscriber: @OliverBurn

Olson Burry commented

2016-03-22 22:01:43 +01:00

This comment was removed by @OliverBurn

*This comment was removed by @OliverBurn*

Mai Lavelle commented

2016-03-22 23:13:22 +01:00

Added subscriber: @MaiLavelle

Mai Lavelle commented

2016-03-22 23:13:22 +01:00

I'm also experiencing a problem here, node wrangler seems to be skipping sockets at random if one is connected to the displacement output.

Greg Zaal was assigned by Brendon Murphy

2016-03-23 00:08:22 +01:00

Olson Burry commented

2016-03-23 00:08:32 +01:00

I see now the issue too, it's skipping the socket that's connected to the Displacement for whatever reason.

It's easier to see if using Separate RGB for example and plugging G to displacement of material output.. ctrl + shift + clicking selects R and B in turn but G is never connected to the viewer

I see now the issue too, it's skipping the socket that's connected to the Displacement for whatever reason. It's easier to see if using Separate RGB for example and plugging G to displacement of material output.. ctrl + shift + clicking selects R and B in turn but G is never connected to the viewer

Brendon Murphy commented

2016-03-23 00:21:19 +01:00

Added subscriber: @BrendonMurphy

Brendon Murphy commented

2016-03-23 00:21:19 +01:00

hi please check that the recently updated file has same issue: https://developer.blender.org/diffusion/BA/browse/master/node_wrangler.py
Looking at https://developer.blender.org/T47832 it seems this did not make it into release & may need to be forwarded to any 2.77 'a' release.

hi please check that the recently updated file has same issue: https://developer.blender.org/diffusion/BA/browse/master/node_wrangler.py Looking at https://developer.blender.org/T47832 it seems this did not make it into release & may need to be forwarded to any 2.77 'a' release.

Mai Lavelle commented

2016-03-23 01:42:49 +01:00

The updated file still has this issue