Export Command Line
The Export Command Line feature provides an alternative way to execute your render queue. Instead of running the process inside the Batch Render Creator (BRC) interface, you can generate a standalone script file that can be executed directly in your operating system's terminal or command prompt.
This is a powerful solution for users who prefer to keep their rendering processes separate from the main application or for troubleshooting environments where a direct terminal output is preferred.
How to Export
To export your current render queue, click on the Terminal Icon located in the Top Menu at the bottom of the interface.
Enabled Jobs Only
The export function only includes jobs and scenes that are currently enabled in your project list.
Platform Support
Batch Render Creator automatically detects your operating system and generates the appropriate script format.
Windows (.bat)
On Windows, the application generates a Batch File.
- UTF-8 Support: Scripts include
@CHCP 65001 to ensure correct character encoding in the Command Prompt.
- Automatic Path Handling: The script automatically handles directory changes (
cd /d) to the Blender installation folder.
- Portability: All paths are quoted and sanitized to prevent errors with spaces or special characters.
Linux (.sh)
On Linux, the application generates a Shell Script.
- Shebang Inclusion: Includes
#!/usr/bin/env bash for proper execution.
- Native Commands: Uses POSIX-compliant commands and quoting for maximum compatibility across different distributions.
Advanced Features Included
The generated script is not just a simple list of commands; it includes several BRC-exclusive optimizations:
- Forced Resolution: All resolution settings (X, Y, and Percentage) defined in BRC are injected directly into the Blender process via Python expressions at runtime.
- Camera Selection: The script ensures the correct camera is active before starting the render.
- Post-Render Actions: If you have configured a post-render action (Shutdown, Sleep, or Restart) in the Action Bar, it will be appended to the end of the script.
- Compatibility Logic: The script automatically adjusts the render engine name (e.g., handling the transition between EEVEE and EEVEE-Next) based on the target Blender version.
Limitations & Warnings
While this feature offers flexibility, it operates independently of the BRC monitoring engine.
Important Limitations
By choosing to render via the Command Line script, please be aware of the following:
- No Custom User Scripts: Custom Python scripts managed within the Python Scripts window are not executed when running via the exported terminal script.
- Terminal Execution: The render process runs entirely inside the OS terminal. If you close the terminal window, the render will stop immediately.
- No BRC Control: Once the script is running, Batch Render Creator cannot monitor progress, pause, or stop the render. All control must be handled directly through the terminal interface.
This solution is recommended as an alternative for specific workflows or when you need a "set and forget" script that can be run even if BRC is closed.