MeshMapRunner

Remarks

docs/plan/48 § 4.8's binding, made visible. A Mesh Map Input node asks for a usage and is handed whichever file this project's bake produced; the whole of that lookup is MeshMapLibrary, and the whole of this verb is running it and printing what came back. So the question an artist actually asks — why is my Curvature Edge Wear binding nothing on this mesh — has an answer that does not require opening the panel that is failing.

⚠ The point of it being a verb is that it is a second caller. The read side landed with no consumer at all — #702 — and a resolver whose only caller is a node that does not exist yet is the finished-thing-nothing-calls shape this repository produces most often. ⚠ That node exists now: Source/Mesh Map is registered by NodeTypes and resolves through the same index, so this is no longer the only reader — it is the one a person can run, and a project in which the verb finds nothing is a project in which the node binds nothing.

⚠ It scans before it indexes. A library is a snapshot over the asset database, and a database loaded from its committed index knows only what the last editor session saw — so a bake run from another process would be invisible, which for a verb whose whole job is "what is there" is the wrong answer rather than a stale one.

Methods (1)

• public static ExitCode List(Project project, string set, string usage, TextWriter output, TextWriter error)

  Lists a project's baked mesh maps, or resolves one.

Used by (1)

• VixenCommandVixen.Cli