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 · Create scene3d

ComfyUI Node: OpenKatana · Create scene3d

Class Name

OpenKatana_create_scene3d

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 · Create scene3d Description

Creates structured OpenKatana 3D scenes with meshes, groups, models, materials, and transforms.

OpenKatana · Create scene3d:

OpenKatana_create_scene3d creates a structured 3D scene within an OpenKatana project, providing a foundation for building and rendering 3D artwork through OpenKatana’s Three.js-based scene workflow. Rather than producing a finished image immediately, it establishes a scene description that you can subsequently check and render with related tools. The supplied scene-validation code supports geometric mesh objects, groups for organizing objects, and imported models, with properties for placement, materials, visibility, and shadow behavior. Model objects also have fields for animation and morph weights, which describe shape adjustments supported by the model. This approach lets you define a scene in a repeatable, text-based form and keep scene creation separate from previewing and rendering, making it easier to organize and troubleshoot your creative workflow.

OpenKatana · Create scene3d Input Parameters:

project_id

A required STRING identifying the OpenKatana project used for the tool call. It provides the project context when the node prepares the creation request, so you should use the identifier of the project in which you want to create the scene. The provided integration test creates a project before creating a scene and uses the same project identifier for subsequent checking and rendering. Keeping this value consistent across related nodes helps ensure that they work within the intended project. No default value, permitted identifier pattern, length limits, or list of options is specified in the supplied node interface.

arguments

A required STRING containing the tool arguments in JSON form. This is where you supply the scene-creation details that are not exposed as separate node inputs. The provided integration test calls the underlying tool with a name and a scene description in addition to the project identifier; these are properties of the tool request, not additional input sockets on this node. The scene description determines the objects and other supported settings used to build your scene, so changes to this text can substantially change the resulting scene. Supply valid JSON with double-quoted property names and JSON values such as lowercase true and false for booleans. The supplied excerpts do not include the complete creation-tool argument schema, so use a known-valid scene description or OpenKatana’s scene3d guide rather than inventing scene fields. No default value, size limit, or enumerated options are specified in the supplied interface.

after

An optional STRING accepted by the node wrapper. In the supplied execution code, this value is received but is not included in the arguments sent to the scene-creation tool, so it should not be used to specify scene objects, materials, rendering settings, or the destination project. It can provide a connection point for arranging workflow dependencies, but the excerpt does not show any additional behavior associated with its contents. No explicit default value, permitted options, or length limits are declared in the supplied input specification; the execution method uses None when the argument is omitted.

OpenKatana · Create scene3d Output Parameters:

result_json

A STRING containing the tool response returned through the OpenKatana node wrapper. Treat it as JSON-formatted result data rather than an image, video, or directly loadable 3D model. The integration test for the underlying creation tool retrieves a scene value from its structured response and passes that value to the scene-checking and scene-rendering tools, demonstrating that the creation result provides scene information for follow-up operations. The supplied excerpts do not show the wrapper’s complete response-formatting implementation, so inspect the returned JSON before assuming an exact nesting structure or connecting it to a consumer that expects a particular field. This output is important for confirming what was created and obtaining the scene information needed for subsequent workflow steps.

OpenKatana · Create scene3d Usage Tips:

  • Create or select your OpenKatana project first, then use its exact identifier consistently for scene creation, checking, and rendering. The supplied integration test follows this sequence.
  • Start with a known-valid scene description. OpenKatana’s supplied tests use its starter scene helper, and the scene3d guide is another documented source of workflow information; either is safer than guessing the full scene schema.
  • Keep the distinction between node inputs and JSON properties clear: project_id, arguments, and after are the only inputs on this node. Scene details such as name and scene belong inside the tool-argument JSON rather than in additional sockets.
  • Use object types deliberately: mesh is for geometry-based objects, group is for organizing objects, and model is for imported models. The validator applies different allowed fields to each type, so avoid copying every property from one type to another.
  • Write visibility and shadow switches as actual JSON booleans. Use true or false, not quoted text such as "true" or numbers such as 1.
  • Check the created scene with the related check_scene3d tool before rendering. For imported models, use inspect_model3d to check the asset separately, especially when you plan to use animation or morph weights.
  • Keep initial render tests small. The supplied test creates a starter scene at 160 × 96 pixels with three frames at 12 fps and previews frames 0 and 2; this demonstrates a practical way to test the downstream rendering workflow before increasing scene size or animation length. These settings belong to the scene or rendering workflow, not to separate inputs on this node.

OpenKatana · Create scene3d Common Errors and Solutions:

Object type must be mesh, model or group

  • Explanation: This exact validation message occurs when an object has a type outside the supported values. A descriptive label such as cube or character is not a supported object type.
  • Solution: Set the object’s type to mesh, model, or group. For a geometric object, use mesh and describe its shape in the supported geometry structure.

visible must be boolean

  • Explanation: The scene validator requires visible to be an actual boolean value. Text such as "false" and numeric values are not accepted as booleans.
  • Solution: Use the unquoted JSON value true to show the object or false to hide it.

cast_shadow must be boolean

  • Explanation: The cast_shadow property has been supplied with a value other than a boolean. This setting controls whether an applicable object casts shadows.
  • Solution: Use unquoted true or false and include this property only on an object type that supports it, such as a mesh or model.

receive_shadow must be boolean

  • Explanation: The receive_shadow property must be a boolean rather than text or a number. It describes whether an applicable object receives shadows.
  • Solution: Replace the value with unquoted true or false and verify that the property is being used on a supported object type.

unexpected inputs: …

  • Explanation: The node explicitly raises a TypeError with this prefix when it receives additional execution fields that are not declared in its supported typed inputs. This is different from an error about properties inside the JSON scene description.
  • Solution: Use only the exposed inputs project_id, arguments, and optional after. Put supported tool-request details inside arguments rather than trying to supply them as extra node inputs.

Invalid JSON in arguments

  • Explanation: This is a descriptive error category rather than a confirmed literal message from the excerpts. The arguments text must be readable as JSON; missing quotation marks, trailing commas, or Python-style values such as True can prevent the request from being prepared correctly.
  • Solution: Validate the text with a JSON checker, use double quotes for property names and string values, remove trailing commas, and use lowercase true, false, and null where appropriate.

Invalid geometry or unsupported fields for an object type

  • Explanation: This is a descriptive error category; the exact message is not shown. Mesh geometry is checked by the scene validator, and different object types have different allowed properties. For example, a group’s permitted fields do not include geometry or material.
  • Solution: Compare the object with a known-valid scene example. Supply supported geometry for meshes, use a model reference for model objects, and keep groups limited to their supported organization and transform properties.

Model asset cannot be resolved or inspected

  • Explanation: This is a descriptive error category; the exact message is not provided. For a model object, the validator resolves its asset and calls the model-inspection function, so an unavailable reference or an asset that cannot be inspected can stop validation.
  • Solution: Check that the model reference resolves within the intended project context. Use inspect_model3d to test the source model and, where needed, the related import_model3d tool to bring it into the project workflow before creating the scene.

Project lookup or access failure

  • Explanation: This is a possible workflow error rather than a confirmed literal message. The tool call uses project_id to establish its project context, so an incorrect identifier or unavailable project can prevent scene creation.
  • Solution: Confirm that the project has already been created and copy its identifier exactly. Use the same identifier in the related creation, checking, and rendering steps.

OpenKatana · Create scene3d 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 · Create scene3d