webgpu-impl-instancing-indirect

WebGPU instanced rendering corrupts geometry when buffer layouts use incorrect indirect record sizes or incomplete u32 parameters. Enforcing exact 4-byte aligned offsets and complete parameter writes prevents silent instance data misplacement.

GPU-driven culling uses compute shaders to write draw parameters into buffers, then calls drawIndexedIndirect to execute rendering. You must enforce exact indirect record sizes and 4-byte aligned offsets to prevent draw corruption.

WebGPU 1.0 treats multiDrawIndirect as experimental and requires feature gating. You must check for indirect-first-instance and multiDrawIndirect support, using stable loop-based fallbacks if features are unavailable.

dispatchWorkgroupsIndirect requires complete u32 records with exact 4-byte aligned offsets. Compute shaders must fully write these parameters into the buffer to avoid silent dispatch errors.

Large particle systems use instanced rendering with instanceCount or drawIndirect to keep the CPU out of the hot path. Correctly structuring indirect buffers and validating firstInstance handling ensures accurate multi-draw workflows.

Feature gating for indirect-first-instance is required when using drawIndirect or drawIndexedIndirect with a starting instance offset. Checking this WebGPU feature prevents silent draw bugs during GPU-driven rendering workflows.