Marcin Ignac

Currently we only [delete the buffers](https://github.com/pex-gl/pex-context/blob/master/buffer.js#L22) and they indeed stay bound the the attribute forever (or until next buffer is bound). By `cleaned up by nulling` i think you mix...

Another thing i've seen is people using `WEBGL_lose_context.loseContext()` to force resources release although it's not an official way.

Question about pex-context syntax though : is it `fbo.blit(anotherFbo)` or `ctx.blit(fbo1, fbo2)` We don’t really have resource class methods, there some but hidden like _dispose and you still do `ctx.dispose(texture)`...

Live example here https://codesandbox.io/s/webgl-multi-sampled-mrt-fbos-1vhkif

https://github.com/mrdoob/three.js/issues/23300#issuecomment-1100666026 > Some notes (I'll repeat the obvious for the sake of being on the same page): • as mentioned above, multi-sampling for data textures is prone to error although...

Next step. Make a test case.

Why do we support cmd.indices.type at all? Is this for gltf where shared subbuffer has to be reinterpreted as index data? The problematic code in pex-renderer is here https://github.com/pex-gl/pex-renderer/blob/master/geometry.js#L123 As...

`Error: Unknown buffer type: 5125`

So this is more tricky because in `pex-context` buffers have type while in webgl they dont https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/bufferData Index element arrays and attrib buffers do https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/vertexAttribPointer https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/drawElements That's why i duplicate...

Having ctx.width will help with situations where we use different values for different things. It's better if ctx is the source of truth. ```javascript var W = 100 var H...