Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1p2
Issue ID
920434
Regression
No
[iOS][Google VR] InputTracker.GetLocalRotationMagic in Window Mode gives incorrect rotation values
Reproduction Steps:
1. Open "Google VR Rotation Error"
2. Build for iOS
3. Hold the device in portrait orientation
4. Select the top button
5. Keep holding the device portrait and try to look around using the Magic Window mode.
Notice: The rotation is off, while looking around the rotation is 90° off. Looking horizontally doesn't move the camera horizontally but it moves vertically. Vertical movements are horizontal movements.
6. Enable fix rotation in the left top corner
Notice the rotation is fixed now (+90° in the z-axis)
Note: If device is held in horizontally(landscape) the fix has to be turned off, because the API is giving correct rotation values for Landscape.
Expected behaviour: InputTracker.GetLocalRotation gives correct rotation values on iOS in both Portrait and Landscape mode.
Actual Result: InputTracker.GetLocalRotation gives wrong rotation values on iOS in Portrait mode.
Reproduced on versions: Unity 2017.1.1p2, 2017.2.0f3, 2017.3.0b6, 2018.1.0a1
Reproduced on devices: iPhone 6s iOS 11.0
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
GoogleVR support is now owned by Google themselves. Please send any bugs you encounter to them.