Render pass in lw

[geo_n]

I think maybe we can talk about some issues in lw section. It might be confusing for other if we include lw issues(matte vs shadowcatch name) like in that main thread.


My first issue, it doesn't have proper way to assign mat,obj id afaik such as this which is a big help when I use 3dmax.




So If lightwave can support two ways of masking and also the ability to assign mat/obj ids manually because sometimes random assignment doesn't work. Like this object id mask will not work



It would be great to support by exr(rgb channels) or by rpf(non-image channels, lw has this afaik).

3dmax, Vue, etc have support for assignable mat/obj ids.

I attached typical Exr which have rgb mat/obj ids. AE, etc can see the mat/obj channels.
Another file is rpf. This is much better because it has Coverage info.

I've been asking coverage buffer in newtek for a long time but nothing.
Since octane is completely independent renderer maybe its possible to have this and also the ability to assign mat/obj ids manually as an option via nodes. Maybe Juanjo can do magic with the lw sdk.

[juanjgon]

As far I know currently Octane doesn't support custom values in the objectID and materialID passes. This is something that can't be done in the the plugins if Octane doesn't support it.

-Juanjo

[geo_n]

Yes this is very important to have custom or manual way to assign ids, tags.
All appz have it. 3dmax, c4d, etc. Lightwave doesn't have this and that's why we are stuck with assigning matt objects(not to be confused with matte node function and why it has shadows in it, lol) . constant black, etc.

I'm hoping they add custom or manual way to standalone and requested it in main thread.

If they add it to standalone(surely they must because other appz have it natively), then lightwave might get this functionality. Compositing appz(nuke, fusion, etc) can read these channel id/tags embedded in exr as well as the coverge buffer. After that I'm pretty much all set for this issue regarding matt/masking.

[geo_n]

Regarding lightwave obj/matt id, matt obj, constant value, constant black, etc and other workarounds.

Skip to 2:40 it similar to constant value, constant black but with more flexibility. This is a more general way of working in most appz with proper implementation of obj/matt id.
https://www.youtube.com/watch?v=kpZr66d0g9U