@pixi/3d
    Preparing search index...

    Interface ParticleContainerViewsAdvanced

    Typed-array views over the particle vertex buffer, for code that writes particles itself instead of through setParticleAt

    All three views share one ArrayBuffer. Each particle is 4 consecutive vertices holding the same data. Vertex v's position starts at f32[v * floatStride], and any other attribute sits offsets[name] / 4 elements after that. Call markDirty for what you write.

    interface ParticleContainerViews {
        f32: Float32Array;
        floatStride: number;
        offsets: Readonly<Record<string, number>>;
        u16: Uint16Array;
        u32: Uint32Array;
        vertexStride: number;
    }
    Index

    The buffer as floats: position, size, rotation, and the float attributes of extra bits

    floatStride: number

    Elements per vertex in ParticleContainerViews.f32 and ParticleContainerViews.u32: 6 for a plain system, 8 with frames, more with extra bits' attributes; twice that in ParticleContainerViews.u16

    offsets: Readonly<Record<string, number>>

    Byte offset of each attribute within a vertex, by name, built-ins and extra bits' alike

    The buffer as 16-bit words, for the unorm16x4 flipbook frame of a system with frames

    The buffer as 32-bit words, for packed attributes such as the unorm8x4 colour

    vertexStride: number

    Bytes per vertex: 24 for a plain system, 32 with frames, more with extra bits' attributes