thanks bonsak!
I had CVEX code from earlier. Indeed it does feel hacky to use a SHOP network in a OBJ network but at least placing the SHOP network on the same level helps some of the back and forth.
For future readers:
The CVEX's parameters appear on the CVEX node in the SHOP and not the VOP in the object network. The CVEX code also needs to define the variable in the code from the pragma otherwise a warning is thrown. The variables are passed into the CVEX function via function arguments. See the screenshot for example.
Useful VEX pragmas: http://www.sidefx.com/docs/houdini15.0/vex/pragmas [sidefx.com]
Found 3 posts.
Search results Show results as topic list.
Technical Discussion » CVEX interface
- yaz
- 3 posts
- Offline
Technical Discussion » CVEX interface
- yaz
- 3 posts
- Offline
@bonsak, can Geometry Operator create geometry? I tried the following snippet without any luck.
sop test()
{
printf(“hello world”);
int p1 = addpoint(geoself(), {0,0,0} );
}
sop test()
{
printf(“hello world”);
int p1 = addpoint(geoself(), {0,0,0} );
}
Technical Discussion » CVEX interface
- yaz
- 3 posts
- Offline
Hey,
How do I add an interface to a CVEX Operator like how a VEX can take ch(..) inputs?
And why are CVEX nodes created in a SHOP and not in Object network directly (instead of via Attribute VOP)?
Thanks!
How do I add an interface to a CVEX Operator like how a VEX can take ch(..) inputs?
And why are CVEX nodes created in a SHOP and not in Object network directly (instead of via Attribute VOP)?
Thanks!
-
- Quick Links