Frame lifecycle and GPU completion¶
The host opens a frame, submits work through ready view/scene entry points, and closes that frame. CPU recording, GPU completion, and presenting an image are separate events.
Frame admission¶
BeginFrame uses the synchronous admission contract. TryBeginFrame
lets the caller handle a busy scheduler without blocking. The async
admission APIs use the supplied Core execution and cancellation routes.
Consume the result before using the runtime as an open frame.
A successful admission must be matched with EndFrame.
Submitting multiple views within the admitted frame is permitted by their
target and graph contracts. An unsuccessful render does not implicitly
close the host frame. The example in Render to a texture shows both
success and failure paths.
Completion¶
GpuCompletionPoint represents
accepted GPU work in a form the active runtime can query. Use
QueryGpuCompletion for a nonblocking state and
WaitForGpuCompletionAsync when joining through Core. Use the point from
the operation that last touched the resource. An earlier point cannot
protect a later submission.
Prepare new pass resources and material variants off the recording path. An edit that changes topology or shader code prepares another generation before publication. Close the host frame before committing live graph mutations. See Frame graphs and typed render profiles.