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

Mark Callow [email protected]
Fri Sep 16 11:39:15 PDT 2011

I do not think so. We have gone to great lengths before, e.g.
UniformLocation, to avoid situations where incorrectly written programs
will run on some GPUs but not others. Why is it suddenly necessary to
abandon the principles we established?



On 2011/09/16 11:14, Kenneth Russell wrote:
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://khronos.org/pipermail/public_webgl_khronos.org/attachments/20110916/8d056a52/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: callow_mark.vcf
Type: text/x-vcard
Size: 394 bytes
Desc: not available
URL: <http://khronos.org/pipermail/public_webgl_khronos.org/attachments/20110916/8d056a52/attachment.vcf>

More information about the public_webgl mailing list