When wasd-controls used together with orbit camera in version 0.8.2 of A-Frame it works as expected (within reason at least).
Starting with A-Frame 0.9.2 WASD stopped doing what it is supposed to and instead rotates camera albeit slowly. Starting with A-Frame 1.4.0 the whole component breaks and logs following:
aframe-orbit-controls.min.js:1
Uncaught TypeError: quat.clone(...).inverse is not a function
at aframe-orbit-controls.min.js:1:2563
at new THREE.OrbitControls (aframe-orbit-controls.min.js:1:3920)
at n.play (aframe-orbit-controls.min.js:1:17154)
at n.play (aframe.min.js:2:417129)
at d.play (aframe.min.js:2:400955)
at v.play (aframe.min.js:2:401016)
at v.<anonymous> (aframe.min.js:2:431426)
at v.emit (aframe.min.js:2:408454)
at aframe.min.js:2:406943
The expected would be if wasd would move both camera and target respecting the direction camera is facing (with 0.8.2 it does not do that as well).
When wasd-controls used together with orbit camera in version 0.8.2 of A-Frame it works as expected (within reason at least).
Starting with A-Frame 0.9.2 WASD stopped doing what it is supposed to and instead rotates camera albeit slowly. Starting with A-Frame 1.4.0 the whole component breaks and logs following:
The expected would be if wasd would move both camera and target respecting the direction camera is facing (with 0.8.2 it does not do that as well).