Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.1.6
2.0.0-pre.3
Issue ID
AVPB-732
Regression
No
[VisionOS] Input state gets stuck when one hand is performing a Touch and another performs a Direct Pinch
How to reproduce:
1. Open the attached Project "2024-04-24 PolySpatialBugReplication - TestPinching.zip"
2. Build and Run the Scene "TestPinching" on a VisionOS device
3. In the Player, touch the green cube with both hands
4. Use one hand to Pinch
5. Observe the active touches information displayed above
6. If a touch does not get stuck, perform steps 3-5 again
Expected result: Both touches 1 and 2 are updated correctly
Actual result: One of the touches gets stuck in a Stationary state
Reproducible with: 1.1.6 (2022.3.39f1), 1.1.6, 2.0.0-pre.3 (2022.3.39f1, 6000.0.12f1)
Reproduced in: MR App Mode
Notes:
- As it gets stuck in a Stationary state, it might require multiple attempts to reproduce
- Ended phase does not get sent on the touch that is stuck
- Initializing a new touch causes the stuck touch to update
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
- Crash on TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
Resolution Note:
Test with all the latest PSL 2.0 fixes on input and this is no longer an issue.
I may look at backporting those fixes to 2022.3