It’s release time! Render+ 2.1 is now out.
This version comes with several small quality of life improvements. I’m trying to smaller, more frequent releases moving forward. This way you can get bug fixes and small improvements faster instead of waiting until I implement some big feature.
Let’s look at the changes in this version
Debug messages now include server debug messages. The Batch server had it’s own logger, but it was only writing to a file. Now we can enable printing to the terminal (with a new parameter).
Render+ will also enable server debug logs when enabling the addon’s debug messages. This will help fight those annoying bugs. Duplicate log messages are also fixed, so no more echo in the terminal (I’m positive there’s a nerd joke in there somewhere).
The camera field will now be red if it is empty, since you need a camera to render. And to help you pick one the field will only show cameras, instead of every object in the scene. This one has been in the backlog for quite a while!
I’ve fixed several issues with paths too. Blender’s “.001” suffixes are now removed correctly. Render+ will autosave image renders to the blend’s folder if the output path is empty instead of failing. The Change Output paths dialog will not add an underscore to the first variable if the filename is empty. For instance, if you had selected scene as the first variable, you can now get something like “MyScene.png” instead of “_MyScene.png”.
Render+ will now change the view layer in the Render Layers node in the compositor for each job. Only when the compo is enabled, of course.
Render jobs won’t be marked as “failed” anymore if they created a render file. Sometimes Blender crashes when quitting or spits other errors that made R+ believe the render failed. Now, we only consider it failed if there was an error and we can’t find any render file.
Starting a batch will show an error before starting if any texture files are missing. No more pink renders! This only works for internal render jobs for now (eg. not for external files).