Hi, pardon me if this is a dumb question, but according to the documentation on the Lighting Model VOP (http://www.sidefx.com/docs/houdini11.1/nodes/vop/lmodel) [sidefx.com] there are several documented outputs such as diffclr, ambclr, etc. However, the default output of the Lighting Model node is only color and BSDF. How does one access those other outputs?
Thanks.
Lighting Model Operator Outputs
3435 5 1-
- faulknermano
- Member
- 11 posts
- Joined: Dec. 2011
- Offline
-
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
-
- faulknermano
- Member
- 11 posts
- Joined: Dec. 2011
- Offline
Hi Rob, thanks for the help. I'm a bit surprised to find that the output refers to the ROP context.
My original plan was to boost or attenuate the pre-computed values such as ‘diffclr’ on their own just before they get piped into Cf in the shading network.
Do you an idea how to go about this in the most direct way? Thanks again.
best,
lernie.
My original plan was to boost or attenuate the pre-computed values such as ‘diffclr’ on their own just before they get piped into Cf in the shading network.Do you an idea how to go about this in the most direct way? Thanks again.
best,
lernie.
-
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
Hi lernie,
Well thats where you can call them to be rendered. If you want to roll your own outputs > Drop a mantra surface shader > dive inside > find the surface model VOP > RMB unlock the asset > dive inside, there you will find the lighting loop and all the parameters set to export.
The only warning I will issue is that the surface model is a asset so unlocking and saving will screw up defaults. You are best using the otl manager <access from RMB menu over the vop> to make a copy of the vop then you can hack around with it.
Good luck
Rob
Well thats where you can call them to be rendered. If you want to roll your own outputs > Drop a mantra surface shader > dive inside > find the surface model VOP > RMB unlock the asset > dive inside, there you will find the lighting loop and all the parameters set to export.
The only warning I will issue is that the surface model is a asset so unlocking and saving will screw up defaults. You are best using the otl manager <access from RMB menu over the vop> to make a copy of the vop then you can hack around with it.
Good luck
Rob
Gone fishing
-
- faulknermano
- Member
- 11 posts
- Joined: Dec. 2011
- Offline
Copy that.
So it's the surface model VOP after all.
I'm also thinking of using two or more lighting model VOPs to separate out the resulting responses (by dialing down the appropriate inputs), then process individually, then mix them in together before going out.
It's a bit of a hack, so I'm eager to have a look at the surface model node soon and see if there's something more elegant.
Thanks again.
best,
lernie.
So it's the surface model VOP after all.I'm also thinking of using two or more lighting model VOPs to separate out the resulting responses (by dialing down the appropriate inputs), then process individually, then mix them in together before going out.
It's a bit of a hack, so I'm eager to have a look at the surface model node soon and see if there's something more elegant.
Thanks again.
best,
lernie.
-
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
-
- Quick Links

