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
- USS code is not updated when a selector is deleted or is moved to a new USS file
- Custom elements not visible in UI Builder when defined in a namespace starting with "Unity"
- Decal Projectors of Prefabs appear less faded in Scene view
- Default Preset application and Reset() method execution order is different when adding a Component via the Inspector versus calling Reset via the Component context menu
- Scene view is not outputting HDR when the "Use HDR Display Output" option is enabled, DX12 is selected as the Graphics API, and URP/HDRP is in use
Add comment