[Public WebGL] WebGL2 element array buffer and copy buffer (5.1 Buffer Object Binding)

Jeff Gilbert ([email protected]) [email protected]
Mon Jul 20 12:00:39 PDT 2020

We would need to check whether we do indeed have RBAB everywhere we
have WebGL2. Otherwise, we'd need more info on how this enables
compelling workloads, to offset the downside of Apps accidentally not
working on a number of older desktop and mobile drivers.

Worth considering for your usecase (complicated vertex fetch) is
vertex-pulling, which should be possible with vanilla WebGL 2.

On Mon, Jul 20, 2020 at 5:51 AM Kevin Rogovin
([email protected]) <[email protected]> wrote:
> Hi,
>  Hopefully this thread necromancy will live on the correct thread still.
> > ANGLE does use the GPU for robust buffer access when using the D3D11 backend (most windows users).  D3D9 always validates index ranges on the CPU.  We also rely on the Vulkan or OpenGL extensions to do it when available on other platforms.
> What do people think of having an extension for WebGL2 that: removes the restriction jazz of ELEMENT_ARRAY_BUFFER and gives an assurance to an application that robust access is used for fetching vertices via an index buffer, i.e. the implementation won't induce a CPU inspect of an index buffer.
> I can draft the extension, but I would like to feel the water on this.
> My use case, which a follow up question on a different thread will address in more detail, is for GPU generated index buffers. Right now, I have scenes where instancing is not sufficient but I manage to get the GPU to generate my vertex buffers entirely. I have  a scene of 1.5 million vertices; for these loads the actual vertex count is 1 million and the index count is 1.5 million.; getting the index buffer generated by GPU is a big performance gain for these kinds of scenes (something like 3N ms/frame without index buffer and 2N ms/frame with index buffer) for some value of N.
> Best Regards,
>  -Kevin Rogovin

You are currently subscribed to [email protected]
To unsubscribe, send an email to [email protected] with
the following command in the body of your email:
unsubscribe public_webgl

More information about the public_webgl mailing list