Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1126640
Regression
Yes
WMR legacy native implementation joystick/thumbstick mappings are messed up
Steps to reproduce:
- Open Unity editor 2019.1.0b3 or 2018.3.5f1
- Connect a WMR Immersive HMD to your PC
- Open the project (19.1 branch) https://github.cds.internal.unity3d.com/unity/xr.manualtests.input
- Open the XR Test menu from the menu bar Window->XR Tests
- Press the "Run" button on the XR Tests menu for the "Generic Buttons and Axes" scene.
Expected:
Button and Axis mappings match the current implementation of WMR. These should be
joystick click - buttons (18, 19)
touchpad touch - buttons (16, 17)
touchpad click - buttons(8, 9)
Observed:
- The joystick and touchpad button and axis mappings are incorrect.
joystick click - buttons (8, 9)
touchpad touch - buttons (18, 19)
touchpad click - buttons(16, 17)
They should match this spreadsheet: (https://docs.google.com/spreadsheets/d/15vYCvmRaYKGDmbW3USCxhhNHvcDm65kcD6eQFSFEswo/edit#gid=0).
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note:
This was a doc issue. The mappings for WMR joystick/thumbstick touch/pressed are changing in 19.2. The docs were incorrectly changed for 18.3 and 19.1