{"id":2266,"date":"2017-01-03T21:35:36","date_gmt":"2017-01-03T21:35:36","guid":{"rendered":"http:\/\/julius-ihle.de\/?p=2266"},"modified":"2018-04-04T08:38:56","modified_gmt":"2018-04-04T08:38:56","slug":"osl-3d-shading-masks","status":"publish","type":"post","link":"https:\/\/julius-ihle.de\/?p=2266","title":{"rendered":"Playing with OSL #1: 3D Shading Masks"},"content":{"rendered":"

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

I have recently started getting into Shader Writing in OSL (actually rather Pattern Writing just to not get frustrated too quickly :-) ). To start things off I wrote a simple Pattern that lets you create a life 3d mask in your shading network that can be used to alter different shading effects in very particular areas of an object without the need to paint texture masks. On top of that being OSL it should work in any renderer that supports it (e.g. PRMan\/RIS, Cycles in Blender, VRay, etc).<\/p>\n

<\/p>\n

The Pattern itself only has a few simple controls:<\/p>\n

\"osl_pmask_ui\"<\/a>
PMask OSL Pattern inside Maya with RenderMan (PxrOSL Node)<\/figcaption><\/figure>\n

 <\/p>\n

Here’s a quick explanation:
\nMapping<\/span> – determines whether to use world- or object-space for the 3d mask (choose PWorld<\/em> or PRef<\/em>). Unfortunately the PxrOSL node in Maya ignores shader metadata for creating a nice dropdown menu here (Blender users might be luckier :)).
\nRadius<\/span> – The X, Y, Z (-> R, G, B) scale of the spherical mask.
\nWhitepoint<\/span> – Values below 1 will move the core towards the outside edge
\nBlackpoint<\/span> – Values above 0 will move the outside edge towards the core
\nGamma<\/span> – Can be used to increase or decrease the falloff<\/p>\n

All of these parameters are mappable, too! In the case of this Tool this has some very nice benefits.<\/p>\n

The first one is that you can create a locator for example and map its translation to the Pos input. If you are using PWorld<\/em> as your Mapping type it will use the world space coordinates so wherever you move the locator the mask will go as well. However assuming you are not animating the locator this will be a static mask in worldspace and any objects which are animated will swim through the mask.
\nIf you want your mask to follow your object you can set the Mapping to PRef<\/em>. This will use the coordinates of the objects translation and deformation from a reference position (zero’d out transforms) and will make the mask stick to the object wherever it’s going. Keep in mind that the Origin for the position (0,0,0) is always wherever the object has zero’d out transforms. This means that you might need an offset if you have frozen your transforms at one point. Another alternative would be to parent or constraint a locator to a moving object and leave the Mapping set to PWorld<\/em>.
\nTo double-check the coordinates the OSL node allows you to output PWorld<\/em> and PRef<\/em> for debugging purposes (you can take the RGB color values of a point in the render as your Pos value).<\/p>\n

Also most of the time a simple sphere is not very desirable, so you can also map the radius with other procedurals or textures to break up its shape.<\/p>\n

Because this is based on position data it’s completely independent of the object’s UV’s.<\/p>\n

You can download it HERE<\/a>.<\/p>\n

Here’s a quick demo video:
\n