<div>Hi Brecht,</div>I just noticed this commit go in today:<div><br></div><div><span style="background-color:rgb(255, 255, 255)">"<span style="font-family:monospace;font-size:12px;white-space:pre-wrap"><font color="#333333">Cycles: replace surface/volume sockets in output nodes with a single shader socket,</font></span></span></div>
<span style="font-family:'Lucida Grande', 'Lucida Sans Unicode', 'Lucida Sans', Lucida, Verdana, sans-serif;font-size:12px;background-color:rgb(255, 255, 255)"><pre><font color="#333333">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."</font><font color="#efefef">
</font></pre><div style="color:rgb(239, 239, 239)">"</div><div>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.</div>
</span>