@James Crowther Really pleased to hear that, looking forward to being able to use Crowdrender when this comes out.

@James Crowther I would be happy enough with a frame based rendering system if the buckets are not possible. I guess the main thing is that all machines are productive and the failure of a single node does not stop the completion of the job. Rather a determined number of retries before it is flagged as failed. and then being able to manually add them back when the machines issues are sorted. The ability to add or remove workers during the course of a render to me would also be more important than a fully distributed rendering solution. In addition, being able to queue multiple jobs would trump all machines working on the same frame. We often have between 10 to 30 concurrent jobs going at the peak of production so sending off jobs and just having them get done without having to babysit frames is pretty important. Thanks for tackling this really important aspect of 3d!

Absolutely!

Yes, absolutely! Distributing via buckets rather than a percentage of the frame would be fantastic. I'm trying to get our organisation to switch to using blender in production but having a network rendering solution is crucial to being viable. We currently use vray on another software which works reasonably well and uses the bucket allocation method. I thought this was standard so it took me a while to get the method currently used which I think (sorry guys) is not as effective. Though much better than manual rendering on each machine! I would be so happy for this to be implemented.