{
  "schemaVersion": "1.0",
  "canonical": "https://superlumin.al/docs/blender-addon/render-node-settings",
  "representations": {
    "html": "https://superlumin.al/docs/blender-addon/render-node-settings",
    "markdown": "https://superlumin.al/docs/blender-addon/render-node-settings.md",
    "json": "https://superlumin.al/docs/blender-addon/render-node-settings.json"
  },
  "retrievalHint": "Read page.description and page.relatedArticles first, then page.body. page.images lists every documentation screenshot with alt text, dimensions, captions, and annotations.",
  "page": {
    "path": "/docs/blender-addon/render-node-settings",
    "title": "Render-node and experimental settings",
    "description": "Choose the farm Blender version and understand Finish Frame On Error and the Persistence Engine.",
    "navTitle": "Render-node settings",
    "section": "Blender add-on",
    "sectionOrder": 20,
    "order": 6,
    "hidden": false,
    "keywords": [
      "Blender version",
      "Persistence Engine",
      "Finish Frame On Error"
    ],
    "updated": "2026-08-04",
    "body": "## Blender version\n\nWith 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.\n\n![Render Node Settings with the Blender version match and experimental runtime toggles](https://superlumin.al/docs/images/blender/addon-render-node.png)\n\n*Local add-on compatibility, farm Blender selection, and experimental execution behavior are separate decisions.*\n\n- [Annotation 1: Match or override the Blender version](/docs/blender-addon/render-node-settings#blender-version)\n\n- [Annotation 2: Experimental runtime behavior](/docs/blender-addon/render-node-settings#persistence-engine)\n\nDisable 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.\n\n### Patch versions are not exact farm selectors\n\nThe 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.\n\n## Finish Frame On Error\n\nDefault: **off**.\n\nWhen 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.\n\nUse it only when you have confirmed all of the following:\n\n- Blender wrote the expected output file completely\n- the recurring error happens after the output save\n- previews and downloaded output are correct\n- suppressing the error will not hide an incomplete layer, output node, or side effect\n\nOtherwise keep it off so errors remain visible.\n\n## Persistence Engine\n\nDefault: **on**.\n\nThe 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.\n\nPersistence 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.\n\n## Controlled comparison\n\n### Choose a short range\n\nUse frames that exercise animation, caches, handlers, and render-time add-ons.\n\n### Hold other settings constant\n\nUse the same source files, Blender version, upload mode, image format, and capacity.\n\n### Compare enabled and disabled\n\nRun one job with Persistence on and one with it off.\n\n### Inspect output and timing\n\nCompare full downloaded frames first, then review machine and operation timings in the web job page.\n\n### No universal speed multiplier\n\nScene 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.\n\n- [Job details](/docs/web-ui/job-details): Compare machines, render time, and other operation timings.\n- [Troubleshoot mismatches](/docs/blender-addon/troubleshooting#render-and-frame-errors): Isolate version and persistence differences with a small test.",
    "images": [
      {
        "id": "addon-render-node",
        "src": "/docs/images/blender/addon-render-node.png",
        "alt": "Render Node Settings with the Blender version match and experimental runtime toggles",
        "caption": "Local add-on compatibility, farm Blender selection, and experimental execution behavior are separate decisions.",
        "width": 1376,
        "height": 364,
        "annotations": [
          {
            "number": 1,
            "label": "Match or override the Blender version",
            "href": "/docs/blender-addon/render-node-settings#blender-version"
          },
          {
            "number": 2,
            "label": "Experimental runtime behavior",
            "href": "/docs/blender-addon/render-node-settings#persistence-engine"
          }
        ]
      }
    ],
    "machineReadable": {
      "markdown": "/docs/blender-addon/render-node-settings.md",
      "json": "/docs/blender-addon/render-node-settings.json"
    },
    "internalLinks": [
      "/docs/blender-addon/render-node-settings",
      "/docs/blender-addon/render-node-settings",
      "/docs/web-ui/job-details",
      "/docs/blender-addon/troubleshooting"
    ],
    "readingTime": "3 min read",
    "toc": [
      {
        "id": "blender-version",
        "title": "Blender version",
        "level": 2
      },
      {
        "id": "patch-versions-are-not-exact-farm-selectors",
        "title": "Patch versions are not exact farm selectors",
        "level": 3
      },
      {
        "id": "finish-frame-on-error",
        "title": "Finish Frame On Error",
        "level": 2
      },
      {
        "id": "persistence-engine",
        "title": "Persistence Engine",
        "level": 2
      },
      {
        "id": "controlled-comparison",
        "title": "Controlled comparison",
        "level": 2
      },
      {
        "id": "choose-a-short-range",
        "title": "Choose a short range",
        "level": 3
      },
      {
        "id": "hold-other-settings-constant",
        "title": "Hold other settings constant",
        "level": 3
      },
      {
        "id": "compare-enabled-and-disabled",
        "title": "Compare enabled and disabled",
        "level": 3
      },
      {
        "id": "inspect-output-and-timing",
        "title": "Inspect output and timing",
        "level": 3
      },
      {
        "id": "no-universal-speed-multiplier",
        "title": "No universal speed multiplier",
        "level": 3
      }
    ],
    "wordCount": 467,
    "relatedArticles": [
      {
        "path": "/compatibility/render-engines",
        "title": "Blender render engine compatibility",
        "description": "Superluminal renders Cycles and EEVEE image sequences with Blender 4.0 through 5.2. Choose the farm version and output format before submission."
      },
      {
        "path": "/how-superluminal-is-so-fast",
        "title": "How Superluminal is so fast",
        "description": "Benchmark results show how Superluminal removes delays through its Persistence Engine, concurrent output work, streaming delivery, and farm scheduler."
      },
      {
        "path": "/cycles-render-farm",
        "title": "Cycles on a render farm",
        "description": "Cycles animations can split across render nodes. Measured jobs show how node count, startup time, GPU memory, and settings affect the result."
      }
    ]
  }
}