{"id":2788,"date":"2021-09-15T19:42:58","date_gmt":"2021-09-15T19:42:58","guid":{"rendered":"http:\/\/julius-ihle.de\/?p=2788"},"modified":"2021-09-16T14:01:03","modified_gmt":"2021-09-16T14:01:03","slug":"playing-with-osl-5-arnold-reflection-alpha-utilities","status":"publish","type":"post","link":"https:\/\/julius-ihle.de\/?p=2788","title":{"rendered":"Playing with OSL #5: Arnold Reflection Alpha + Utilities"},"content":{"rendered":"

\"arnold_refl_aovs\"<\/a><\/p>\n

When trying to integrate CG renders into real life footage one common hurdle is to treat reflections properly. Often times in your plate you will have elements that have bright reflections (eg windows, plastic chairs, shiny tables, etc) in which your CG elements need to reflect. Rendering a simple reflection pass however often times does not really cut it<\/p>\n

<\/p>\n

See the example below. If you were to add a usual reflection pass to it the result does not really make sense:<\/p>\n

\"03_renderrefl\"<\/a><\/p>\n

This is because the reflection is simply added in this case. While adding reflections is technically correct, the problem is that we already have reflections in the plate. The window behind the table has a large contribution to the specular reflection on the table. If you look at the cup on the right what is happening is that the cups reflection is blocking the highlights from the window. As the cup is neither emissive nor very bright it’s reflection is a lot darker.<\/p>\n

We’d need to do something similar to the reflection of the CG render. A common trick is to render a separate reflection of the same element but with a constant white shader. This has several drawbacks tough:
\nMost renderers don’t support arbitrary utility outputs in traced results. This means the render would need to be a separate layer
\n–> more render layers to manage for the Lighting TD
\n–> longer rendering times
\n–> Comp has to deal with more separate renders
\n–> even more layers to manage if additional utility passes are requested (reflected Position, Normals, userdata, etc.)<\/p>\n

Ideally you would have the alpha and any additional arbitrary outputs as an AOV instead of a separate render to remedy all of the drawbacks mentioned above.<\/p>\n

 <\/p>\n

I therefore wrote a simple OSL shader. This however probably only works reliably in more recent versions of Arnold. You can assign it to your set geometry and anything that will reflect in it will sample whichever shading component you specify. This supports OSL builtins (eg P<\/code> and N<\/code>) as well as arbitrary userdata (eg Pref<\/code>). If you use dist<\/code> or distance<\/code> as a special keyword for the trace_component it will output the distance of the reflection from the current shading point, which can be used in comp to fake roughness. If the given component is not found it will reflect the trace_color<\/code> (eg to be used as an alpha for reflections).
\nIf your set geometry contains multiple shapes you can add them to a trace set and specify that same trace set in the shader and untick inclusive<\/code>. This will allow only reflections from your anything other than the set geometry.
\n\"\"<\/a><\/p>\n

The shader will output rgb data which means you can pipe it into custom AOVs for example with the help of aov_write<\/code> shading nodes:
\n\"\"<\/a><\/p>\n

With a little bit of comp love you can get quite promising results:
\n\"comp\"<\/a><\/p>\n

You can give it a whirl by downloading the jiTraceAOVs shader from my github<\/a><\/p>\n

Here’s a bit more indepth demo + a simple comp example:
\n