public record class BufferUploadAssetHost bytes into a buffer the frame declared.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
What the document decides is where the copy goes and what it fills; what the host supplies is the bytes — through Uploads, or through the node's own OnUpload. That division is the same one GpuCulling already has, and for the same reason: a file can say a histogram starts cleared, and cannot say what this frame's emitters are.
A node whose bytes nothing ever sets declares no pass at all, which is what an authored frame running against a host that has not wired it up should cost.
Fields and properties (4)
public string NameThe node's name, for debug groups and for a human reading the file.
public bool EnabledWhether the node runs.
public string BufferThe buffer to fill, which must be declared as a copy destination.
public long OffsetWhere in that buffer the bytes land.
Used by (5)
- BufferTransferTestsVixen.Rendering.Tests
- CompositorBuilderVixen.Rendering
- TypeRegistrationVixen.Rendering
- Vixen_Rendering_Compositor_BufferUploadAssetSerializerVixen.Rendering
- BufferUploadNodeVixen.Editor.AssetEditors