I've noticed what I think may be a bug or some weird behavior that is causing some downstream issues. In Chrome 66 with the latest version of KRPano, krpano.view.hlookat is either positive or negative and keeps increasing if you spin clockwise or decreasing if counterclockwise. In the Gear/Oculus browser in WebVR mode however, hlookat basically flips from positive to negative at 165 degrees/-195 degrees. This quick flipping between positive and negative values is creating a bit of a problem in the WebVR version.
I'm really sure if this is a gyro, webvr or just a browser issue so I'm not really sure the best way to solve it. Any idea what is going on/why the inconsistency?
EDIT: A little more investigation makes me believe it is gyro related. On my iphone, if I spin the view with my finger, hlookat keeps incrementing without flipping back and forth between positive and negative 180 degrees from the initial view like the desktop browser while if spin using the gyro, the lookat x flips between positive and negative. The reason the example above was 165 instead of 180 is the initial view has a -15 degree offset.
Nevertheless, this inconsistency is creating a problem since we processing the lookat data with a smooting algorithm to pass to a different device and this quick transition back and forth between positive and negative values and the inconsistency between navigation/input methods is making this a difficult to solve. It seems to me the viewer should return the same data regardless of the method used to spin the view no?