Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-694
Regression
No
[Android][Windows] Pointer Input Action Binding gives wrong values when the screen is touched on Google Pixel 7 device or PC with touchscreen
Reproduction steps:
1. Open the attached project “InputProject”
2. Build and run the Project on Android or Windows Standalone
3. Tap few times anywhere on the device screen
4. Observe the pos1 values
Expected result: pos1 values are consistent with pos2 values
Actual result: pos1 and pos2 values are not equal
Reproducible with: 1.8.0, 1.8.2 (6000.0.5f1)
Not Reproducible with: 1.8.2 (2021.3.39f1, 2022.3.32f1)
Reproducible with these devices:
VLNQA00498 - Google Pixel 7 (Pixel 7), CPU: Google Tensor G2, GPU: Mali-G710, OS: 13
VLNQA00594 - Google Pixel 7 Pro (Pixel 7), OS: 13
Dell XPS 15 with touch screen display
Not reproducible with these devices:
VLNQA00378 - Google Pixel 5, OS: 13
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0
VLNQA00139 - Vivo Xplay6 (vivo Xplay6), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 7.1.1
Note: I think it's related to the fact that when touching the screen the input comes from two devices:
* On Google Pixel 7, the touch input comes simultaneously from Stylus and TouchScreen
* On PC with a touchscreen, the touch input comes from touch and mouse devices, when touching the screen.
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
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Resolution Note:
Closing this. To make this work, the Pointer action needs to be setup to Passthrough type to bypass "conflict resolution".
When on Windows w/ Touchscreen and using an InputAction of "Value" type, we receive both Mouse and Touch position events and decide which one to use based on the highest magnitude. The Passthrough type ignores this decision-making and provides all position events, which returns correct Touch values for this particular case.