In the type properties panel I see there is a new entry in “Create Parameters” / “By Type”:
Data
I imagine this is for “Blind Data”?
How is this new “Data” retrieved and accessed?
h15 data parameter in type properties
7133 5 0- josh3light
- Member
- 120 posts
- Joined: Feb. 2008
- Offline
- pwquint
- Member
- 53 posts
- Joined: Aug. 2009
- Offline
- josh3light
- Member
- 120 posts
- Joined: Feb. 2008
- Offline
Yes, and now in the parameter interface there is a “Data” parameter that can be added. Yet there are no options to set anything in the interface once added. This appears to be new in H15.
Attached is a screen-shot of what I'm referring to.
I'm wondering if this parameter is:
- for storing data which is “blind” (or unknown/unrecognized by houdini, yet useful for cooperating with 3rd party libraries etc),
- if there are python or hdk commands to set and retrieve such data
- and what the motivation and use case for this “Data” parameter could be
Attached is a screen-shot of what I'm referring to.
I'm wondering if this parameter is:
- for storing data which is “blind” (or unknown/unrecognized by houdini, yet useful for cooperating with 3rd party libraries etc),
- if there are python or hdk commands to set and retrieve such data
- and what the motivation and use case for this “Data” parameter could be
- tamte
- Member
- 8780 posts
- Joined: July 2007
- Offline
you can store and retrieve geometry to that parameter
so if dataparm is your Data Parameter
and sopnode is some sop node containing geometry you want to store in the Data Paremeter you can do
dataparm.set(sopnode.geometry())
then at any point to get that geometry you do
dataparm.eval()
or
dataparm.evalAsGeometry()
EDIT: and the motivation is probably to provide fast and flexible way to cache arbitrary data (well, at least geometry) for your tools in order to avoid slow and dangerous workaround using editable nodes and node locking within HDAs
so if dataparm is your Data Parameter
and sopnode is some sop node containing geometry you want to store in the Data Paremeter you can do
dataparm.set(sopnode.geometry())
then at any point to get that geometry you do
dataparm.eval()
or
dataparm.evalAsGeometry()
EDIT: and the motivation is probably to provide fast and flexible way to cache arbitrary data (well, at least geometry) for your tools in order to avoid slow and dangerous workaround using editable nodes and node locking within HDAs
Edited by - Nov. 21, 2015 13:42:15
Tomas Slancik
FX Supervisor
Method Studios, NY
FX Supervisor
Method Studios, NY
- josh3light
- Member
- 120 posts
- Joined: Feb. 2008
- Offline
- derrick
- Staff
- 329 posts
- Joined: July 2005
- Offline
tamte
and the motivation is probably to provide fast and flexible way to cache arbitrary data (well, at least geometry) for your tools in order to avoid slow and dangerous workaround using editable nodes and node locking within HDAs
Yes, one of the main goals for the Data Parameter is to provide a better alternative to editable nodes in an HDA. You can see an example of it in use in the Curve Groom SOP. In that HDA, the “Cache Strokes” button (an invisible parameter) is used to store some geometry in a data parameter and a Python SOP in the HDA makes use of the stored geometry.
-
- Quick Links