Page 1 of 2
Request: Node Support
Posted: Mon May 18, 2015 11:53 am
by agentwd40

Blender has support for nodes. How about some material love for nodes?
Re: Request: Node Support
Posted: Mon Jun 08, 2015 2:18 am
by Headroom
While there is nothing wrong how materials are set up right now but node support would be great. This must be one of the top requests for the Blender exporter interface.
+100
Sent from my iPad using Tapatalk
Re: Request: Node Support
Posted: Sat Jan 23, 2016 3:35 am
by Eneen
+100
Re: Request: Node Support
Posted: Tue Jan 03, 2017 11:37 pm
by thednx
Very cool feature request indeed.
Re: Request: Node Support
Posted: Wed Jan 04, 2017 4:16 am
by burnin
wooow

YES!
One of best examples is how Pixar's team did it with their
PRMan-for-Blender exporter for the 21.2 NC release...

... as if seamless integration within blender, amazing
Re: Request: Node Support
Posted: Thu Jan 05, 2017 7:30 am
by SreckoM
With this dev speed I hope we will get it in 2018 ...
Re: Request: Node Support
Posted: Thu Jan 05, 2017 8:25 am
by Eneen
Every vote matters!
Re: Request: Node Support
Posted: Thu Jan 05, 2017 11:17 pm
by Originalplan®
SreckoM wrote:With this dev speed I hope we will get it in 2018 ...

It will come soon enough... just give them a bit time to build something that gives you actually more speed and not just a node base. IMO right now only one application did master the node base in an almost perfect way and that is Houdini. The rest like Arnold etc is not very well thought out (could be better) at least on c4d integration side.
Re: Request: Node Support
Posted: Thu Jan 05, 2017 11:20 pm
by Oscar J
I think SreckoM is referring to the Blender exporter. It's fair to say that the development is very slow currently.
Re: Request: Node Support
Posted: Thu Jan 05, 2017 11:35 pm
by Originalplan®
Oscar J wrote:I think SreckoM is referring to the Blender exporter. It's fair to say that the development is very slow currently.
Ah Ok. Not very familiar with the Blender update cycle...C4D's is awesome.
Re: Request: Node Support
Posted: Fri Jan 06, 2017 12:34 am
by SreckoM
Exactly, was talking about Blender plugin. As a matter a fact except C4D and Maybe Sketchup? exporters development is dead. Which is wrong strategy imho. Nowadays ppl favour mostly workflow. What would I bother with 15% gain in render speed if I lose 50% speed in workflow. Also I am actively involved into workflow so it is even more annoying. Just look where Arnold is now and why even CPU and slower than Indigo is so widely adopted compared to it. Also Redshift, both much younger.
Re: Request: Node Support
Posted: Fri Jan 06, 2017 1:40 am
by Originalplan®
SreckoM wrote:Exactly, was talking about Blender plugin. As a matter a fact except C4D and Maybe Sketchup? exporters development is dead.
Hmm... i did not know that. Didn't we had some job listings for it? Hope someone is skilled enough to take up the challenge for less than a bag of $/month.
SreckoM wrote:Which is wrong strategy imho. Nowadays ppl favour mostly workflow. What would I bother with 15% gain in render speed if I lose 50% speed in workflow.
Yep agreed that's why i said that is better to leave it a bit time to get it right. Rather than just have a node base which consumes more time than the classic way. Anyways it's not a small challenge design wise. Neither for the main app and neither for the plugins. You see / host app SDK's there are some style and integration restrictions you can't really just simply overcome. Like Arnold on c4d uses the Xpresso window which is basically the only way to get a simple integration but also has it's downsides. I'm really n favor of a separate Mat editor which features Nodes and a fast workflow outside the host app.
SreckoM wrote:Also I am actively involved into workflow so it is even more annoying.
SreckoM wrote:Just look where Arnold is now and why even CPU and slower than Indigo is so widely adopted compared to it. Also Redshift, both much younger.
Well it's a whole nother topic. I think the adoption for those """""Industry standard"""""" renderers are just simply the timing/release year and feature set. What i mean exactly is that right now Indigo is crazy fast ( super proud of the guys who did it ) BUT it's not very versatile in ONE SINGLE WAY and that is VFX. It can't do hair and it can't do smoke....
and it's really simple as that. Once we get those inside Indigo with the same speed you will see a rise in user and studio base. Right now i think Indigo has two big paths one is
architecture viz and another is
product visualization.
But not VFX it's still down the road but once it will support smoke, hair etc etc...i think it can and maybe will be bigger than those engines you mentioned above or at least on the same level as them now. From a studio stand point more and more are investing in GPU render farms in house. And if you calculate cost usage etc...maybe you are better off with a super fast OpenCL renderer and not lock yourself into only using Nvidia cards and a much expensive renderer.
Of course it's much harder to turn the big studios but time will tell. Anyways let's do a separate topic on this i'm pretty curious what people thing about this matter.
PS: Hope you get a Blendigo update soon.

Re: Request: Node Support
Posted: Fri Jan 06, 2017 1:58 am
by SreckoM
Market is way too competitive nowadays, so waiting is not alternative

My company already went different route.
Also interesting to see
http://www.cgarchitect.com/2016/11/2016 ... ---results
Re: Request: Node Support
Posted: Fri Jan 06, 2017 6:50 am
by Eneen
@Originalplan®:
I don't have such experience regarding nodes, but they seem to me easier and faster to use due to better control of what I have inside material, specially when blend one is used.
Blender plugin doesn't even now have mat preview so you know...
Re: Request: Node Support
Posted: Fri Jan 06, 2017 7:11 am
by Originalplan®
Eneen wrote:@Originalplan®:
Blender plugin doesn't even now have mat preview so you know...
What do you mean it does not have a mat preview?
Ok downloading Blender now + Blendigo to have a look at the situation.
