WebGPU unavailable
Use HTTPS or localhost and a browser with WebGPU enabled. Check hardware acceleration, browser policy and GPU driver support if no adapter is returned.
DEVICE CAPABILITIES / SCENE REQUIREMENTS
Before the first sample.
Check which scenes fit this device’s WebGPU limits, and what might prevent a render.
YOUR DEVICE
Checking WebGPU…
Requesting the same device limits as the renderer. No scene is loaded and no render starts automatically.
PREPARED ASSET INVENTORY
Scene compatibility
Widths preserve each view’s aspect ratio, just like the renderer. These checks allocate no scene buffers, including at 2K and 4K.
*Known GPU data adds requested buffers, the film, the uniform buffer and texture texels. It excludes driver padding, the browser’s canvas surfaces, upload staging and other applications. CPU scene copies need additional system memory. Expand a view for details.
OPTIONAL EXECUTION CHECK
Can the renderer execute?
Compile Astra’s actual shaders and render one sample of a synthetic 32 × 32 scene. This checks GPU execution and readback; it does not test large allocations or predict render time.
Waiting for your command.
Adapter and device limits / what the renderer can actually use
The adapter advertises hardware/browser capacity. The device exposes the limits granted to Astra’s request; validation uses those device limits. No optional WebGPU features are required.
| Limit | Adapter | Renderer device |
|---|
When limits fit but rendering fails
Out of memory
Close other GPU-heavy tabs and applications. A smaller film reduces memory use, but it cannot shrink a scene’s geometry, texture array or environment buffers.
Device lost or shader failure
The browser may reset a device after a driver fault or a long GPU workload. Retry in a fresh tab, update the browser/driver, and include the downloaded diagnostic report when reporting the issue.