csharp
public sealed class MemoryMeshletPageSourceReads pages out of page sets already in memory, which is what an unstreamed build has.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
Synchronous behind an asynchronous signature, and honestly so: the bytes are already here, and pretending otherwise would put a thread hop in front of a memcpy. What a real content pipeline supplies instead reads from the bundle — see docs/plan/08 — and nothing about the pool changes when it does.
Methods (2)
public void Add(int source, MeshletPageSet pages)Registers a mesh's pages under a source id.
public ValueTask<int> ReadAsync(PageKey key, Memory<byte> destination, CancellationToken cancellation)Reads one page's bytes.
Used by (3)
- ClusterResolveTestsVixen.Rendering.Tests
- CompositorAssetTestsVixen.Rendering.Tests
- VirtualGeometryFrameTestsVixen.Rendering.Tests