[Bf-cycles] A Single "Cycles" Shader

Agustin Benavidez agustinbenavidez at gmail.com
Thu Mar 29 01:28:21 CEST 2012

Christophe , You are right, simplicity, faster workflow, and
powerful possibilities is what all tools are meant to be, and in my opinion
Brecht with His design is going straight in that direction, the issue right
now is that work is still in progress, with Cycles you got
powerful possibilities and faster workflow, only left is more simplicity,
and that is part of the final stage where all those modular
and powerful tools can be group together in simple to use presets and group
nodes. I think what is really lacking to fulfill your need is an Asset
Manager, where you can save your custom nodes setup, presets, images,
meshes , label at will and re use them easily, while at the same time
maintain and extend the low level/flexible workflow .


2012/3/28 Christophe Leyder <shotalot at gmail.com>

> Hey Brecht,
> Im really loving how Cycles is coming along, but I have a slight concern
> about the direction the shading workflow is taking.
> Currently, in the materials tab, the shaders presented with Cycles feel
> very "technical" and un-artist friendly, let me explain why:
> "Glossy BSDF", "Transparent BSDF", "Transcusent BSDF", "Diffuse BSDF" to
> me as an artist should be parts of a shader, not individual shaders.
> To elaborate, from using a whole lot of other engines these past few
> years, the one thing they have in common is they have unification.
> Unfication in Blender in general is seriously lacking, and I would hate to
> see Cycles go even further down that road. My suggestion is:
> Have a "basic" shader with the current "shaders" combined, (I really dont
> know the maths and stuff behind this though). Rather have the current
> scattered system as inputs in the nodes system, because by all means, they
> WILL be usefull there, if someone wants to use them individually, they can
> plug them straight into the material output. To add, in my experience, a
> Mix shader shouldnt be a "shader" at all, rather a function in the node
> tree. eg. Changing the colour of a texture, or placing a decal on a shader;
> and of course what it does now, mixing shaders.
> Or to be even safer, just add the "basic" shader to the materials list
> thats already there, and leave the shaders that are there as is.
> Just my 2 cents from an artists standpoint! :)
> Thanks
> --
> *Christophe Leyder*
> *3D Artist\Animator*
> **
> www.luma.co.za
> _______________________________________________
> Bf-cycles mailing list
> Bf-cycles at blender.org
> http://lists.blender.org/mailman/listinfo/bf-cycles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-cycles/attachments/20120328/b0a5c2be/attachment.htm 

More information about the Bf-cycles mailing list