Search Issue Tracker
Fixed
Fixed in 1.11.2
Votes
0
Found in [Package]
1.11.1
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Add comment