[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] readPixles() can't access float values (OES_texture_float interaction)

That means we need an extension for RGB8 and RGBA8 as well?

And following the WebGL model of no extension feature is exposed to WebGL unless you call getExtension this means breaking every WebGL program that uses FBOs currently because I can pretty much guarantee, none of them ask for 565, 4444 or 5551 textures for their FBO textures. All of them are making 888 or 8888.

On Thu, Sep 1, 2011 at 12:21 PM, Mark Callow <[email protected]> wrote:

As I pointed out before, the core spec. does provide a guarantee. It says that the RGB565, RGBA4444 & RGBA5551 internal formats are color renderable and that NO other format is color renderable. Regardless of the confusion about how an application can guarantee to create a texture with one of these internal formats, it is very clear that an FP texture is not going to have one of these internal formats and will therefore not be color renderable.

An extension is required in OpenGL ES and in WebGL.



On 2011/08/31 21:11, Gregg Tavares (wrk) wrote:
As far as I recall, OpenGL ES 2.0 makes no promises about what types of textures can be bound to frame buffers. The only way to know is to bind one and then call glCheckFramebufferStatus.  

So, do we need a specific extension to enable rendering to floating point textures or is the current situation good enough?