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 explicit caps would be nice?
Yes. A "null" reading could also indicate an intermittent loss of positional tracking, right? -Sven