[Bf-cycles] Please Give Us Back Volume&Surface Combos

[Brecht Van Lommel]

Hi,

On second though I've just reverted the commit. It might make it a bit
too difficult to understand for the user what's going on and how you
should mix shaders...

Brecht.

On Thu, Oct 13, 2011 at 12:05 AM, Brecht Van Lommel
<brechtvanlommel at pandora.be> wrote:
> Hi,
>
> This change will not limit what is possible to render, it will only
> require a different shader setup. Volume rendering will still support
> using a different shader with a BSDF at the surface. Probably a node
> will be added to make this kind of setup easier, but an Add Shader
> node might already work for now... it depends a bit on how volume
> rendering will interpret closures.
>
> Layering again is something that can be done with nodes, rather than
> adding sockets. I rather have this sort of thing as nodes, so that you
> can put it in a node group and use entirely as preset, or mix it with
> another group.
>
> Brecht.
>
> On Wed, Oct 12, 2011 at 10:55 PM, Michael Fox <mfoxdogg at gmail.com> wrote:
>> On 13/10/11 06:22, Kel M wrote:
>>
>> Hi Brecht,
>> I just noticed this commit go in today:
>> "Cycles: replace surface/volume sockets in output nodes with a single shader
>> socket,
>>
>> decided it's better to render objects as either surface or volume.
>>
>> This may break the volume rendering patch, but shaders with volume closures
>> still
>> get tagged as having volume closures, so it should be fixable without too
>> many
>> changes."
>>
>> "
>> The ability to render an object with both a surface and a volume shader was
>> a selling point of Cycles. It's how swimming pools must be rendered. I'm
>> asking you to please revert this commit, I was able to make a bunch of
>> beautiful ice sculptures with the volume patch because Cycles allowed both
>> Surface and Volume on the same object.
>>
>> _______________________________________________
>> Bf-cycles mailing list
>> Bf-cycles at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-cycles
>>
>> i agree with this, you shouldn't be taking away slots as it takes away the
>> flexibility that was a cornerstone of the nodal workflow when it was
>> designed if anything we need to add the ability to add more sockets, like
>> more displacment values and surface and volume so we can layer shaders
>> rathur then mix or add them
>>
>> _______________________________________________
>> Bf-cycles mailing list
>> Bf-cycles at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-cycles
>>
>>
>