CubeCom Pro Docs
3D Editor

3D Editor

Current Editor authoring scope and the boundaries between Editor, Backoffice, and API capabilities.

The 3D Editor is a canvas-first workspace for technical artists and 3D specialists. Today it inspects an attached glTF model and edits existing SET_MATERIAL and SET_VISIBILITY bindings. Do not infer Editor UI support merely because a capability exists in the domain model or GraphQL schema.

Capability matrix

CapabilityDomain / APIBackofficeEditor UI today
Set materialSupported and validatedCreate in 3D StudioEdit hydrated bindings
Set visibilitySupported and validated on updateCreate in 3D StudioEdit hydrated bindings
Replace componentSupported; linked OBJECT revision requiredContract is callable; no verified product-workspace controlShown as unsupported; not editable
Set modelEnum and generic value contract exist; production value semantics are not establishedNo verified controlShown as unsupported; not editable
Create targetSupportedCreate in 3D StudioNot available
Register componentSupported for linked OBJECT revisionsNo verified product-workspace controlNot available

“Supported” in the API column means the current schema and service expose the operation. It does not promise a complete operator workflow or a renderer implementation.

Topics

GuideWhat you accomplish
ModelsUnderstand model assignment and inspect the attached model
Scene objectsNavigate the glTF node tree and understand ModelTarget anchors
MaterialsConfigure PBR metallic-roughness materials and texture maps
ComponentsUnderstand API-level component registration and Editor limitations
VisibilityEdit hydrated SET_VISIBILITY bindings to show or hide scene parts
Visual bindingsUnderstand how choice values trigger visual operations
Replace componentUse the API/runtime contract and understand the missing Editor control
Set materialEdit SET_MATERIAL operations to swap surface finishes
Set modelUnderstand the schema-only operation and current authoring limit
Preview & testInteractively test option switching inside the Studio before publishing
TroubleshootingDiagnose missing node paths, unresponsive bindings, and transform offsets

On this page