3 ms·
Works very well on my mid-2012 MBP in OSX 10.10 with a puny Intel HD4000 GPU! The framebuffer completeness check error is a result of some early confusion arou
by flohofwoe 12y ago
Works very well on my mid-2012 MBP in OSX 10.10 with a puny Intel HD4000 GPU!
The framebuffer completeness check error is a result of some early confusion around the OES_texture_float WebGL/OpenGLES extension. Most browsers interpreted this as being able to both read from a floating point texture, as well as render to a floating point frame buffer. But some (mobile) GPUs can sample fp textures but not render to them. So later another extension was introduced to clean this up (WEBGL_color_buffer_float and others) which specifically handles rendering to fp render targets, while OES_texture_float is restricted to sampling textures. But this is not widely supported yet, and most desktop browsers still support rendering to fp render targets even they only expose the OES_texture_float extension in order to not break backwards compatibility. Because of this, some WebGL code which runs on desktop browsers breaks on some mobile devices even though the code 'properly' checks for extensions.