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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment