Oculus touch controller

[daoshengmu]

In order to support all the current functions in FxR, we need to follow MozillaReality/FirefoxReality-android-third-party#2 to upgrade SDK to 1.19.

In this implementation, I notice the fov from the projection matrix of predictedTracking.eye is [fovX: 95, foxY: 99], But if we use VRAPI_SYS_PROP_SUGGESTED_EYE_FOV_DEGREES_X to get fov, they will be 104 and 106 degrees. So, we have to make it consistent with camera.projectionMatrix and the main eye buffer layer.

Besides, the controllerTransform is wrong when doing 6 DOF controller orientation. It should rotate transform by the elbow instead of by the origin. This new device has the same button layout as Oculus Rift Touch but different looking. So, we will keep working on it at following bugs to let it support multiple controllers and has the same button and axis mapping for WebVR content as Oculus Rift.

[bluemarvin]

Does the 6DoF head tracking work with this patch? It would seem the 6DoF controllers are not if you are applying an elbow model. Also you should be able to use two controllers. If there is an issue we should get that sorted out as well.

[daoshengmu]

@bluemarvin the 6DoF head tracking is supported from my patch. Because we use m.predictedTracking.HeadPose.Pose to get the headset position that is 6Dof data. Both of 6Dof headset and controllers are workable base on this.

In terms of two controllers, I already have a WIP patch in local, it has been near to be done. I will send you a PR shortly.

[bluemarvin]

@daoshengmu Please wait for @MortimerGoro to review before landing. He wrote the original implementation so I would like his feedback first. Thanks.

[daoshengmu]

Update using deviceType to check the controller type in DeviceDelegateOculusVR::SetControllerDelegate() because controllerCapabilities is not yet ready until calling UpdateControllerID().