Hayden Greer

Thanks for replying @willeastcott! In the actual project we're using aframe-physics-system with the ammo.js driver. The vehicle updates in step and I tried hooking the camera into the afterStep call...

Hey @arpu! I have submitted an issue on the aframe-physics-system repo (https://github.com/donmccurdy/aframe-physics-system/issues/153#issue-642045495)

I solved or at least patched the issue by setting the fixedTimeStep to 0.005. The scene was still lagging and jittering on some devices, which seemed to be caused by...

I've never seen that before, thanks for sharing the knowledge!

Friendly +1 on this bug. Would be awesome to get this submodule + gitLFS implementation working correctly

Any update on when this bug might be fixed or investigated?

@overlordofmu thank you for the reply. That timeline is obviously way longer than I was expecting, which is disappointing, but I do greatly appreciate your honesty as it helps me...

@overlordofmu One thought I just had was that it may take 6 months for Netlify devs to get around to fixing the bug in the code but a temporary and...

Just to note, I commented out the `this.physicsWorld.setForceUpdateAllAabbs()` function in the startup function and everything seems to be working now. I didn't see any function `setForceUpdateAllAabbs()` in the ammo.js idl

Is the change to webGL 2 in three v118? On Mon, Aug 3, 2020 at 5:27 PM Jaume Sanchez wrote: > It´s not a bug really. Three.js now uses WebGL2...