Author: admin

Archived post by JeffLMnT

here I’m calling the vex source from the `noise` wrangle – and it’ll run that vex snippet on the vop

so I can just change the `noise` wrangle and every other vop that points to it will also pull the change

the vop also has other modes like the script mode if you’re interested – so if you have a CVEX snippet on disk, you can point to that <:chef:730208016174940172>

here’s that file – you can do the same thing with vex > vop, vop > vop

Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20233205/10/23/image.png
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20233205/10/23/vex_shop_mode.hiplc

Archived post by JeffLMnT

was curious to see if the loop idea was just something I pulled out of my ass — and its not! lol

here’s the same applied in a loop and driven with a multiparm – @flight404

you can probably also add a switch and promote it as a toggle

and use the to enable/disable conditions

Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20231505/07/23/stack_vex_conditions_loop.hiplc
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20231505/07/23/image.png

Archived post by Ambrosiussen

You can actually drive all parms automatically on a node with the dictionary generated from attribfromparms

No python needed

1 Create a detail dict using attribfromparms called `parms` with parameter values. (Name is important) 2 Create a spare input on the node which you want to drive the parms for. Set it’s value to be the node you have your parms dict attribute on. 3 Create an integer parm called `spare_parminputindex` and set it to -1 (to point at the spare input connection)

Profit!