Vixen
dd8b0a81
csharp
public static class TextureGraphExternals

Between a compiled graph's external images and the textures an evaluation reads them from.

Read the guide page for this →

Remarks

The step that would otherwise be written out at every bake, and there is going to be more than one. A compilation says which images the caller supplies and what fills them — Externals — and TextureUploads puts bytes on a device; joining the two is a four-line loop, and a four-line loop copied into a CLI verb, a panel and a content build is three places to forget an entry.

⚠ What it deliberately cannot do is resolve an asset. An entry naming one is handed back rather than skipped, because skipping it would produce a plan that is missing exactly one texture and an exception at Evaluate about an image index. A host with an asset database reads what came back, loads each picture and uploads it — and a host without one can see, before it starts, that this graph is not one it can bake.

Methods (1)

Used by (5)

  • TextureCompoundBakeDeviceTestsVixen.Editor.TextureGraph.Tests
  • TextureExternalGraphDeviceTestsVixen.Editor.TextureGraph.Tests
  • TextureExternalImagesVixen.Editor.Texturing
  • TextureGraphPreviewsVixen.Editor.TextureGraph
  • TextureGraphRunnerVixen.Cli