FNiagaraComputeExecutionContext

Used to track if we have processed any ticks for this context this frame.

Do we have a reset pending, controlled by the game thread and passed to instance data.

Dynamic state updated either from GT via RT commands or from the RT side sim code itself.

The CPU instance count at the time the GPU count readback was issued. Always bigger or equal to the GPU count.

The current maximum instances we should allocate on the RT.

The current maximum of instances on the RT.

The current number of instances on the RT Before ticks are processed on the RT this will be CurrentData's NumInstances As ticks are processed (or we generated the tick batches) this will change and won't be accurate until dispatches are executed

Used only when we multi-tick and need to keep track of pointing back to the correct FNiagaraDataBuffer.

Most current buffer that can be used for rendering.

Persistent layouts used to create the constant buffers for the compute sim shader

The offset at which the GPU instance count (see FNiagaraGPUInstanceCountManager()).

Game thread spawn info will be sent to the render thread inside FNiagaraComputeInstanceData.

Particle count read fence, used to allow us to snoop the count written by the render thread but also avoid racing on a reset value.

Optional buffer which can be used to render translucent data with no latency (i.e. this frames data)

Render thread data.