new bug in commit "improved cryptomatte handling"

#1 · 3. February 2019, 17:43

Hello,

you replaced this line :

parm.setExpression(expression, hou.exprLanguage.Python)

with

parm.set(outPut)

in the previous commit for cryptommate handling, the code isn't python anymore and isn't updating the filename per frame

that resulted in every AOV to override the same frame number (the one when submitting ), that make all render unusable.

#2 · 4. February 2019, 1:01

True, I should have looked at it twice.

Fixed now.

#3 · 17. February 2019, 17:12

Hello, tried the fix today, most of the AOV seem to have the correct, but not the cryptomatte :

O:/NetworkedWorkspace/03_Workflow/Shots/ShortAnimation-Bilby/Rendering/3dRender/SFW/v0001_nocomment/$AOV/shot_ShortAnimation-Bilby_SFW_v0001_$AOV.$F4.exr

the $AOV isn't replaced by cryptomatte and end up with folder named xxxxxx/$AOV/

also, I think prism should take care of removing any key in the AOV parameter to keep everything uniform, I got a mix of purple parameter and non-keyed black parameter! (happen when prism was updated)

#4 · 17. February 2019, 23:36

The keyframes on the outputpath parameters are the reason why $AOV wasn't evaluated. The new Prism version doesn't set keyframes for this parameters anymore. I just uploaded a fix, which makes sure there are no keys from previous Prism versions left.