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 · Import model3d

ComfyUI Node: OpenKatana · Import model3d

Class Name

OpenKatana_import_model3d

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 · Import model3d Description

Imports a 3D model and dependencies into an asset folder, preserving relative file paths.

OpenKatana · Import model3d:

OpenKatana_import_model3d brings an existing 3D model and its identified supporting files into a new asset folder so you can organize them for your OpenKatana project. It inspects the model, copies the dependencies reported by that inspection while preserving their relative folder structure, and saves an import receipt containing the inspection information. Preserving this structure helps keep references to supporting files intact when you move an asset into your project. This is a file-import operation rather than a model-generation, rendering, or mesh-editing tool: the shown implementation copies files without modifying their contents. It also explicitly reminds you that you must supply the rights needed to redistribute the imported asset.

OpenKatana · Import model3d Input Parameters:

project_id

A required STRING identifying the OpenKatana project for the tool call. The node passes this value into its argument-building process before invoking the import tool, giving the operation its project context. Use the identifier of the project where you intend to organize the asset; the provided example uses proof. The supplied code does not show project creation, project identifier validation, or the exact rules for resolving project-relative paths, so do not assume that entering a new identifier automatically creates a project. No default value, length limits, or list of allowed identifiers is shown in the authoritative interface.

arguments

A required STRING carrying the import tool’s arguments. For this operation, supply JSON text containing source and destination, for example {"source": "/assets/robot/model.obj", "destination": "scenes/demo/assets/rig"}. These are fields inside this input, not separate node inputs. The source identifies the existing model file, and the destination identifies the new folder for its imported files. The underlying importer resolves both paths, inspects the source, creates the destination, copies the dependencies reported by inspection, and writes import-receipt.json. The destination must not already exist, although missing parent folders can be created automatically. The provided tool-call example uses a project-relative destination, but the complete path-resolution rules are not included. No default string, maximum length, or selectable options are shown.

after

An optional STRING accepted by the node’s execution method. Its execution-method default is None when omitted; no input-widget default, allowed values, or length limits are shown. Although the node accepts this parameter, the displayed execution method does not explicitly read it or pass it into the tool invocation, so its effect on scheduling or execution order cannot be established from the supplied code. Leave it unconnected unless your surrounding OpenKatana workflow documents how it should be used, and do not rely on it alone to guarantee that another operation finishes before the import begins.

OpenKatana · Import model3d Output Parameters:

result_json

A STRING containing the tool response serialized as JSON. The underlying importer returns the inspection information together with a model field pointing to the model’s destination path and a rights field containing the notice user must supply redistribution rights. The inspection information includes a dependencies collection, which the importer uses to determine which files to copy, and that inspection information is also written to import-receipt.json in the destination folder. Use this output to check the reported imported location and pass relevant information to later steps that can read JSON text. This output is not itself a loaded 3D object or a rendered preview. The node applies a response-formatting function whose implementation is not supplied, so the exact outer JSON structure and the nesting of the importer’s fields cannot be confirmed from the available code.

OpenKatana · Import model3d Usage Tips:

  • Keep the source model’s supporting files in their expected relative locations before importing. The importer reads each reported dependency relative to the source model’s parent folder; moving or renaming those files beforehand can prevent the import from completing.
  • Choose a new destination folder for every import, such as scenes/demo/assets/robot_v001. The importer deliberately refuses to reuse an existing destination, so a versioned folder name is useful when testing or updating an asset.
  • Enter valid JSON in arguments, with double quotes around field names and text values. For a straightforward local-path example, use {"source": "/assets/robot/model.obj", "destination": "/projects/demo/assets/robot_v001"}; make sure those paths are accessible to the OpenKatana process.
  • Use paths on the machine or filesystem accessible to OpenKatana. A path that exists only on your browser’s computer will not necessarily be available to a remotely running service.
  • Check result_json and the destination’s import-receipt.json after importing. The receipt records the inspection information, while the underlying return value additionally supplies the imported model path and redistribution-rights reminder.
  • If an import fails after creating its destination, inspect that folder before retrying. The shown implementation does not include automatic cleanup, so a failed attempt may leave a partially populated folder that blocks another attempt at the same location.
  • Confirm format support through OpenKatana’s inspection behavior or documentation before preparing a large asset collection. The provided context does not expose the inspection implementation, so it does not establish a complete list of supported formats or dependency types.
  • Verify your asset license before sharing or packaging the imported files. Copying an asset into your project does not grant permission to redistribute it.

OpenKatana · Import model3d Common Errors and Solutions:

FileExistsError: [Errno 17] File exists

  • Explanation: The importer creates the destination with existing folders disallowed. An empty folder or a folder left behind by a failed attempt can therefore stop the import. This is a standard filesystem error; its exact wording can vary by platform.
  • Solution: Choose a new destination folder. If you want to reuse the original path, first inspect and back up anything important, then remove the old destination before retrying.

FileNotFoundError: [Errno 2] No such file or directory

  • Explanation: The source model or a dependency being copied may be missing from the expected location. Dependency paths are read relative to the source model’s parent folder. The exact error text depends on which operation encounters the missing file.
  • Solution: Verify the source path on the machine running OpenKatana. Restore missing supporting files to their original relative locations, and check filename spelling and capitalization.

PermissionError: [Errno 13] Permission denied

  • Explanation: OpenKatana may lack permission to read the source files, create the destination, or write the copied files and receipt. This is a possible filesystem error rather than a custom error message shown in the node.
  • Solution: Use a readable source location and a writable destination. If OpenKatana runs in a container or under a service account, check that the relevant folders are mounted and accessible to that process.

NotADirectoryError or IsADirectoryError

  • Explanation: A path may have the wrong filesystem type—for example, a parent path may be a file instead of a folder, or a dependency expected to be a file may actually be a directory. The exact message depends on the failing filesystem operation.
  • Solution: Point source to the intended model file, ensure the destination’s parent paths are folders, and check the source asset’s directory structure for incorrectly named files or folders.

OSError: [Errno 28] No space left on device

  • Explanation: Importing copies asset files rather than simply linking to their original locations. Insufficient storage can interrupt copying or receipt creation and may leave a partially populated destination.
  • Solution: Free disk space or select a destination on a drive with enough capacity for the model and its dependencies. Inspect and clean up the incomplete destination, or choose a new one, before retrying.

Invalid JSON or missing import arguments

  • Explanation: The arguments input is processed into tool arguments before invocation. Malformed JSON or missing source and destination values can prevent the call from reaching the importer. The supplied code does not show the exact parsing or validation error messages.
  • Solution: Supply a JSON object with both fields, such as {"source": "/assets/model.obj", "destination": "/projects/demo/assets/model_v001"}. Avoid trailing commas, use double quotes, and escape backslashes correctly if using Windows-style paths.

Model inspection fails before copying

  • Explanation: Inspection runs before the destination is created. If the inspector cannot read or understand the model, the import cannot proceed. The inspection implementation is not supplied, so its supported formats, validation rules, and exact error messages cannot be listed reliably.
  • Solution: Confirm that the source is a valid model file and that its format is supported by your installed OpenKatana version. Open it in a compatible 3D application to check for damage, and use the actual inspection error to guide any repair or re-export.

unexpected inputs: ...

  • Explanation: The node explicitly raises this error if it receives additional fields outside its defined typed inputs. This can occur when programmatic integrations try to pass tool arguments as separate node fields.
  • Solution: Use only the exposed node inputs: project_id, arguments, and optional after. Put source and destination inside the JSON text supplied to arguments, rather than adding them as separate node inputs.

OpenKatana · Import model3d 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 · Import model3d