Render-node and experimental settings

Blender version

With automatic version selection enabled, the add-on reads your running Blender major/minor version. It picks the same version when the farm supports it. Otherwise it picks the closest supported version that is not newer, and it clamps versions outside the available range. Manual choices span Blender 4.0 through 5.2.

*Local add-on compatibility, farm Blender selection, and experimental execution behavior are separate decisions.*

• Annotation 1: Match or override the Blender version

• Annotation 2: Experimental runtime behavior

Disable automatic selection to choose a version yourself. Manual selection helps when a production standardizes on a known farm build. Remember that Blender files and features are not generally backward compatible.

Patch versions are not exact farm selectors

The selector targets a major/minor build such as 4.4 or 5.2. Test the scene remotely whenever patch-level behavior, add-ons, or newly introduced Blender features matter.

Finish Frame On Error

Default: off.

When enabled, the farm can mark a frame finished if a usable image exists, even though Blender exits with an error afterward. This covers cases where the render and file save succeed but cleanup fails.

Use it only when you have confirmed all of the following:

• Blender wrote the expected output file completely
• the recurring error happens after the output save
• previews and downloaded output are correct
• suppressing the error will not hide an incomplete layer, output node, or side effect

Otherwise keep it off so errors remain visible.

Persistence Engine

Default: on.

The Persistence Engine keeps a Blender process alive between frames instead of paying the full startup and scene-build cost each time. It helps most when scene setup is long relative to render time.

Persistence can expose scene or add-on behavior that assumes a completely fresh process per frame. If repeated frames differ from isolated local renders, submit a small comparison with Persistence disabled.

Controlled comparison

Choose a short range

Use frames that exercise animation, caches, handlers, and render-time add-ons.

Hold other settings constant

Use the same source files, Blender version, upload mode, image format, and capacity.

Compare enabled and disabled

Run one job with Persistence on and one with it off.

Inspect output and timing

Compare full downloaded frames first, then review machine and operation timings in the web job page.

No universal speed multiplier

Scene load, geometry preparation, render time, output size, and add-on behavior vary widely. Measure your own representative scene rather than relying on a fixed performance claim.

• Job details: Compare machines, render time, and other operation timings.
• Troubleshoot mismatches: Isolate version and persistence differences with a small test.