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