Skip to content

Authoring node parameters

Supported authored schema: 110. Shader layer-graph nodes store controls in patch.params. Catalog controls are not serialized parameter records. Use operator-templates.json for complete nodes generated by Studio’s operator factory.

The file contains projectSchemaVersion and an operators map keyed by exact operator ID. Copy an entry into layer.graph.nodes. It includes kind: "shader", id, position, and a complete patch with required parameters, defaults, choices, colour grouping, textures, and signature where needed.

Assign a unique ID to both node.id and node.patch.id. Update wires and parameter references that target it. Set position, edit authored values, and connect named ports from the catalog. Preserve structural controls such as Resolution. Scalar or vector outputs require a compatible conversion before the layer’s colour Output; inspect the operator’s outputs and signatures. A node template is not a complete project.

A complete parameter record shape (use actual IDs and metadata from your operator template):

{"id":"amount","name":"Amount","valueKind":"float","value":0.7,"defaultValue":0.5,"min":0,"max":1,"step":0.01,"hardMin":0}

value is the authored starting value; defaultValue is the reset value. Editing one does not change the other. min/max describe the slider viewport; only hardMin/hardMax, when present, are engine limits. step is the control increment. Preserve integer: true where required. Patch floats are stored in parameter units, not normalized 0–1. Rack/global floats use their own schema; do not substitute a patch record for a globalParams entry.

Choices use numeric values and serialized options, not the catalog’s string choices. An Edges example:

{
"id":"edge","name":"Edges","valueKind":"select",
"value":1,"defaultValue":1,"min":0,"max":3,"step":1,"integer":true,
"hardMin":0,"hardMax":3,"control":"select",
"options":[{"label":"Repeat","value":0},{"label":"Mirror","value":1},{"label":"Extend","value":2},{"label":"Transparent","value":3}]
}

Keep the selected operator’s exact labels/values. Structural controls can also have internal: true, which makes them ineligible as ordinary exposed/bound controls. Do not add control: "slider" to floats: the factory emits control: "select" only for choices.

Three component records share vectorGroupId and groupLabel:

[
{"id":"color.r","name":"Color R","valueKind":"color-component","value":0.95,"defaultValue":0.95,"min":0,"max":1,"step":0.01,"vectorGroupId":"color","groupLabel":"Color","component":"r"},
{"id":"color.g","name":"Color G","valueKind":"color-component","value":0.35,"defaultValue":0.35,"min":0,"max":1,"step":0.01,"vectorGroupId":"color","groupLabel":"Color","component":"g"},
{"id":"color.b","name":"Color B","valueKind":"color-component","value":0.15,"defaultValue":0.15,"min":0,"max":1,"step":0.01,"vectorGroupId":"color","groupLabel":"Color","component":"b"}
]

Retain exact IDs, grouping, and hard limits from the template. Edit component values to author a colour. Multiple stops each have their own grouping. See composition for wiring and the schema for all parameter variants.