Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
WebGL error texture bound to texture unit 1 is not renderable
See original GitHub issueHi, guys. I faced this error in our React App:
[.WebGL-0x7f872a918c00]RENDER WARNING: texture bound to texture unit 1 is not renderable. It might be non-power-of-2 or have incompatible texture filtering (maybe)?
I’m using PluginContext like in examples in the repo. Here on stackoverflow proposed to “make a 1x1 texture at creation time” (similar error but not for molstar). I wanna try this workaround.
So my question is: how can I do that? Should I use applyPreset function or something else?
Maybe you have a different solution for my problem.
Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
texture bound to texture unit 0 is not renderable - Stack Overflow
To fix this, I put the calls to bind the texture and draw elements in the onload function: image.onLoad.listen((e) { gl.bindTexture(webGL.
Read more >'texture bound to texture unit 0 is not renderable. It maybe non ...
'texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering #6014.
Read more >Webgl couldnt load tilemap (texture bound to texture unit 0 is ...
hey guys this is the error msg i get on console: [.WebGL-0x18b5577b3700]RENDER WARNING: texture bound to texture unit 0 is not renderable.
Read more >[Chrome OS] WebGL error - RENDER WARNING: there is no ...
[Chrome OS] WebGL error - RENDER WARNING: there is no texture bound to the unit 0. As soon as our participant start using...
Read more >Using textures in WebGL - Web APIs | MDN
TEXTURE0 . We tell WebGL we want to affect unit 0. We then call bindTexture() which binds the texture to the TEXTURE_2D bind...
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
I wish I read the docs more closely 🙂 I opened an issue, and then found the answer in the docs. Turns out, the cleanup method I was after is
plugin.dispose. Now that I am calling it on unmount, the console is clear.Hi, I see that message on browserstack for your versions. However things seem to render fine. After all they are warnings not errors and should not break your app.