Vixen
02b45cc4
csharp
public interface IVfxEffectSource

Where the effect a VfxEmitter names comes from.

Read the guide page for this →

Remarks

IMaterialSource's shape, one asset kind along, and for the same reason: Vixen.Rendering links no asset manager. An extraction system asks for a graph by reference and is told whether it is ready; what turns a reference into an address and an address into bytes is the content stack's business, which sits above this one.

A compiled graph rather than the content record, because the conversion is not free: VfxEffectContent.ToGraph runs the validation that refuses an updater reading what nothing writes, and doing it per emitter per frame would be doing it a thousand times for an answer that cannot change. An implementation caches; the interface says so by handing back the compiled form.

⚠ The graph is shared between every emitter that names it. A VfxCompiledGraph is immutable data — that is the property the whole dual backend rests on — so one asset is one graph however many VfxSystems run it, and an emitter's own state lives in the system rather than the graph.

Methods (1)

Used by (4)

  • AssetVfxEffectSourceVixen.Engine.Renderer
  • SourceVixen.Rendering.Tests
  • VfxExtractionSystemVixen.Rendering
  • WorldRendererVixen.Engine.Renderer