public record class MeshMapImageOne baked mesh map, as the file it is about to become.
Remarks
The step § D12 leaves to the caller, done once. MapBaker returns arrays of float and Vector3 and its remarks are explicit that writing them is somebody else's job, because Core/ is under the virtual-path rule. This is what that job produces: the bytes, what to call them, and what the sidecar beside them has to say so that the file means the same thing when it is read back.
⚠ Bytes rather than a path. Encoding and writing are separated so that the whole of the encoding — the row flip, the signed remaps, the settings each usage needs — is testable without a project, a database or a disk, which is most of what can be wrong here.
Fields and properties (4)
public required MeshMapUsage UsageWhat this map measures.
public required byte[] PngThe PNG.
public required TextureImportSettings SettingsHow the texture importer must read it.
public float ScaleWhat an encoded value is multiplied by, or zero where the map is not quantized.
Used by (6)
- ContentTasksVixen.Editor.App
- IMeshMapBakerVixen.Editor.Assets
- MeshMapBakeVixen.Editor.Assets
- MeshMapEncodingTestsVixen.Editor.Assets.Tests
- ProjectMeshMapBakerVixen.Editor.App
- RecordingBakerVixen.Editor.App.Tests