Search Issue Tracker
Active
Under Consideration for 3.4.X
Votes
0
Found in [Package]
2.6.3
3.1.0-pre.1
3.3.0
3.4.0-pre.1
Issue ID
XRIT-233
Regression
No
Arrow button is poked in opposite direction when clicking on it
Reproduction steps:
1. Open the attached project “ReproProject“
2. Open the scene “HandsDemoScene“
3. Make sure VR headset is connected and is ready to use in Play Mode
4. Enter Play mode
5. Using controller or finger (if hand tracking is available), press on the arrow buttons in the middle of the view
6. Observe the result
Expected result: Arrow buttons are slightly pressed into the panel behind Arrow buttons
Actual result: Arrow buttons are moving into the controller/finger direction
Reproducible in: 2.6.3 (2021.3.48f1, 2022.3.57f1), 3.1.0-pre.1 (6000.0.37f1, 6000.1.0b5, 6000.2.0a2)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Reproducible with:
- Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, v72, OS: 1
- Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740 (user)
Note: Also reproducible in Player for Quest
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment