1:
It seems that the “Generate All partition locally” does not respect the name of the sequence from the save particle rollout!
So if we have for example named the sequence prtV_skin_v001_.prt and we try to partition , it just ignores the name and calls the partition “Part01_10…prt” …!
2:
When we partition a single frame PRT volume on deadline it saves the frame before the actual frame and when we partition the same setup locally it saves the current frame plus the next frame “Which make sense due to the seed updating”
So if we are on frame 1001 , local partitoin would make “Filename.1001.prt” + “filename.1002.prt” , but the deadline partition saves “filename.1000.prt”
Confirmed, found and fixed.
This was a side effect of a bug fix in the function FranticParticles.MakePartitionFilename() to deal with periods around the frame number. I was previously calling it with path name and file name without extension and before the fix it was working (adding the extension after that).
Since the fix, I have to pass the complete filename including extension for the function to work correctly. I will check with Darcy whether that is a separate bug in the core code, but for now at least the local partitioning should be fixed.
This is a bit scary.
Is Frame 1000 the first frame in the scene range?
I am asking this because when you submit a scene to Deadline and it gets opened, it’s current time will most probably be set to the animationRange.start frame, not to the frame that was active at the time of submission. In other words, if you have animationRange = interval 1000 1100 and you are on frame 1042 when submitting, the frame that will be partitioned will probably still be 1000. Also, I am actually not sure whether the seeds will be randomized correctly in that case. I am calling
render frame:#current
in the script KrakatoaPartitionTasksOnDeadline.ms when set to single frame rendering, but I am not sure whether it would work right. So if you want to render a single frame, it is better to specify it either in the pickup frames list or via the custom range spinners, possibly setting it to two frames just to be sure. I will see if this could be improved somehow.
Ok, I changed the Deadline Partition submission of a single frame to automatically set the Custom Range to the current frame and the current frame plus one to ensure two PRTs are saved (and thus the seeds are hopefully incremented correctly). So if you are on frame 1042 and submit with Single Frame in Render Setup Dialog, the Custom Range will be set to 1042 and 1043, the submission will be performed and the Render Setup Dialog will be set back to Single Frame. Quite transparently.
Our shot range is always from 1001, so I was surprised why it saves a frame that was not in the frame range.
When do you think the new build or update would be available ?