WebGL warning: drawElements in Firefox
See original GitHub issueAlthough everything appears to work fine, i’m getting this error in Firefox when rendering sprites:
Error: WebGL warning: drawElements: This operation requires zeroing texture data. This is slow.
Is there a more optimal solution?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:13 (4 by maintainers)
Top Results From Across the Web
1420122 - WebGL warning: drawElements: Active texture 0 for ...
I'm facing the same problem (https://github.com/aframevr/aframe/) with a-frame on Firefox 60.0.1 (64-bit). The warning I get is: WebGL warning: drawArrays: ...
Read more >WebGL warning: drawElements in Firefox · Issue #3897 - GitHub
Error: WebGL warning: drawElements: This operation requires zeroing texture data. This is slow. All reactions.
Read more >ARRAY_BUFFER lost after VAO binded to null in WebGL
drawElements () here gl. ... WebGL warning: bufferData: Buffer for `target` is null. I checked. ... I tested on Firefox 90.0.2 for Windows....
Read more >Workshop not completely loading - Mecabricks.com
Firefox after Cleared Cache= not at all, black screen, workshop don't works at all. ... Error: WebGL warning: drawElements: Index buffer too small....
Read more >Can I mute the warning about vertex attrib 0 being disabled?
When drawing with gl.disableVertexAttribArray(0) , Firefox (just like other browsers, they say) issues this warning: WebGL warning: drawElementsInstanced: ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@GoodBoyDigital could you tell me how to fix it? I want to fix it in my fork-v4 . thanks
closing as this has been fixed in v5 👍