Re: [webvr] [gamepad] Missing VRPose for tracked controllers

Apologies if this comes across twice - the mailing list rejected my first attempt :-) Do we need to know if a given Gamepad is orientation only versus position+orientation? I'm seeing a lot of devices that only know their orientation and we could detect this by a 0,0,0 position, but having a flag

Re: [webvr] [gamepad] Missing VRPose for tracked controllers

Am 24.05.16 um 20:50 schrieb Brandon Jones: > Position/Orientation/Acceleration can always be reported as NULL, so > that's what I would expect from controllers that don't support a > particular pose value. That's a bit of a pain to use for feature > detection purposes, though, so maybe a more

Re: [webvr] [gamepad] Missing VRPose for tracked controllers

On Tue, May 24, 2016 at 8:50 PM, Brandon Jones wrote: > > but Yaw probably just initializes to whatever position the user started > with. > Applications for these kinds of controllers usually have some "reset forward" thing. Sometimes the settings of the device do (as is the

Re: [webvr] [gamepad] Missing VRPose for tracked controllers

Position/Orientation/Acceleration can always be reported as NULL, so that's what I would expect from controllers that don't support a particular pose value. That's a bit of a pain to use for feature detection purposes, though, so maybe a more explicit caps would be nice? As for determining what

Re: [webvr] Re: [gamepad] Missing VRPose for tracked controllers

Brandon Jones (Google) has made some experimental WebVR Chromium builds that include support for the HTC Vive VR motion controls. We would like to propose this as a standard and update to the GamePad API. Brandon has started a thread on w3.org that gives some background:

Re: [gamepad] Missing VRPose for tracked controllers

Hello, Am 24.05.2016 um 09:38 schrieb Florian Bösch: > You should discuss this on the WebVR ML as well, it's the main > communication channel for that, and since it has impact on their > spec it should be coordinated. I looked at the archive and saw that Brandon Jones already made a good

Re: [webvr] Re: [gamepad] Missing VRPose for tracked controllers

You should discuss this on the WebVR ML as well, it's the main communication channel for that, and since it has impact on their spec it should be coordinated. On Tue, May 24, 2016 at 9:22 AM, Sven Neuhaus wrote: > Hello Florian, > > Thanks for pointing out the WebVR spec draft.

[webvr] Re: [gamepad] Missing VRPose for tracked controllers

Hello Florian, Thanks for pointing out the WebVR spec draft. The WebVR draft dated April 1st contains a Gamepad interface expansion (§2.11), however it only extends it by a DisplayId. It should also add a VRPose for tracked controllers. I think adding a VRPose could have benefits for non-VR

Re: [gamepad] Missing VRPose for tracked controllers

The WebVR API models HMD pose and will model the gesture controllers. https://mozvr.com/webvr-spec/ On Tue, May 17, 2016 at 9:41 AM, Sven Neuhaus wrote: > Hello, > > I read the gamepad API description at > https://developer.mozilla.org/en-US/docs/Web/API/Gamepad > > I think the

[gamepad] Missing VRPose for tracked controllers

Hello, I read the gamepad API description at https://developer.mozilla.org/en-US/docs/Web/API/Gamepad I think the gamepad API should support a VRpose for gamepad controllers like the ones included with the HTC Vive and the upcoming Oculus Touch controllers. I suggest that you add a getPose()