[PC][INPUT][REPORT] Joystick/HOTAS detection/binding issues - 56 links

Community-wide report with a 56-link evidence pack. Non-detection, drift, duplicate defaults. Minimal repro and a clear 2-step request.

TL;DR

• Symptoms:
  • Joysticks/HOTAS not detected or only partially bind
  • Camera/axis drift or lock when a stick is connected
  • Duplicate, non-removable default actions
  • Impact: Blocks aircraft/heli gameplay for a sizeable part of the PC community.
• Ask (priority): (1) Fix PC joystick detection/binding and allow full unbind of defaults. (2) Ship native HOTAS support next (axes, curves/deadzones, per-vehicle profiles).
• Evidence: Attached evidence pack - 56 links - filename: BF6_Joystick-HOTAS_Evidence_2025-10-26.txt (EA Forums 35, Steam 4, Reddit 17) with one-line contexts and up-to-date stats (≈1.2k comments, 12.9k upvotes, ≈12k EA views, as of Oct 26, 2025).

Impact & scope

PC pilots who use flight sticks/HOTAS/pedals can’t reliably fly; workarounds (Steam Input/gamepad emulation) reduce axis count and fidelity (Steam Input emulation uses XInput fixed layout with fewer axes/buttons). This is a critical launch-window issue for the flight sandbox. Community corpus: 56 threads; ≈12k EA views, 12.9k upvotes, ≈1.2k comments. Many players avoid community workarounds (platform-level input mappers) due to a perceived anti-cheat risk; an official clarification would reduce anxiety and keep pilots in the game.

Minimal repro

1. Connect a common PC joystick/HOTAS.
2. Confirm it works in Windows Game Controllers.
3. Open BF6 → Settings → Controller → Joystick and try to bind pitch/roll/yaw/throttle/buttons. Result: inputs don’t register or register partially; some players also get camera/axis drift.

Observed vs expected

Observed

• No input registration in binds/gameplay despite the device being recognized and calibrated in Windows.
• Axis drift or camera lock (e.g., stuck looking up/down) when a stick/HOTAS is connected (even with no mappings).
• Default controller actions remain active alongside custom mappings (duplicate actions that can’t be fully unbound).
• Split-USB HOTAS/pedals: game sees only one module (usually the stick); throttle/pedals invisible to the binding menu.
• Settings/UI shows a console-controller profile on PC, confusing the active input context.
• High-axis sticks are often misclassified as a gamepad; the Joystick page becomes inaccessible until some axes are disabled (pattern reported by multiple VKB users).
• No option to fully disable controllers on PC → forced mode switching and unintended inputs when HOTAS is connected.

Expected

• Native detection of common PC flight sticks and HOTAS devices.
• Clean, per-device binding with full unbind capability.
• No spurious input from inactive devices; sensible defaults to prevent drift.
• Clear UI that reflects the active device; joystick/HOTAS options are discoverable and functional.
• An explicit “Disable controllers on PC” toggle and per-device ignore.

What we’re asking for

• Now (hotfix): restore reliable joystick detection/binding on PC and allow full unbind (ability to clear any default binding). Suppress analog noise to prevent drift. Please also acknowledge the issue publicly so affected players know it’s being tracked.
• Additionally, please clarify that using common input mappers for compatibility is considered safe and won’t be flagged by anti-cheat, and expose a temporary per-device Ignore toggle in Controls so players can silence unwanted devices.
• Next: deliver native HOTAS support: full axis mapping (pitch/roll/yaw/throttle), invert, curves/deadzones, per-vehicle profiles/presets, plus import/export.

Community action - please reply using this template

Device / Platform build (EA App or Steam) / OS version / What happens / Any workaround

Example: Logitech X52 / Steam / Win11 23H2 / Joystick tab shows no input; Steam Input works but lacks axes.