csharp
public interface IRenderGraphQueuesWhere the graph gets a command list per segment, and what it does with it after.
Remarks
The seam exists because submission is not the graph's business anywhere else either: Execute records into a list the caller opened, finishes nothing and submits nothing. A frame on two queues cannot work that way — the graph decides how many lists there are — so it asks for them, and hands each one back the moment it is full.
⚠ The implementation owns the waiting. WaitsOn says what must have finished; how that is enforced is a property of the device. DeviceQueues is the one to use — it waits by value where the device has timeline semaphores and drains the producing queue where it does not.
Methods (2)
ICommandList Begin(RenderGraphSegment segment)Opens a list for a segment.
void Submit(RenderGraphSegment segment, ICommandList list)Takes a segment's list back, recorded.
Used by (7)
- DeviceQueuesVixen.Graphics.RenderGraph
- RecordingQueuesVixen.Graphics.RenderGraph.Tests
- RenderGraphVixen.Graphics.RenderGraph
- SceneRenderHostVixen.Engine.Renderer
- SerialisedQueuesVixen.Graphics.RenderGraph
- TimelineSubmissionTestsVixen.Graphics.RenderGraph.Tests
- WrongQueuesVixen.Graphics.RenderGraph.Tests