OpenKatana · Create webgl kit:
OpenKatana_create_webgl_kit prepares an editable starting kit for creating original 3D animations with JavaScript and Three.js, using OpenKatana’s bundled WebGL renderer rather than Blender. It combines an editable scene module, a declarative scene setup, an animated display atlas, and a camera schedule with a planned cut, giving you a foundation to customize for your creative brief. The starting scene includes a floor, post-processing settings for bloom and depth-of-field blur, and motion-blur settings. Its camera schedule separates the animation into two sections with a cut around the midpoint, helping keep camera transitions controlled during later rendering. This node creates authoring materials only: it does not render a video or download resources, and it refuses to overwrite an existing destination.
OpenKatana · Create webgl kit Input Parameters:
project_id
A required STRING identifying the existing OpenKatana project where the kit will be created. The tool resolves this identifier to the project’s folder and checks the project state before preparing the kit, so you should use the identifier of a project you have already created, not an arbitrary output-folder path. Choosing a different project changes where the kit and its supporting files belong. The supplied node interface does not specify a default value, allowed options, or minimum or maximum string length.
arguments
A required STRING carrying the tool’s additional arguments as a JSON object. These settings are supplied through this text field rather than through separate node inputs. The underlying tool supports directory, which defaults to webgl; width and height, which default to 640 and 360 and must each be even integers from 64 to 4096; fps, which defaults to 30 and must be an integer from 1 to 120; and frames, which defaults to 60 and must be an integer from 6 to 36000. These settings determine the destination and the canvas size, playback rate, and frame count used to prepare the scene and its camera schedule; they do not start rendering. For example, {"directory":"webgl_draft","width":640,"height":360,"fps":30,"frames":60} requests a two-second starting scene in a new destination. The node interface does not specify a default string or string-length limits for arguments; an empty JSON object, {}, expresses a request to use the tool’s default settings.
after
An optional STRING available on the shared tool-node interface, with a default of None in the execution method. It can provide a workflow connection for placing this call after another operation, such as project creation, but the supplied execution code does not read or forward its value to the kit-creation tool. It therefore does not change the scene dimensions, destination, animation settings, or generated content. No supported text options or minimum or maximum string length are specified, and you should not use it to pass kit configuration.
OpenKatana · Create webgl kit Output Parameters:
result_json
A STRING containing the tool response serialized as JSON, rather than an image, video, or directly editable scene object. The supplied examples show that a successful kit result includes scene and module entries, whose values identify the generated scene description and editable JavaScript module relative to the project folder. These paths matter for subsequent steps: you can inspect or edit the module and scene, validate the scene, and pass the scene path to the renderer. The complete response schema is not shown in the supplied code, so you should inspect the returned JSON rather than assume additional field names or a particular response-wrapper layout. A successful creation response means the authoring kit has been prepared, not that rendering has completed.
OpenKatana · Create webgl kit Usage Tips:
- Create the OpenKatana project first, then use its exact identifier in
project_id. If you connect a preceding operation throughafter, treat that connection as workflow ordering, not as a source of configuration values. - Start with
{}inargumentswhen you want the standard 640 × 360, 30 fps, 60-frame kit. Use a newdirectoryvalue whenever you want another version without replacing your existing work. - For a small test scene, use
{"directory":"webgl_test","width":160,"height":96,"fps":24,"frames":12}. These settings appear in the supplied tests and provide a short, low-resolution setup for checking the later rendering workflow. - Calculate the intended duration as frame count divided by frame rate. For example, 60 frames at 30 fps represents two seconds; increasing
fpswithout increasingframesshortens the animation. - Keep both image dimensions even. Common choices such as 640 × 360 and 1280 × 720 meet the validation requirements; odd dimensions are rejected before the kit is created.
- Read the WebGL guide and customize the generated JavaScript module for your brief. The kit is a starting point for your scene, not a finished artwork, and its initial camera schedule includes a midpoint cut that you should review when planning the animation.
- Validate the generated scene before rendering, then use the WebGL-compatible
render_scene3dworkflow. The supplied rendering tests explicitly enabletrusted_script=Truefor the editable JavaScript scene; review the script before granting that permission. - Keep kit creation, rendering, and clip assembly as separate steps. If you later render in chunks, preserve their order; the supplied assembly tests reject reversed chunks when contiguous assembly is expected.
OpenKatana · Create webgl kit Common Errors and Solutions:
Video dimensions must be even
- Explanation: The requested width or height is an odd number. The kit explicitly requires both dimensions to be divisible by two.
- Solution: Change both dimensions to even integers within the supported range, such as 640 × 360 or 1280 × 720.
WebGL kit destination already exists
- Explanation: The destination selected by
directoryalready exists. The tool deliberately stops rather than overwriting files, including files in a destination you may have created during an earlier run. - Solution: Choose a fresh directory, such as
webgl_v2, or continue editing the existing kit. Back up any work before manually removing an old destination.
Invalid numeric setting or value outside the supported range
- Explanation: The tool validates width and height from 64 to 4096, fps from 1 to 120, and frames from 6 to 36000, with integer validation enabled. The supplied excerpt does not show the exact validation error wording.
- Solution: Supply whole-number JSON values within those limits, not quoted numbers or fractional values. Also check that width and height are even.
Invalid JSON in arguments
- Explanation: The additional settings must be readable as a JSON object. Missing quotation marks, trailing commas, or incomplete braces can prevent argument processing before kit creation starts; the exact parsing message is not shown in the supplied source.
- Solution: Use double quotes around setting names and text values, and leave numeric values unquoted. A valid example is
{"directory":"webgl_v2","width":640,"height":360,"fps":30,"frames":60}; use{}when no overrides are needed.
Unexpected or unsupported argument
- Explanation: The supplied tests confirm that an unrecognized argument such as
unexpectedis rejected. Separately, the node’s execution method raisesTypeErrorwith the prefixunexpected inputs:if unsupported direct input fields reach it. - Solution: Keep the node inputs limited to
project_id,arguments, and optionalafter. Insidearguments, use only the supported kit settings:directory,width,height,fps, andframes.
Project lookup or project-state error
- Explanation: Kit creation first resolves the project and checks its state. A missing, incorrect, or unusable project can therefore stop the operation before any kit is generated; the exact error text is not included in the supplied context.
- Solution: Confirm that the project exists in the active OpenKatana workspace and copy its identifier exactly into
project_id. Complete project creation before running this node.
Destination path rejected or files cannot be written
- Explanation: The tool resolves
directorythrough a project-local path helper and writes the kit beneath the project. An unsuitable path or a filesystem access problem may prevent creation; the supplied excerpt does not expose the exact path-validation or permission messages. - Solution: Use a simple, fresh project-relative directory such as
webgl_draft. Avoid paths outside the project, and confirm that the OpenKatana process can write to the project folder.
