I've been testing out the wedge ROP and am running into an issue with the $WEDGE (and $WEDGENUM) variable in my output picture parameter of the target Output Driver.

If I type in $WEDGE_ in the filename it turns to a red color and during render time it does not expand (it does not expand if I middle click on the Output Picture field either). However, if I put single or double quotes around the $WEDGE it turns green and works fine, except I get double quotes in the filename which is not desirable. Dots over an underscore seems to work, as in: $WEDGE.$WEDGENUM_$F4.exr, but I'd like to know why this doesn't work:
$WEDGE_$WEDGENUM_$F4.exr

thanks
z

you could always put the variables in spare parameters on the output driver and call those with the chs() expression. To why this doesn't work in this case I'm not sure, although I've seen people using the syntax `{$WEDGE}` before, don't have Houdini in front of me right now, but you should give it a try!

cheers,

Manu

ah great, thanks for that, ${WEDGE} worked! didn't know you could use syntax like that. awesome.

asnowcappedromance
you could always put the variables in spare parameters on the output driver and call those with the chs() expression. To why this doesn't work in this case I'm not sure, although I've seen people using the syntax `{$WEDGE}` before, don't have Houdini in front of me right now, but you should give it a try!

cheers,

Manu

zephyr707
I'd like to know why this doesn't work:
$WEDGE_$WEDGENUM_$F4.exr

Underscores are allowed in variable names, so without the braces {} to explicitly delimit the name, it thinks the variable name is $WEDGE_ (with an underscore).

I see, that makes a lot of sense now, did not know variables could have underscores in them! I always assume houdini knows what it is doing, but only occasionally understand why at this stage

many thanks for the info,
z

edward
Underscores are allowed in variable names, so without the braces {} to explicitly delimit the name, it thinks the variable name is $WEDGE_ (with an underscore).