Blender add-on
Submitting from Blender
The upload and launch flow inside Blender, what each phase means, and where the render then lives.
- 1Save the fileThe add-on uploads what is on disk, not what is in memory. Unsaved changes are not rendered.
- 2Scan dependenciesPress Scan and resolve anything red with Locate.
- 3Set the frame rangeStart and End in the Render settings block. Test one frame before an animation.
- 4Choose add-ons and colourUntick add-ons the render does not need. Leave the OCIO checkbox on if the scene uses a custom config.
- 5Upload and launchOne button. Progress is shown per file in the panel and in Blender's status bar.
- 6Open the renderWhen it is away, View on blender.farm opens the live view in your browser. Start a new render resets the panel.
Phases you will see
| Phase | What is happening |
|---|---|
| Preparing | Collecting files and zipping add-ons and OCIO config |
| Fingerprinting files | Hashing so anything already uploaded is skipped. Turn it off with the upload option if you would rather not read the files |
| Creating job | Registering the job and getting upload links |
| Uploading | Per-file progress and speed. Files reused from the cache are counted and not sent |
| Launching render | Renting the GPU machine |
Blender stays usableUploading runs on a background thread, so the interface does not freeze. Do not close Blender before the launch finishes; once the render is away you can close everything and follow it in the browser.
After launch
The render lives on the website from there: live frames, logs, downloads, relaunching. The add-on is a submission tool, it does not stream frames back into Blender.