Skip to content

PS4 DualShock 4 Gamepad Setup in Flair — flair7.ini, HID Detection, Classic vs Flair 7

Summary

The PS4 DualShock 4 controller works with Flair for live robot control, but setup requires care. Flair detects controllers via Windows HID (Human Interface Device) — do not install the official Sony or DS4Windows driver as third-party drivers can conflict with or prevent HID detection. In Flair 7, the joystick/gamepad device must be declared in flair7.ini under the *Controller parameter. In Flair Classic, setup is done through the Axis Setup dialog. The DualShock 4 is functional but the Logitech F310 is the community's most recommended controller due to its reliable HID mode and layout. Live control is available via the standard Controller panel in Flair (not through Mimic). Keep the controller wired — never use wireless/Bluetooth for robot control.

Symptoms

  • Flair does not detect the PS4 controller despite it being connected.
  • Controller is detected in Windows but not in Flair.
  • Robot does not respond to gamepad input despite correct setup.
  • Controller works in Flair Classic but not in Flair 7 (or vice versa).
  • PS4 controller detected but button/axis mapping is wrong.
  • After installing DS4Windows or official Sony drivers, controller stops working in Flair.

Community Guidance

[RESOLVED] Do Not Install Third-Party Controller Drivers

Community — multiple dates

Flair reads gamepad input via the standard Windows HID interface. Third-party drivers (DS4Windows, official Sony PS4 driver) intercept the HID path and present the controller to Windows as a different device type — which Flair may not recognise or may incorrectly map.

Correct setup: 1. Connect the DualShock 4 via USB (not Bluetooth). 2. Do NOT install DS4Windows, InputMapper, or the official Sony drivers. 3. Allow Windows to recognise it as a standard HID-compliant game controller. 4. Verify in Windows → Control Panel → Game Controllers that it appears as a generic gamepad.

Community consensus: do not install official controller drivers — use Windows native HID detection only.

confidence_score: 0.90

[RESOLVED] Declaring the Controller in flair7.ini (Flair 7 Only)

Community — Flair 7 setup

In Flair 7 Classic, the gamepad controller must be declared in flair7.ini using the *Controller parameter. The syntax specifies the controller type and the device index (usually 0 for the first connected device):

*Controller: JoyStick 0

Without this line, Flair 7 will not poll the gamepad even if Windows detects it. In Flair 6/Classic, controller setup is configured through the Axis Setup → Controller tab in the Flair interface.

confidence_score: 0.88

[RESOLVED] Axis Mapping and Button Assignment

Community

Flair assigns gamepad axes and buttons through the Controller Axis Setup dialog:

  • Open Flair → go to the Controller panel
  • For each robot axis you want to control, assign a gamepad axis (X, Y, Rx, Ry, Z, etc.)
  • Set appropriate scaling (sensitivity) for each axis
  • Set deadband to prevent drift (see Gamepad Drift / Uncommanded Motion)
  • The PS4 DualShock 4 has two analog sticks (X/Y and Rx/Ry) plus L2/R2 triggers (Z axis) — all usable for robot axes

confidence_score: 0.85

[INFORMATIONAL] Flair 7 Live Control Interface Improvements

Community — Flair 7

The Flair 7 interface provides improved live control features compared to Classic, including better visual feedback for controller input and more flexible axis assignment. If working primarily with live control and gamepad input, Flair 7 is the preferred environment. That said, many experienced operators continue using Classic for its familiar workflow.

confidence_score: 0.82

Official Documentation

MRMC Forum — Flair 7 Hardware Requirements