Development

Runtime ownership and extension

Use one runtime as the owner of the selected device, retained objects, resources, and execution. Core owns windows, event pumping, worker executors, and the host’s shutdown policy. Passes declare dependencies and record commands. A profile is an authored collection of those passes and its valid terminal outputs.

Compose through canonical handles

  • A RenderScene contains retained scene objects and lights and accepts frame-local submission packets.

  • A RenderView describes the current camera, extent, and view identity.

  • A RenderProfileHandle selects a frame graph owned by the runtime. Different profiles can share the same device and resource authorities.

  • A surface or render target determines the format and size of presentation. The application can submit multiple views and can render without a window.

The stock OpenPBR and probe-capture factories return bundles containing actual handles and pass state. Use the handles through the canonical runtime. Build directly against its graph APIs when the supplied composition is too restrictive. See Frame graphs and typed render profiles.

Join asynchronous operations

Expensive preparations accept an explicit PassResourcePreparationContext. Its routes are supplied by the caller. Drive the host owner, workers, and any host-driven completion or deadline services until the task joins. Keep the runtime, scene, profiles, and captured inputs alive through that boundary. Cancellation requests an orderly return. GPU use can extend lifetime after a CPU task has joined.

Make separate decisions for source and native content

A development tool can cook source assets and compile eligible shaders. A shipping configuration can consume prepared content without the authoring modules. Platform compilation policy, shader capability, and actual pipeline availability are separate conditions. Query and propagate their results.