Taylor Petrick


About Me

Not Specified


Recent Forum Posts

Variable frame range for ROP Fetch Oct. 18, 2019, 12:28 p.m.

You can specify a range by setting Evaluate Using to “Frame Range”, and then entering an expression for the frame range. I've attached an example that wedges out random noise and frame range values, then cooks a target SOP node using a ROP Geometry with the frame range. Each wedge variation has its own unique range which is used to drive the Frame Range parameter on the ROP.

If the frame range information you need is in a file, you'll need to load that into PDG and get into an attribute on the work item. Your ROP Fetch can then access that attribute to set the frame range.

Rop Fetch with custom Rop Hda does not cook propperly Oct. 9, 2019, 1:59 p.m.

This looks like a bug on our end. The ROP Fetch isn't properly handling your node since it's actually a SOP, not a ROP. It ends up cooking the full frame range even though the ROP Fetch is configured to cook partial frame ranges in separate batches. I'll have a fix in tomorrow's daily build that addresses the issue

Rop Fetch with custom Rop Hda does not cook propperly Oct. 7, 2019, 4:14 p.m.

When cooking ROPs as a batch, PDG needs to be able to set the pre/post frame callback on the target ROP. These are used by PDG in order to alert the graph that a batch sub item has begun/completed cooking. If you promote the script parameters from your custom ROP asset onto the top level HDA itself, they should be picked up automatically.