Avaer Kazmer
Avaer Kazmer
This has been expected behavior for quite a few people.
No idea why this is, something to do with WebSockets.
Currently on r86. Changelog: https://github.com/mrdoob/three.js/releases/tag/r87 There's some WebVR stuff in there, but this is mostly just gonna be trying 'n testing. We use a vendorized fork at `three-zeo` so there...
Should have a load-time warning here, as we do when some plugin is hung. We've seen this a couple of times, and it would be nice to know GPU support/blacklisting...
Would work really well when you drag and drop a model to place it into the world.
Current loader doesn't support it, but it's a very common model format we should support.
Options menu should not be required to hear other people.
Should help with cases of unreliable cross-continent connections.
Right now the plugins are very ad-hoc in assets serving via manual express. This could easily be rolled into a first-class API on both the front and back end.