MeshMapReference

Remarks

Doc 48 § 4.8's binding, as a string, because that is the only thing that crosses. A compilation may not open an asset database — it runs on every edit and a preview is one — so what a Mesh Map node puts in TextureGraphExternal.Asset is a reference and a host resolves it. For a Source/Bitmap that reference is a project-relative path; for a mesh map there is no path to write, because the whole point is that the graph does not know which mesh it is about to be baked for.

⚠ So the grammar is a scheme — meshmap:curvature — and it is deliberately not a path. A path would have to be a lie about some particular mesh, and a host reading one could not tell the lie from a real reference to a file an artist happened to wire in by hand. The scheme makes the two kinds of external distinguishable by looking, which is what lets a bake with no mesh refuse a generator with a sentence rather than fail to open Assets/MeshMaps/curvature.png.

Fields and properties (1)

• public const string Scheme

  The scheme a mesh-map reference is written under.

Methods (3)

• public static string For(MeshMapUsage usage)

  What a graph writes to ask for one map.

• public static bool IsMeshMap(string? reference)

  Whether a reference is one of these at all.

• public static bool TryParse(string? reference, out MeshMapUsage usage)

  Reads a reference back into the usage it names.

Used by (2)

• MeshMapBindingVixen.Editor.Assets
• MeshMapGeneratorBindingTestsVixen.Editor.App.Tests