Typing in a new frame range into the submission dialog doesn’t actually affect the range of frames rendered. The job uses the range set by the Fusion render range.
- Chad
Typing in a new frame range into the submission dialog doesn’t actually affect the range of frames rendered. The job uses the range set by the Fusion render range.
I can only reproduce this if I have the “Render First And Last Frames
First” box checked, in which case this was done by design. Can you
confirm if you have this option checked or not?
Thanks!
Hmmm… I don’t have that checked, but that IS what is happening to the tasks. It’s doing first-last-rest.
Weird… I did my test with Fusion 5 - is that the version you’re running?
5.21
What happens when you check that “Render First And Last Frames First”
before submitting the job? I’m just wondering if there is a backwards
boolean check with regards to that option.
Um, seems to be behaving ok. Maybe I was mistaken about what I had checked.