Compositor

The Compositor combines multiple published products in one saved scene. Use it for space planning, side-by-side comparison, product groupings, and compositions that can be loaded by a supported runtime client.

Start a composition

1. Open Tools, then Compositor. The tool is independent of the card currently open in the workspace.
2. Add Lounge, Ottoman, or Lounge + Ottoman from Published products. This first product slice resolves the pinned catalog revision for each PID.
3. Select a product in the viewport or in Scene objects.
4. Move, rotate, or scale it with the transform gizmo or numerical fields.
5. Configure product options from that product's published manifest.

Select and place products

• Click a product to select it. Click empty space to clear the selection.
• Hold Shift and drag on empty space to window-select multiple products.
• Enable bounds snapping to align products by their bounding boxes.
• Enable spacing dimensions to inspect distances between products.
• Hold Shift while beginning a transform to create and place a lightweight instance.

Instances share the source product resources but retain their own transform and product selections.

Product configuration

Each scene object owns its configuration state. Changing one option updates the affected product branch without rebuilding unrelated products or resetting the scene.

The Compositor uses the same published manifest, selection resolution, shader resolution, and transform-node behavior as the single-product runtime. A client-specific runtime may change presentation, but not application logic or asset truth.

Save and access a composition

1. Open Save & export.
2. Give the composition a useful name and version note.
3. Choose Private, Organizational, or Public access.
4. Save with an access key. A key is required at every scope.

Saved state includes PID, publication revision, option selections, canonical Signature, transforms, instances, camera state, and tool-supported scene settings.

Runtime modes

Runtime mode controls the client and is not stored as a property of an individual product object.

• Expanders resolves product selections from the product manifest.
• Signature addresses a product by its stable product identity and submits signature data for that product. A signature index alone is not a safe cross-product identifier.

Both modes operate on the same composition and product truth. Export Runtime products writes the plural Signature input, including every instance transform.

Humanscale Signature presentation

The custom <vertcie-humanscale-signature-compositor> element presents a multi-product Signature composition with the same five generated views, turntable behavior, camera constraints, lighting, toolbar, and contact shadows as the singular Humanscale Signature runtime. Load it from https://cdn.vertcie.com/runtime/vertcie-humanscale-signature-compositor.js. It uses the generic compositor data contract and forces Signature mode; product configuration remains independently addressed by Key.

In Runtime Catalog, open a composition runtime, open Props, and select Humanscale Signature. Signature entry remains a Catalog-only test control and is not added to the production custom element. The active Lounge + Ottoman composition currently preserves the Ottoman transform at position [0, 0, 0.75], rotation [0, 0, 0], and scale [1, 1, 1].

Troubleshooting

• If a product is unavailable, verify that it has an active runtime publication.
• If material behavior differs from Preview & Publish, compare the active publication and its asset-card references.
• If a selection fails, inspect the product's published manifest rather than copying option assumptions from another product.
• Use Logs & Reporting to capture the request, result code, and product identity before changing data.