[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)

Shouldn't the existing need to check the framebuffer's status be
sufficient? Applications that don't check for FBO completeness are by
definition incorrectly written. These applications already have to
request the floating-point texture extension from WebGL.


On Fri, Sep 16, 2011 at 11:08 AM, Mark Callow <callow_mark@hicorp.co.jp> wrote:
> Would you object to having to modify your applications to explicitly enable
> rendering to floating point buffers?
> It is the high probability that this far from universally supported feature
> will be used without the developer realizing that it is optional that is
> causing my objections.
> Regards
> -Mark
> On 2011/09/15 16:04, Florian Bösch wrote:
> I heard there was some discussion on disabling floating point texture
> writing to fbos
> I'd like to point out that:
> - Some of my demos use this, and it would break them:
> http://codeflow.org/entries/2011/apr/13/advanced-webgl-part-2-sky-rendering/
> http://codeflow.org/entries/2011/apr/11/advanced-webgl-part-1/
> - I had planned on continued support of this functionality for
> upcoming applications

You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl