Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.3.5f1
Issue ID
815918
Regression
No
[Android] Calculating delta position (manually), gives different results from Touch.deltaPosition
Reproduction steps:
1) Open Unity Remote on a device
2) Open "case_815918-DeltaPositionBug.zip" project
3) Open "scene" and enter playmode
4) Swipe on screen using Unity Remote and check results in console output
5) Exit playmode and build game for Android device
6) Swipe on built project and check debug output in adb logcat
- Notice that user's calculated delta position in built project is very different than in case using Unity Remote
Note:
User's formula for delta position: touch.position - LastPosition // last position is updated in LateUpdate()
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