Search Issue Tracker
Fixed in 5.0.1
Votes
2
Found in
4.5.1f3
Issue ID
617281
Regression
No
Inconsistency of Input.gyro.gravity values in Androind and WP8 platform
If device is horizontally placed on the surface, Android Input.gyro.gravity returns (0,0,-1) vector, while Windows Phone 8 returns (0,0,1).
If devices are held in vertically landscape-left orientation, values on Android are (0,-1,0) and (-1,0,0) if Input.compensateSensors is false.
WP8 returns (1,0,0) both with and without compensateSensors being true.
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
Add comment