Render Back v2.6

Render Back is a Blender add-on that allows you to perform 'command line rendering' (console/batch rendering) without the hassle of writing a script for each project. Console rendering can make rendering faster, but its true upside is that it provides stable renders and is less likely to crash. This is particularly beneficial if you're working with limited hardware resources.

What's New in Version 2.6

• New "Keep terminal open" feature, when enabled, keeps the terminal window open after rendering finishes. This allows you to review useful information such as render time and any messages displayed during the rendering process.

Pros

• Completion Actions: A feature to specify post-render actions, such as Hibernate, Sleep, or Shutdown to be automatically executed after the render is complete.
• Open Directory on Completion: Option to automatically open the file directory where the rendered files are saved after the rendering process finishes.
• Batch File Execution: The add-on generates a batch file that handles the rendering process.
• System Notifications: A pop-up notification to alert the user when rendering is complete.
• User-Friendly Interface: Provides a simple panel within Blender's "Output Properties" to specify and manage rendering options.
• Supports Multiple Render Types: Capable of rendering both animations and single images.
• Keep Terminal Open: This will keep the terminal open so you can view the rendering stats.

Cons

• Windows only: The add-on has been developed and tested on Windows and has no support for other operating systems.

Road Map for Future Plugin Features

• Standalone Rendering App

• Support for other operating systems

The add-on has been tested in Blender 4.1, and the extension has been tested in Blender 4.4.1.

Note:

• In Blender 4.4.1, install "render_back_2_6_extension", not the add-on. If you use anything older than Blender 4.1, due to API changes, you might have to use older versions of the add-on.
• When updating the add-on from v2.1 to v2.6, and it doesn't change to the updated UI, restart Blender, disable it, then re-enable the add-on. The new changes should now show up. This is caused by Blender caching property UI labels from when the script was first registered.