You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Black blocks spread over grass and trees in scenes with a pond (browser, not reproduced) #84
In the browser (Chrome, WebGPU), scenes that have a pond sometimes show black blocks on the grass, trees and path, away from the pond itself. Once it starts, the black spreads from frame to frame across clusters. Turning the camera fully away clears it.
Seen first in solstice-garden, then in the (paused) editor after adding a pond.
Random: no reliable steps. A guess from the reporter: it happens when the GPU is "full".
Blocks have screen-aligned, stepped edges (about 8 px), which suggests a screen-space or temporal pass is carrying it.
Weather (clear, storm), time of day (day, sunset), Low/Medium/High and switching between them, window resize, pond size and depth, Zorah's ponds, the editor island with the sea removed and restored.
Injecting NaN or Inf into the pond pass's colour, depth and motion, for one frame or permanently: D3D12 drops NaN at max (natively and in Chrome), and a bad pixel stays a dot for a few frames; it does not spread.
The pond's bind-group caching, the HZB (built from the opaque visibility buffer only), the GI volume (never reads the screen) and the wind maths: no path carries a bad value across frames.
The garden with tiny streaming budgets (?geometry-mb=64&texture-mb=24) and the camera churning pages, a native render loading the GPU alongside, and 16 GB of VRAM held by another tab while the garden reallocated. 0 GPU errors throughout.
Not tried: device loss or reset under real VRAM exhaustion.
Next time it happens
Leave it on screen and check, in that tab: the GPU errors count, pages_starved(), and the debug views (lit, albedo, normals) to see which pass draws the black. Also note whether the scene has a sea, and the Quality setting.
A drafted mitigation, not applied for lack of evidence: zero non-finite values (bit test on the exponent) where the TAA, screen GI, reflection and cloud histories are written, and where the GI reads last frame's image.
Activity
SamG-Coder commentedon Nov 13, 2026
#85