Search Issue Tracker
Fixed
Fixed in 1.11.2, 7000.0.0
Votes
0
Found in [Package]
1.11.1
7000.0.0
Issue ID
ISXB-1101
Regression
No
Input Actions incorrectly adds 2048 to a Display Index when getting the value from a raw touch event
How to reproduce:
1. Open the “PointerInputTest.zip“ project
2. Build and run the project
3. Touch the screen and move around
4. Observe the text logs in the top-left corner
Expected results: “Updating screen coords…“ is logged and a green diamond follows the touch point
Actual results: “Touch event at (…) on display 2048 intersects no valid base cameras.“ is logged and a green diamond does not follow the touch point
Reproducible in: 1.7.0 (2021.3.44f1, 2022.3.49f1, 6000.0.22f1), 1.11.1 (2021.3.44f1, 2022.3.49f1, 6000.0.22f1)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Workaround: use the Modulo of 2048 operation on the display index
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors and warnings are thrown after installing Visual Effect Graph Learning Samples
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
- Empty gap next to Preview window in SpeedTree Shader Graph Nodes
- Override move options in Inspector are not disabled when only one Override is added in URP Volume
- “NONE”/“ALL” text in Adaptive Probe Volumes Option Override is too light when Editor theme is set to Light
Add comment