Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > OpenKatana > OpenKatana · Render blender

ComfyUI Node: OpenKatana · Render blender

Class Name

OpenKatana_render_blender

Category
OpenKatana/Tools
Author
rk0neki (Account age: 235days)
Extension
OpenKatana
Latest Updated
2026-11-05
Github Stars
0.05K

How to Install OpenKatana

Install this extension via the ComfyUI Manager by searching for OpenKatana
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter OpenKatana in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

OpenKatana · Render blender Description

Renders existing 3D scenes or trusted Python-built scenes in Blender from OpenKatana workflows.

OpenKatana · Render blender:

OpenKatana_render_blender connects an OpenKatana workflow to a separately installed Blender application so you can render existing 3D scenes or scenes created by trusted Python scripts. It uses Blender’s scene settings, including the camera, lighting, materials, animation, and image dimensions, to produce rendered imagery rather than generating images with a diffusion model. This makes it useful when you need deliberate control over object placement, consistent geometry, or repeatable animation. The supplied implementation supports choosing a rendering engine and limiting the frames to render, checks for missing external image textures, and includes compatibility handling for Blender versions that use the newer Eevee engine identifier. Script-based rendering is intended for trusted scene authors, because a Blender Python script executes code rather than simply describing a scene.

OpenKatana · Render blender Input Parameters:

project_id

A required STRING passed to OpenKatana’s argument-preparation layer together with the selected tool and the argument text. It provides project context for the tool call; however, the supplied code does not show how that context affects file locations, project lookup, or render storage. Use the project identifier associated with your OpenKatana workflow rather than assuming this field accepts a Blender file path. No default value, allowed-value list, minimum length, or maximum length is visible in the supplied node interface.

arguments

A required STRING containing the arguments to prepare for the rendering tool. The node processes this text through OpenKatana’s argument helpers before invoking the tool; the helpers’ accepted text format and validation rules are not included in the supplied source, so use the argument format documented by your installed OpenKatana tool rather than assuming an arbitrary string will work. For context, the underlying rendering bridge has the signature render_blender(source, out, engine='BLENDER_EEVEE', start=None, end=None, trusted_script=False, timeout=1800): these are rendering settings carried through the tool’s argument mechanism, not additional node sockets. They describe the scene or script source, output destination, rendering engine, optional frame limits, script-trust setting, and timeout. The bridge defaults to BLENDER_EEVEE, uses the scene’s frame limits when the overrides are None, and rejects a resolved frame range that runs backward or contains more than 36,000 frames. No default value, string-length bounds, or complete set of accepted options for the arguments input itself is shown in the node interface.

after

An optional STRING with a default value of None in the node’s execution method. Although the node accepts this input, the shown method does not read it, include it in the prepared rendering arguments, or pass it to the tool invocation. Consequently, the provided implementation does not establish a rendering or sequencing effect for its value. Do not rely on this field to change Blender settings or guarantee that another task has finished. No allowed values, minimum length, or maximum length are specified in the supplied interface.

OpenKatana · Render blender Output Parameters:

result_json

A STRING containing the tool invocation’s response after it has been processed by OpenKatana’s response helper. This is the node’s single result channel, intended to convey the rendering tool’s structured response as JSON text rather than directly supplying a ComfyUI image tensor or video output. Inspect the returned text to determine what the tool reports about the operation before passing any reported file locations or metadata to later steps. The supplied context does not include the implementation of the response helper or a sample render response, so the exact JSON fields, output artifact types, file naming conventions, and error-response structure cannot be specified reliably.

OpenKatana · Render blender Usage Tips:

  • Make sure Blender is installed and available to OpenKatana before starting a render. The bridge uses a separate Blender installation, and scripts run in Blender’s Python environment rather than necessarily sharing ComfyUI’s Python packages.
  • Begin with a short, low-resolution preview. The supplied example uses 320 × 180 pixels, 100% resolution scale, 12 frames per second, and frames 1 through 3, which provides a useful starting point for checking camera framing, materials, and lighting before a larger render.
  • Set the scene’s frame range deliberately, or provide supported frame overrides through the tool’s argument mechanism. When no overrides are supplied, the worker uses the scene’s start and end frames; each render range must contain no more than 36,000 frames.
  • Use the bridge’s default BLENDER_EEVEE setting when appropriate for your scene. The worker automatically retries with BLENDER_EEVEE_NEXT if Blender rejects the older identifier. Other engine identifiers must be supported by your Blender installation; the supplied code does not enumerate them.
  • Check that all external image textures are available on the machine running Blender. Pack textures into the Blender file where appropriate, or keep their external files accessible; the worker explicitly checks unpacked, file-based images and stops if one is missing.
  • Use Python scene scripts only when you trust their contents. The bridge exposes trusted_script with a default of False, and the supplied example is explicitly intended for the trusted-script route. Review scripts before enabling that route.
  • For script-created scenes, explicitly set a camera, render dimensions, lighting, and frame limits. The provided example creates these settings inside the script, making the scene setup easier to reproduce.
  • Account for render duration when preparing tool arguments. The underlying bridge exposes a timeout default of 1800; its timeout handling is not shown, so check your installation’s tool documentation before changing it for longer jobs.

OpenKatana · Render blender Common Errors and Solutions:

Missing Blender texture: ...

  • Explanation: The worker found an unpacked, file-based image whose resolved path does not point to an existing file. The actual message includes the missing texture’s path.
  • Solution: Open the scene in Blender and reconnect the missing image, restore the file at the reported location, or pack the image into the Blender file. Confirm that the render machine can access the asset, not just the machine where you prepared the scene.

Invalid Blender frame range

  • Explanation: The resolved end frame is earlier than the start frame, or the requested range contains more than 36,000 frames. Both conditions produce this exact message in the supplied worker code.
  • Solution: Set the end frame equal to or later than the start frame and keep the inclusive frame count within 36,000. Split longer animations into multiple render jobs.

unexpected inputs: ...

  • Explanation: The node’s execution method received extra named fields that are not declared in its typed input definitions. The message lists the unexpected field names.
  • Solution: Use only the exposed node inputs: project_id, arguments, and optional after. Supply rendering settings through the supported argument mechanism instead of adding new node inputs.

Rendering engine rejected by Blender

  • Explanation: Assigning an unsupported rendering engine can raise a TypeError. The worker provides a fallback only when the requested identifier is BLENDER_EEVEE; it then attempts BLENDER_EEVEE_NEXT. The exact Blender error text is not provided.
  • Solution: Check which engines your Blender installation supports and use an appropriate identifier through the tool arguments. If the default Eevee setting fails even after the fallback, check the Blender installation and its compatibility with the scene.

Python script execution failure

  • Explanation: Trusted scene scripts execute inside Blender using runpy.run_path. A syntax error, unavailable import, missing script-side asset, or incompatible Blender API call can interrupt execution. The resulting message depends on the script and is not specified in the provided context.
  • Solution: Test the script in the same Blender version used for rendering and review its traceback. Ensure required packages are available in Blender’s Python environment and that any referenced files are accessible.

Arguments rejected or not understood

  • Explanation: The node prepares arguments before invoking the rendering tool, but the supplied source does not show the accepted serialization format or the validation messages. Incorrect argument text may therefore fail before Blender starts.
  • Solution: Follow the argument schema exposed by your installed OpenKatana rendering tool. Verify the source and output settings first, then add optional settings one at a time. Do not assume that the bridge’s Python signature alone defines the required text format.

Changing after has no visible effect

  • Explanation: This is not a confirmed error message. The shown execution method accepts after but does not use its value, so changing it does not establish a different render configuration or execution dependency in the supplied implementation.
  • Solution: Put render settings in the supported arguments structure. If you need task ordering, use a sequencing mechanism documented by your installed workflow rather than relying on this field alone.

OpenKatana · Render blender Related Nodes

Go back to the extension to check out more related nodes.
OpenKatana
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

OpenKatana · Render blender