Blender Runner
Lets you execute any Blender Python script straight from Unity using command-line communication
- Free updates
- Online support
- Unity 2021+
- Workflow Management: Create and manage multiple processing workflows
- Script Execution: Run custom Blender Python scripts with arguments
- Model Selection: Support for single and multiple model processing
- Argument Handling: Flexible argument system for script customization
- External Addon Support: Integration with Blender external addons
- Real-time Output: Monitor execution progress and results
- Background Processing: Run scripts without blocking Unity UI
Installation
- Import the Blender Runner package into your Unity project
- Ensure Blender is installed on your system
- Open Unity and wait for scripts to compile
Note
Blender Runner works in both the Unity Editor and at runtime, but most features are intended for Editor use.
Opening Blender Runner
Open the main window via:
Window → URage → Blender Runner
This window is the central hub for all Blender Runner workflows and scripts.
Core Concepts
Settings Asset
Blender Runner uses a central Settings ScriptableObject to store all workflows.
Create one via:
Assets → Create → URage → BlenderRunner → Settings
The Settings asset contains a list of Workflows, which appear as tabs in the Blender Runner window.
Workflows
A Workflow represents a collection of Blender scripts that belong together.
Examples:
- FBX Cleanup
- Low Poly Conversion
- Material Baking
Create a Workflow via:
Assets → Create → URage → BlenderRunner → Workflow
Each Workflow:
- Has a display name
- Contains a list of Scripts
- Appears as a tab in the Blender Runner window
Scripts
A Script represents a single executable Blender task.
Create a Script via:
Assets → Create → URage → BlenderRunner → Script
Script Settings
- Script Name
Display name in the UI - Description
Short explanation of what the script does - Python Script
The Blender.pyfile to execute - Model Required
Requires a selected model before execution
Arguments
Scripts can define arguments that are passed to Blender as command-line parameters:
--argumentName=value
Each argument supports:
- String
- Integer
- Float
- Boolean
- Mandatory flags
- Tooltips for user guidance
External Addons
If a script depends on non-built-in Blender addons, they can be listed here.
These addons are shown to the user with:
- Name
- Description
- Download URL
Execution Options
- Run in Background
Runs Blender headless - Use File System Watcher
Automatically detects exported FBX files
Typical Workflow
- Select a model in the Unity Project or Scene
- Open Blender Runner
- Select a Workflow tab
- Select a Script
- Fill in required arguments
- Click Run
Blender will execute the script and return control to Unity.
If enabled, generated FBX files are automatically reimported and instantiated.
File System Watcher
When enabled, Blender Runner monitors the output directory for changes.
This allows Unity to:
- Detect newly exported FBX files
- Refresh the Asset Database
- Automatically instantiate results in the scene
Note
This feature is Editor-only and intended for rapid iteration workflows.
Best Practices
- Keep Blender scripts small and focused
- Use arguments instead of hardcoded values
- Group scripts logically into workflows
- Use background mode for batch processing
No FBX is imported
Ensure File System Watcher is enabled
Verify the script actually exports an FBX
Blender does not start
Verify the Blender executable path
Check the Unity Console for errors
Arguments not applied
Check argument keys
Ensure mandatory arguments are filled


