Closed noio closed 7 years ago
indeed, very much. I think that this might go away upgrading to later versions of Three.js, because I think I've seen the same warnings in other three.js demos, but I might be wrong and this might be entirely LCL's fault.
I now think it's due to not loading a texture when creating MeshBasicMaterial (in graphics-commands.coffee). See http://stackoverflow.com/questions/7919516/using-textures-in-three-js
this is no longer happening
I get a whole bunch of WebGL warnings every time I start LCL. Is there a way to either fix or mute these? They make debugging somewhat annoying. :anger: