Is there a maximum number of passes Deadline will check before submitting the job?
We have a scene with 33 passes and when we put a check in the box next to the 2 lasts one, in the script editor output window, the value doesn’t change if the check is on or off. If we use “submit all passes”, then there’s no problem, all passes are submitted. but if we select manually, whatever we do, no passes over 31 will be submitted.
I count passes from the top going down. The last in the list are never submitted.
Thanks
Vincent
What we do for now is submit all passes (as suspended) and then go in the monitor and delete the one we don’t want.
I’ve reproduce this with Beta3 as well.
Vincent
This appears to be a limitation of the XSI check box list control we use, as it stores the selected item(s) internally as an integer value. Each item in the list represents a power of 2 equal to its index (the first pass is 2^0=1, the second is 2^1=2, etc), and using the sum of the selected items, we can determine which items are selected and which are not. However, a value of 2^32 is too big for an integer, and explains why selecting anything after the 31st pass does nothing. We’ve looked at the list box control as well, and it too has the same problem. From reading the SDK documentation, there really isn’t an alternative to these controls.
One potential solution would be to display a second check box list control, and only populate it when the first list gets filled up. For now though, using the “submit all passes” option is really the only workaround.
Cheers,