Namespace Apogee.Graphics.Metal¶
Classes¶
The bindless textures, samplers and storage images as one Metal argument buffer, buffer 1 of every shader that reads them (see ParameterBlock<BindlessResources> in common.slang). In an argument buffer of
tier 2 each resource of an array takes one 8-byte slot and a struct's members follow one another, so the buffer is the runs of
A Metal buffer. Device-local buffers are private (the GPU's), upload and readback buffers are shared and mapped for their whole life.
A Metal command buffer being recorded. Metal has encoders where Vulkan has one command buffer: this opens the one the next command needs (render, compute or blit) and ends the one that is open.
Metal does not order what a shader reaches through an address or an argument buffer, so the encoders form a chain, each waiting for a fence that the one before it updates: that is what the barriers of the
render graph mean here (there are no image layouts to change, so
The Metal implementation of
A Metal call failed or the machine cannot do what the engine needs; the message says which.
The Metal frame loop: a few frames in flight, each with its own upload arena and command buffer, and one shared event as the timeline (its value is the number of frames the GPU has finished).
With a swapchain it takes the next drawable and presents it; without one it renders headless. GPU timings are not measured yet, so
A Metal texture, or a window's drawable texture that is borrowed for a frame (
A view of a Metal texture. The image's own view borrows the texture; views made with
Records a command buffer, commits it and waits for it: for loading and tools. The calls are serialized.
A Metal compute pipeline, or a render pipeline with the fixed-function state Metal sets on the encoder (depth test, culling, winding).
The images of a window: a CAMetalLayer that SDL made for it (the window needs