AWS Thinkbox Discussion Forums

Single frame local partition generation makes 2 frames


Beta 17

When I have the render set to single frame and do a Generate All Partitions Locally, I get frames 0000 and 0001 for each partition.

When I make partitions with Deadline, I correctly only get the 0000s.

- Chad

Beta 17

When I have the render set to
single frame and do a Generate
All Partitions Locally, I get
frames 0000 and 0001 for each
partition.

When I make partitions with
Deadline, I correctly only get
the 0000s.

- Chad

This is As Designed.
A vicious bug in PFlow prevents us from creating a single frame with varying random seeds. Somehow PFlow figures out we intend to render one frame and refuses to update the system no matter what, so the result would be multiple partitions with the same seeds. Thus, for local rendering, it always does two frames in a row to ensure the seeds will be incremented correctly.

We could not find any other workaround. This will be documented (if it isn't already).

Yeah, we’ve seen that bug, where you change the seed and it doesn’t invalidate the particles until you change frames, but can’t you just render 2 frames but only output the intended frame? Or post-render cleanup the output by deleting the 0001 files?



Seems we’re going to be deleting a LOT of 0001 files manually otherwise.


  • Chad

Yeah, we’ve seen that bug,

where you change the seed and

it doesn’t invalidate the

particles until you change

frames, but can’t you just

render 2 frames but only

output the intended frame? Or

post-render cleanup the output

by deleting the 0001 files?



Seems we’re going to be

deleting a LOT of 0001 files

manually otherwise.


  • Chad



    What I might do is save both with temp. names, then rename the one to the real name and delete the other. I want to avoid killing a frame that already existed (right now, it would actually overwrite the other frame if it existed, which is not too good either).

You’ve brought this bug up to ADSK? Seems like one of those things that you’d want to change in Krakatoa once they fixed PFlow (if ever).


  • Chad

You’ve brought this bug up to

ADSK? Seems like one of those

things that you’d want to

change in Krakatoa once they

fixed PFlow (if ever).





Of course not. Nobody there is touching PFlow, chances for this to be fixed are minimal, and we need Krakatoa to work with PFlow in Max 8 and 9, not with Max 2011 ;o)



So we do what we can to work around all the funky things that happen.

Privacy | Site terms | Cookie preferences