When i send off a job for rendering trough backburner (max9 sp1) it’s not always that all computers joins the job.. sometimes some machines just sits idle.. or sometimes they all start the job, but then i use some slaves for something else, but then when that is done they should re-join the old job, but they don’t.. it’s a real pain in the a..
Got taskblocking enabled ? That way tasks can be assigned to a machine before it gets idled and then the tasks cant be assigned to the slaves going idle anymore.
Hmm.. good question.. The advanced setting dialog says it’s enabled, but when i inspect a job with the queue manager it’s says “enable blocking tasks: no”
i had the same problem, updating to the 2007 version fixed it here. though there are reports of people having issues with it. the area forum generally gets a decent amount of traffic about backburner issues.
Yes, it’s been widely reported that BB2007 is buggy. We couldn’t get the one that shipped with max (backburner2007.0.0_000) to work properly and the updated one on under the Max service packs page (backburner2007.0.2_224) caused the same problem that Suurland is having.
Just wanted to let you know that it’s fixed now.. A friend installed BB .231 using the link DanielBrew posted which fucked everything up and he was not able to use backburner at all..
I installed backburner2007.0.2_224.zip (on the manager only) which in the readme file says: Fixed a problem that occurred when jobs were sent to multiple servers. Servers would finish a job, and not be available again for subsequent jobs. This prevented them for picking up jobs in the queue, and from being re-assigned manually.