public readonly record struct MeshletPageClusterWhere one cluster's geometry sits inside a page, and how to decode it.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
Deliberately not the cluster record. Meshlet carries what a traversal needs to decide whether to draw a cluster — bounds, cone, error, parent error — and all of that stays resident, because a traversal has to test a cluster before it can know whether it wants its geometry. This is the other half: where the bytes are, which page they are in, and the origin they are quantized against. It is meaningless until that page is resident, which is exactly the distinction the whole phase turns on.
Fields and properties (4)
public int PageWhich page holds this cluster's geometry.
public int VertexOffsetWhere its vertices start, in bytes from the page's own start.
public int TriangleOffsetWhere its triangle corners start, in bytes from the page's own start.
public Int3 OriginThe grid coordinate its quantized positions are relative to.
Methods (1)
public MeshletPageCluster()An unplaced cluster, for the serializer.
Used by (9)
- GpuClusterCullingVixen.Rendering
- GpuClusterVisibilityVixen.Rendering
- MeshletCutVixen.Rendering.VirtualGeometry
- MeshletPageBuilderVixen.Rendering.VirtualGeometry
- MeshletPageBuilderTestsVixen.Rendering.VirtualGeometry.Tests
- MeshletPageSetVixen.Rendering.VirtualGeometry
- MeshletStreamingTestsVixen.Rendering.Tests
- Vixen_Rendering_VirtualGeometry_MeshletPageClusterSerializerVixen.Rendering.VirtualGeometry
- Vixen_Rendering_VirtualGeometry_MeshletPageSetSerializerVixen.Rendering.VirtualGeometry