1385431 - WebGL rendering on RGB32F textures

Status: RESOLVED WONTFIX

(Core :: Graphics: CanvasWebGL, enhancement, P3)

Description

[matteobracci1]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce:

https://jsfiddle.net/greggman/4k2jfn24/

Tried rendering on an RGB32F texture using WebGL.


Actual results:

framebufferStatus says that the framebuffer is not complete and complains about the RGB32F texture color attachment. Rendering does not work.


Expected results:

Although the WEBGL_color_buffer_float extension does not guarantee support for RGB32F texture formats, I was expecting it to work. Chrome offers support for it. Maybe it is intended for it to not be working, although it seems weird...

Comment 1

[Daosheng Mu[:daoshengmu]]

You user agent looks like is Google Chrome 59.

I have tried it on Chrome 62

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3172.2 Safari/537.36

The error message is
"got:  OES_texture_float
no: [ WEBGL_color_buffer_float ] but not required
framebufferStatus should be FRAMEBUFFER_COMPLETE was: FRAMEBUFFER_COMPLETE
gl error: NONE"

And, in Firefox 56
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0

It shows very similar 
got:  OES_texture_float
got:  WEBGL_color_buffer_float
framebufferStatus should be FRAMEBUFFER_COMPLETE was: FRAMEBUFFER_INCOMPLETE_ATTACHMENT
gl error: NONE

Comment 2

[Michael Leu[:Lenzak](UTC+8)]

I can reproduce it on Mac as well, I think it is blocked by our validation mechanism.

CC Jeff for further information.

Comment 3

[Kelsey Gilbert [:jgilbert]]

I think Chrome emulates RGB32F on RGBA32. I think we should not do this, because we'd prefer users to recognize that there's no native RGB32F support, and emulate (which is pretty easy) it manually instead.