-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RenderMan coshaders #72
Conversation
…nto the GafferScene::Shader base class. Registering an appropriate Nodule creator for RenderManShader so that only coshader parameters appear in the node graph.
So I looked it over and don't see a problem, but I also know almost Also, any chance we can get pull request emails to differentiate Andrew On 04/01/2013 06:40 PM, John Haddon wrote:
|
I'm pretty happy with this one so we can just merge it. I'll come over and go through it with you though because I want to see what this "cannot be automatically merged" thing is all about. I've had a look around, and can't see anything to differentiate pull request emails from issues...if you find something feel free to activate it... |
I've merged the changes manually. |
This pull request implements support for building networks of RenderMan coshaders, addressing issue #39. Coshader parameters are represented simply as the base Plug class, because conceptually they're just a connection which doesn't provide data directly. RenderManShader::acceptsInput() is implemented to ensure that only other RenderManShaders are connected as coshader inputs, and that shaders cannot be connected to inputs other than those representing coshader parameters.
Also took the opportunity to tidy up existing shader ui registrations while defining the ui for the RenderManShader.