This does ring some bells now. I think it was part of one of our big refactorings of shaders and we were thinking of exploring a model where the renderer would be able to pull on only certain outputs.

It can vary depending on the renderer. I believe Arnold and 3dsmax use the texture coordinates, but Prman has historically used the surface parameterization. Are you thinking you would need the baryce

I believe we have defined "N" to always point toward the incoming ray. This is usually what you want for shading calculations. You can use the "backfacing()" function to find out if you actually hit t

Ok I've canceled the next two TSCs since they aligned with holidays. Enjoy the time off and see you all on Dec 9th :)

Two thumbs up from me! This is really great work. Thank you so much for all your effort on this, I'm really happy with how this turned out.

Sounds good to me as well. I will cancel the invite for this week then.

Hi Patrick, Just to clarify, Larry's suggestion about using "transformc" is what is currently implemented in OSL (though it is an optional feature that only works if you compile with OCIO as a depende

I'm really liking #3 -- ties into the shaded sphere and nodegraph ideas at the same time (and even half-tone dots to some extent). #1 reads a bit too much like CSL for me #2 I like the leftmost one, t

Hi Elizabeth, I think getmessage is probably not the easiest way forward here. Generally we try to avoid calls that require holding onto state as much as possible (the trace call and getmessage being