You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mrdoob/three.js#8666 seems to say it's a Chrome bug, and fixed in a more recent threejs release (which doesn't seem to be available on npm yet?)
/server/#key=zMjA:1 [.CommandBufferContext]RENDER WARNING: there is no texture bound to the unit 0
8/server/#key=zMjA:1 [.CommandBufferContext]RENDER WARNING: there is no texture bound to the unit 1
The text was updated successfully, but these errors were encountered:
The lens flares, in particular. But delaying load isn't making them go away.
Also, oddly, this delays the physics simulation, but doesn't seem to delay rendering or camera movement. You can (in server/god mode) move around almost immediately -- the physics just take a while to start until WebGL errors stop showing.
mrdoob/three.js#8666 seems to say it's a Chrome bug, and fixed in a more recent threejs release (which doesn't seem to be available on npm yet?)
The text was updated successfully, but these errors were encountered: