RGB16F driver bug on Mac+Intel in conformance/extensions/oes-texture-half-float.html
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: jgilbert, Assigned: jgilbert)
References
Details
(Whiteboard: gfx-noted)
Attachments
(2 files)
If an RGB16F texture is ever cleared to ClearColor(0,0,0,0)
or (0,0,0,1)
, it will later sample as if it were RGBA16F with (R,G,B,A)
instead of (R,G,B,1.0)
.
Even setting the texture swizzle channels to R,G,B,ONE doesn't fix it.
Using ClearColor(0,0,0,0.5)
(at least) avoids this driver bug.
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•6 years ago
|
||
It's pretty wild.
Fortunately, RGB16F is only optionally color-renderable in webgl1's EXT_color_buffer_half_float, and is explicitly not color-renderable in webgl2's EXT_color_buffer_float.
For portability's sake, we should try never allowing RGB16F to be color-renderable.
Assignee | ||
Comment 3•6 years ago
|
||
There's a crazy driver bug here on Mac+Intel, but if we're forbidding it
there, why not everywhere.
It's optional in EXT_color_buffer_half_float for webgl1, and no allowed by
EXT_color_buffer_float for webgl2 anyway.
MozReview-Commit-ID: kI9DUj8TU8
Comment 5•6 years ago
|
||
bugherder |
Description
•