Open takahirox opened 4 years ago
Currently the extension doesn't touch gamepad.axes and keeps it [0, 0]. But we should update them properly when touch event happens in AR mode.
gamepad.axes
[0, 0]
Google \<model-viewer> sees the values. This is one of the reasons why the extension doesn't work correctly with it.
And from #237
axes[0], axes[1] are implemented in #250. We should support axes[2], axes[3], too.
Currently the extension doesn't touch
gamepad.axes
and keeps it[0, 0]
. But we should update them properly when touch event happens in AR mode.Google \<model-viewer> sees the values. This is one of the reasons why the extension doesn't work correctly with it.
And from #237