Render+ 2.3 is out today! This version comes with another important step towards better batch rendering.
After a massive rewrite of the batch server, Render+ can now render more than one job at a time. The global batch settings include a small slider to change the number of jobs that get run in parallel.
Render jobs are now started in “groups “at the same time. For instance setting
parallel render jobs to 2 will run two renders at the same time. Note that cancelling a job will not start the next one immediately, but it will wait until for the other render jobs in the group to finish.
This new feature ties in neatly with the work in the previous version. For instance, if you have multiple GPUs you now can run a different render on each one. Though even if you only have one, you choose to spread the jobs on both the GPU and CPU.
The RSS feed feature had some changes as well. Now instead of creating a file, the RSS feed is served right from the server. Once the batch starts you can point your browser to
localhost:7777/batch/rss to see the feed. If you are on a network, just replace localhost with the ip of the computer running the batch. Also feeds now include the progress percentage in the title.
This version also includes fixes an issue when Blender gets stuck after rendering. If a render job hits 100% and Blender hasn’t quit, the Blender process gets killed now, so the batch server is able to move on to the next render job.
Finally I’ve lowered the minimum refresh time for the UI. This is the time R+ waits to poll the batch server. It used to be around 1 second so it would not overwhelm the server, but it seems like lowering this isn’t affecting rendertimes much.
I’ve lowered both the minimum and the default value. In practice, this means the progress bar will update much more often instead of jumping around. However if you are upgrading, the value will stay at 1 second or whatever value you had set. You can change this to your liking in the addon preferences.
Life is a little hectic at the moment, so I’m hoping to do shorter versions and release more often. It’s more manageable for me, and I think it’s also better for users that need the new features fast.