public enum MaterialMapUsageWhat one output of a texture graph is, which is how a bake knows where to put it.
Remarks
docs/plan/48 § 4.8's Output usages, verbatim. An Output node declares one of these and the bake does the rest — which file it lands in, which channel of it, what the sampler is told the bytes mean, and which material feature reads it.
⚠ Nine usages and seven files, because three of them share one. Orm is Occlusion, Roughness and Metalness in R, G and B — the packing TexturedOrmFeature reads, and the reason a material spends one streaming page on three measurements instead of three. So a usage is not a file, and the two are separate types rather than one enum somebody later assumes is both.
Fields and properties (9)
BaseColorAlbedo, seen by a person. Its alpha is coverage.
NormalThe tangent-space normal.
RoughnessPerceptual roughness. Packed into Orm's green.
MetalnessHow much of a conductor the surface is. Packed into Orm's blue.
OcclusionHow much light reaches the point. Packed into Orm's red.
HeightDisplacement along the normal.
EmissiveEmitted radiance.
OpacityCoverage as its own map, read from red.
MaskA mask this graph produced for another graph, or for a layer stack.
Used by (10)
- BakedMaterialImageTestsVixen.Graphics.Golden.Tests
- MaterialBakeVixen.Editor.Assets
- MaterialBakeAssetTestsVixen.Editor.Assets.Tests
- MaterialBakeRouteVixen.Editor.Texturing
- MaterialBakeRouteDeviceTestsVixen.Editor.Texturing.Tests
- MaterialBakeTestsVixen.Editor.Assets.Tests
- MaterialMapNamingVixen.Editor.Assets
- TextureCommandTestsVixen.Cli.Tests
- TextureGraphRunnerVixen.Cli
- TextureRunnerVixen.Cli