Expanding Frame Range after Completion Wrong

[im_thatoneguy]

If you change the frame range from like 50-100 to 0-100 after the job finishes it will mark frames 0-50 as complete as well. This is incorrect behavior imo. It should create new ready-to-render frames. I believe this is a regression from 5.x behavior.

Also “requeue selected tasks” would be a nice feature to fast-track for Beta 6.

[im_thatoneguy]

Also reducing the frame range so that it’s shorter seems to sporadically be reflected in the tasks list.

[rrussell]

If you change the frame range from like 50-100 to 0-100 after the job finishes it will mark frames 0-50 as complete as well.

This will be fixed in beta 6.

Also “requeue selected tasks” would be a nice feature to fast-track for Beta 6.

The options to requeue and complete specific tasks will be available in beta 6.

Also reducing the frame range so that it’s shorter seems to sporadically be reflected in the tasks list.

This has already been fixed in our internal build, and the fix will be included in beta 6.