Vixen
02b45cc4
csharp
public static class VirtualGeometryContent

Reads what ModelImporter wrote, and registers it so a frame can draw it.

No guide page documents this yet — the page shows what the code says about itself.

Remarks

The caller Register was written for. A build produces two chunks per clustered mesh — the records under ClusterArtifact and the page blob under ClusterPageArtifact — and until this existed nothing outside the importer's own tests read either of them back. The system was complete from import to shaded pixel with no way to get from one to the other.

Bytes in, not an address. What produces the bytes is the caller's — AssetManager in an application, a file in a sample, an array in a test — and putting a content pipeline in this signature would mean the renderer knew what a bundle was. What it does know is the two formats, which it owns.

The blob is a stream and stays one. StreamMeshletPageSource seeks into it per page, which is what makes residency demand-driven; handing it an array would load the mesh whole and leave the streaming machinery reading out of memory it had already paid for.

Fields and properties (2)

  • public const string ClusterArtifact

    The artefact name a build writes the hierarchy and page records under, together.

  • public const string ClusterPageArtifact

    The artefact name the page blob is written under.

Methods (3)

Used by (4)

  • VirtualGeometryContentTestsVixen.Rendering.Tests
  • VirtualGeometrySystemVixen.Rendering
  • ImportedGeometryLoadsTestsVixen.Editor.Assets.Tests
  • ModelImporterVixen.Editor.Assets