csharp
public interface IEffectSourceWhere the bytes of a variant come from, before any device has seen them.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
IEffectProvider answers with an Effect, which is a thing on a device; this answers with an EffectData, which is a thing on a disk or a wire. The distinction is what lets the tiers compose: a disk cache that missed can ask the dev machine and write down what came back, which it could not do if the answer were already a set of device handles.
So the shape of the chain is: sources stack, and one EffectSourceProvider at the top turns whatever the stack produced into an effect. A shipping build's stack is one deep.
Methods (1)
EffectData? TryGet(EffectKey key)The variant for a key, or null when this source does not have it.
Used by (8)
- CountedVixen.Shaders.Tests
- EffectDiskCacheVixen.Shaders
- EffectSourceProviderVixen.Shaders
- EffectStoreVixen.Shaders
- RemoteEffectSourceVixen.Shaders
- RavenEffectCompilerVixen.ShaderCompiler
- ShaderCompilerServerVixen.ShaderCompilerService
- ShaderCompilerServiceTestsVixen.ShaderCompilerService.Tests