What is the point of using a ramp in VOPs if you need to control things with a ramp at the sops level? Does the ramp curve set within vops even do anything?
In Houdini 20.5 it’s odd because I’m following along but adjusting my ramp curve on the Attribute VOP node adjusts all the buildings together and they are only affected by changes to the ramps uppermost value (furthest right) but not even the small buildings are affected by changes to the curve in the lower ranges.
I immediately fixed the curve not responding by correcting the Fit Range destination mapping to [0 1] (by mistake I had [10 0]).
However the purpose of a Ramp Parameter node in VOPs (with a ramp curve in the parameter window) makes no sense to me if it then needs to be controlled at a level above in SOPs. What would happen if we wanted to use 2 or 3 or even 10 ramp parameters within a VOPs network?
Hey Dave, yup, we know this is a strange way to do a ramp, but this is how Houdini does it. The motivation behind it is to build a very complex setup inside the vop, but to use it, you just have to interact with a couple simple parameters on the vop itself. Adding more than one ramp however is quite simple: Just make sure you have a different name parameter on each ramp node (this should be the case by default) and Houdini will simply create multiple of those ramps on the VOP node with that same name.
Thanks! I see so by default ramps are exposed for fine tuning in the network above.
Is it possible to expose other parameters from within VOPs? Would this be done by selecting ‘Promote Parameter’ from the gear icon? And so with this terminology the entire ramp graph and it’s parameters are promoted by default?
If this is the case it then makes more sense to me because we want the entire graph and not just parameters to be promoted.
Unlock with Patreon
What is the point of using a ramp in VOPs if you need to control things with a ramp at the sops level? Does the ramp curve set within vops even do anything?
In Houdini 20.5 it’s odd because I’m following along but adjusting my ramp curve on the Attribute VOP node adjusts all the buildings together and they are only affected by changes to the ramps uppermost value (furthest right) but not even the small buildings are affected by changes to the curve in the lower ranges.
I immediately fixed the curve not responding by correcting the Fit Range destination mapping to [0 1] (by mistake I had [10 0]).
However the purpose of a Ramp Parameter node in VOPs (with a ramp curve in the parameter window) makes no sense to me if it then needs to be controlled at a level above in SOPs. What would happen if we wanted to use 2 or 3 or even 10 ramp parameters within a VOPs network?
Hey Dave, yup, we know this is a strange way to do a ramp, but this is how Houdini does it. The motivation behind it is to build a very complex setup inside the vop, but to use it, you just have to interact with a couple simple parameters on the vop itself. Adding more than one ramp however is quite simple: Just make sure you have a different name parameter on each ramp node (this should be the case by default) and Houdini will simply create multiple of those ramps on the VOP node with that same name.
Thanks! I see so by default ramps are exposed for fine tuning in the network above.
Is it possible to expose other parameters from within VOPs? Would this be done by selecting ‘Promote Parameter’ from the gear icon? And so with this terminology the entire ramp graph and it’s parameters are promoted by default?
If this is the case it then makes more sense to me because we want the entire graph and not just parameters to be promoted.
Exactly! For all other parameters there’s a “parameter” vop node. Again just specify a name and a datatype and you should be golden.