Noeri Huisman

> Meant Firefox desktop @dmarcos Firefox desktop has WebVR disabled by default since 98 ([link](https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features#webvr_api)). It can be enabled by setting `dom.vr.enabled` and one of `dom.vr.openvr/osvr.enabled` manually. Though, personally whenever...

@dmarcos Rebased. > Also cardboard support is still around albeit disabled by default. Heard of some people still using it One option for cardboard users could be to use the...

Let me know if you want me to split off a PR that focusses on removing the WebVR controller logic.

Thanks for the clear and concise glitch showing the issue @meduzo. I managed to find the root cause. The removal of the element happens while the scene is processing `ticks`,...

@dmarcos I don't really see any jank in the three example. Only occasionally when it hits the bottom, but that's probably due to the `setInterval` not taking exactly 5000ms. Would...

Came across this Codepen: https://codepen.io/joliss/pen/wWKGeV/ This seems to indicate that using the rAF timestamp results in more consistent frame pacing compared to `performance.now()`. Effect is even more pronounced on Chrome...

@dmarcos Rebased

Old issue, but in case someone comes across it while searching. The mentioned change in behaviour is due to a change made in Three.js at the time (https://github.com/mrdoob/three.js/pull/12787). Negative scales...

There is already logic in place to defer the initialization till the `document.readyState` is complete. I feel it would be cleaner to generalize this logic instead of adding additional flows....

The current limit on triangles is set very low to the point that it's effectively useless. I'd suggest removing rather than increasing the limit. Since A-Frame runs on a wide...