Search Issue Tracker
Won't Fix
Won't Fix in 2.0.X
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
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
Resolution Note (2.0.X):
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