Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.10f1
2023.3.0b7
Issue ID
UUM-64809
Regression
No
The "secondary" touchpoint reverts to the previous position when the "primary" touchpoint is released and re-engaged on WebGL applications
How to reproduce:
1. Open the “webgl Multitouch test.zip“ project
2. Open the “SampleScene”
3. Build the project for WebGL
4. In the Player enable the Debug mode (with the UI Toggle)
5. Press and hold a finger on the “red“ side
6. Press and hold another finger on the “green“ side
7. Let go of the first finger (“red” side)
8. While holding, drag the second finger some distance (“green“ side)
9. Press and hold a finger on the “red“ side again
10. Observe the Debug text of the Player
Expected results: The “secondary” touchpoint position (“green“ side) is independent of the “primary” (“red“ side) touchpoint
Actual results: The “secondary“ touchpoint position translates back to where it was (until it is updated) before the “primary“ touchpoint was released
Reproducible in: 2021.3.35f1, 2022.3.20f1, 2023.2.10f1, 2023.3.0b7
Reproduced on: Windows 11 Pro (23H2) (with touch-screen), Huawei Nova 5T (by the reporter)
Not reproduced on:
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00175, Samsung Galaxy Note9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 6.0, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00146, Htc 10 (HTC 10), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00372, Samsung SM-G991U (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Notes:
- On multi-touch testing websites there does not seem to be the “primary“ touchpoint dependence like there seems to be on Unity WebGL builds
- When successfully reproduced, the corresponding Debug line usually features a relatively large number (“… drag = <~100-2000>”), and on the very next line, the same negative number (to indicate, that the “secondary“ touch-point changed to the first position, and then went back to the current position)
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.