filament: WebGL samples no longer work on Windows
Describe the bug I tried to view a sample of Filament tutorial_triangle in Chrome 87. However, an error appeared in the console and no triangles were displayed on the screen.
To Reproduce Steps to reproduce the behavior:
- Launch Chrome 87.
- Go to the following page https://google.github.io/filament/webgl/tutorial_triangle.html
- Check the console.
The following error is output to the console and the triangle is not displayed on the screen.
GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
GL_INVALID_FRAMEBUFFER_OPERATION: Draw framebuffer is incomplete.
Expected behavior
The assumed result is a triangle on the screen and no error output to the console.
Screenshots If applicable, add screenshots to help explain your problem.
| Chrome 87.0 | Firefox 82.0 |
|---|---|
![]() |
![]() |
Desktop (please complete the following information):
- OS: Windows 10 Version 1909
- GPU: Intel UHD Graphics 617
- Backend: ANGLE
- Browser: Chrome 87.0.4280.66
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (4 by maintainers)
Commits related to this issue
- WebGL: RGB16F is not color renderable. This was problematic with Chrome's ANGLE backend; more information at: https://bugs.chromium.org/p/chromium/issues/detail?id=941671#c10 Fixes #3308 — committed to google/filament by prideout 4 years ago
- WebGL: RGB16F is not color renderable. This was problematic with Chrome's ANGLE backend; more information at: https://bugs.chromium.org/p/chromium/issues/detail?id=941671#c10 Fixes #3308 — committed to google/filament by prideout 4 years ago
- WebGL: RGB16F is not color renderable. This was problematic with Chrome's ANGLE backend; more information at: https://bugs.chromium.org/p/chromium/issues/detail?id=941671#c10 Fixes #3308 — committed to google/filament by prideout 4 years ago


Ah, right, apologies. Indeed, we did not merge the RGB16F fix (#3334) into our 1.9.10 release candidate, as it was not considered critical fix for an internal upgrade at Google. However the fix will definitely be included in our release next week. Thank you for being patient with us. š
Thanks @cx20, I have a tentative fix that Iām going to push momentarily. Would be great if you could test it out for us.