Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.41f1
2022.3.39f1
6000.0.12f1
Issue ID
UUM-121962
Regression
No
Dpad Input Control Layout disappears when USE_INPUT_SYSTEM_POSE_CONTROL or USE_STICK_CONTROL_THUMBSTICKS symbol is defined
Reproduction steps:
1. Create a new project
2. Install Input System, OpenXR Plugin and XR Interaction Toolkit packages
3. Open Input Debug window (Window > Analysis > Input Debugger) and find Dpad Control Layout (Layouts > Controls > Dpad)
4. Enable OpenXR (Edit > Project Settings… > XR Plugin Management)
5. Press “Fix” button for “[OpenXR] [Optional] Switch to use InputSystem.XR.PoseControl instead of OpenXR.Input.PoseControl…” or “[OpenXR] [Optional] Switch to use StickControl thumbsticks instead of Vector2Control…”
6. Open Input Debug window (Window > Analysis > Input Debugger) and observe Control Layouts (Layouts > Controls)
Expected result: Nothing of note happens
Actual result: Dpad disappears from Control Layouts
Reproducible with: 1.7.0 (2021.3.41f1), 1.9.0 (2021.3.41f1, 2022.3.39f1, 6000.0.12f1)
Reproduced on: macOS Sonoma 14.5 (Intel)
Note: Removing “USE_INPUT_SYSTEM_POSE_CONTROL” and “USE_STICK_CONTROL_THUMBSTICKS” Scripting Define Symbols in Player settings makes the Dpad reappear but closing the Editor and reopening it again makes Dpad disappear and removing Scripting Define Symbols again does nothing
Comments (1)
-
JsommerOcto
Apr 03, 2025 15:36
Similar issue. Converted our Project to Unity 6. Did the 'Switch to Use StickControl Thumsticks' fix. But, made our flight controller feel way different. Now, we can't figure out how to revert back to legacy defaults.
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
- Build for iOS with UnityAds fails with linker failures when performing a CocoaPods build
- NavMeshManager.LoadData takes a long time and causes performance spikes when enabling a NavMeshSurface with already instantiated NavMeshLinks
- Shadows created by real-time Spotlights are rendered at a very low resolution on terrain when HDRPAsset Lit Shader Mode is set to Forward or Both
- “STP” in Project window > Advanced Upscalers by Priority menu list is shown as available to add when it is already added to the list
- Rename fails with an error “Canceling DisplayDialog” when renaming a Mipmap Limit Group in Project Settings > Quality after adding a new group
Resolution Note:
won't fix, not a prio