THREE.VRController
THREE.VRController copied to clipboard
An unhandled exception may occur when expected buttons mismatch the actually reported ones
Just recently hit that issue: different browsers may report different number of buttons (and theoretically - axes) for the same controllers (even though the order of those, obviously, must be correct). If the number of expected buttons is greater than the number of buttons actually reported then VRController throws an exception (in line 187). For safety reasons I am adding if check for buttons and axes.