Hey guys,
maybe someone can clear something up for me. My compositors don’t like sitting around waiting on a long job to finish in order to start working so we tend to manually prioritize based on task number; basically giving jobs with low task-counts a high priority, meaning that the small jobs finish first and they can start working on them, and while they’re working, the longer jobs are rendering.
When weighted scheduling came in I thought it was a godsend, as I figured that’s what Rendering Task Weight was, but after experimenting with it for a while, I think Rendering Task Weight just means ‘how many tasks are actually rendering in that job at that time’, rather than how many tasks (or even better: uncompleted tasks) are in the job in total.
If I’m right about that, is there a way (even a workaround) to add weight to lighter jobs? It’s fine if not, we’ll return to doing it manually, but just wanted to see if anyone had any thoughts.
Thanks!
Mark