Babylon.js is adding an opt-in option so a new WebGPU material no longer stalls the frame that first draws it.
The problem: On 9.33.0, the first draw that needs a new render pipeline creates it synchronously. In the author's test, a wave of 20 meshes with a new PBR variant cost 108 to 129 ms in that frame.
The option: `engine.asynchronousPipelineCreation`, off by default. A mesh whose pipeline isn't ready yet is skipped while it compiles, then appears a few frames later.
Results: In their tests on Chromium 147 with an RTX 3080 Laptop GPU, the slowest frame fell to 31 to 45 ms across the three modes. With the option off, the PR draws as 9.33.0 does.
Open question: Would a change letting `createRenderPipelineAsync()` take the texture state be welcome? That would let app prewarming match draws that receive depth-texture shadows.
Sign in to comment.
TL;DR of the post, generated automatically.
Babylon.js is adding an opt-in option so a new WebGPU material no longer stalls the frame that first draws it.