- User Since
- Nov 8 2010, 11:53 PM (427 w, 4 d)
Feb 23 2018
Apr 30 2015
Thanks for the report. We'll take a look at it and hopefully solve it shortly.
Mar 30 2015
Mar 27 2015
Mar 26 2015
Mar 24 2015
Mar 23 2015
Mar 19 2015
Mar 18 2015
Mar 16 2015
Mar 15 2015
Mar 13 2015
Checked it and indeed there is an issue. I don't yet know how to solve it, but will check on it. Thanks for letting me know.
Feb 27 2015
Nov 20 2014
Oct 21 2014
Brought back Node Wrangler to Blender Render material nodes and to texture nodes.
Improved behavior in those tree types.
You are absolutely right.
I didn't even think about using Node Wrangler in Blender Render and thought that having it enabled there causes more problems than advantages.
Made some tests and it seems that many options work there just fine. I understand you 100%. The tool had flows in those modes, but worked in many cases.
Oct 20 2014
I made a decision about disabling it for texture nodes and nodes for internal render engine, because I was once asked why cycles nodes get added to internal materials.
Because it was never my intention to make the add-on work for texture nodes and internal material nodes, I made a simplest decision to avoid confusion: disable it in modes it's not intended to work with.
It's great that we can collaborate this way, have feedback from other users. I admit that it didn't even cross my mind that Node Wrangler could anyhow be useful in texture nodes or when creating blender internal's material nodes.
Bringing it back is not a big issue, but before I decide to do it, let me think of some way not to have issues with add-on trying to add not correct nodes.
Node Wrangler is designed to work ONLY on compositing nodes and cycles material nodes.
There is no functionality of Node Wrangler in texture nodes nor in blender's render material nodes.
That's why this is disabled in those modes.
This behavior is set like this in purpose.
Sep 10 2014
Fixed. Thanks for pointing those bugs out.
Got it. I will take care about it shortly.
At first I will fix behavior with hidden sockets.
As for material nodes for Blender Render: The add-on is not intended for material nodes in Blender Render. I will add restriction that will disable it when working with Blender Render material nodes.
Aug 25 2014
Thank you Greg.
I will get in contact with Greg who wrote this part of the add-on. If he can't take care about it for any reason - I will. Thanks.
Aug 11 2014
@Czarek Kopias (kopias):
Lazy Connect: Yes, we noticed this. Will try to fix as soon as possible.
Extended F6 dialog: This is not a bad idea. Some of us (included me) use F6 pretty heavily, so I think that it IS worth some coding effort. I will take a look at it and try to think about the possibilities.
BTW: When you go to User Prefs and open Node Wrangler you can set some preferences. One of them is that newly added "Mix" nodes (Alpha Over included) can be by default hidden or not. If you want them unhidden - you can change the setting.
Aug 7 2014
Mar 19 2014
Here is an updated version:
Nov 19 2013
Nov 18 2013