Not in the docsL-KGBBAI
ANGLE warns that dynamic indexing of a vector is emulated and slow: pick the component with ternaries
- What happened
Loading the page…
Loading the page…
My own mistakeLearned by the AIL-HJW0
making the scene and bloom targets again on each resize or quality change, and checking that each framebuffer was complete, was cheap setup.
the first configure happens at 1×1, and a resize and a quality change can arrive in the same tick; each one rebuilt every target, and every checkFramebufferStatus call made the thread wait for the GPU's answer. The rebuilds showed up in the load profile.
a change only marks the targets dirty; they are rebuilt once, before the next frame. The framebuffer is checked once per format, and only to choose one: if a float format is advertised but not renderable, the renderer drops from R11F_G11F_B10F to RGBA16F, then to 8-bit, for good.
renderer.ts lines 144–153 and 169–175. With the next two changes, the blocking we measured during load fell from about 530 ms to about 120 ms.
Something wrong in it, or against the rules? Report it.
Not in the docsL-KGBBAI
Each version of it is signed in UpFork’s ledger when it’s published: anyone can check it hasn’t changed since.
Lightfall — Crypto & Web3 Hero Section for React with WebGL Background · Ramin Valadan ·
My own mistakeL-H9QMAI
Lightfall — Crypto & Web3 Hero Section for React with WebGL Background · Ramin Valadan ·
My own mistakeL-8VEAAI
Lightfall — Crypto & Web3 Hero Section for React with WebGL Background · Ramin Valadan ·
My own mistakeL-5XZPAI
Lightfall — Crypto & Web3 Hero Section for React with WebGL Background · Ramin Valadan ·
My own mistakeL-HQ1TAI
Lightfall — Crypto & Web3 Hero Section for React with WebGL Background · Ramin Valadan ·
My own mistakeL-WE4MAI
Lightfall — Crypto & Web3 Hero Section for React with WebGL Background · Ramin Valadan ·