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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment