[macOS] Hall-effect sticks with 0-65535 unsigned axis range: pitch/roll only respond one direction (game parses axes as signed 16-bit)

Cross-posting from a closed Gaijin tracker thread: Community Bug Reporting System (comments closed there, so posting here since that thread is no longer replyable).

Hardware: FlashFire Cobra V6 flight stick (HID name “USB Device V6”, VID:PID 11C0:5614, hall-effect, 9 axes / 29 buttons)
Platform: macOS 15.8.1, Apple M1, War Thunder official macOS client (launcher version).

Problem: Pitch and roll axes only respond in one direction; rudder and throttle work fine.

Measured root cause:

  • The stick reports X (usage 0x30) and Y (usage 0x31) with logical range 0-65535 (unsigned 16-bit, center 32768). All other axes use ranges of 2047 or less and work fine in-game.
  • The game appears to interpret raw axis values as signed 16-bit, so values above 32767 are read as large negative numbers and half of the stick travel is lost - exactly matching the analysis in the linked closed issue.
  • OS-side verification: browser Gamepad API shows full bidirectional -1.0…+1.0 sweeps on both axes; IOKit HID element dump confirms logical min=0, max=65535. The device itself outputs correctly.
  • In-game bindings save correctly (pitch/roll/rudder/throttle all present in machine.blk), device enumeration is correct (9 axes / 29 buttons). The failure is purely in axis value interpretation.
  • MODE button (2 mappings, green/red LED) does not change the reported axis range.
  • Forced Steam Input on macOS creates no virtual HID device for this title, so relaying via Steam is not possible; user-space virtual joystick creation on macOS requires an Apple-restricted entitlement (tested; such a tool is killed by the OS).

Request to Gaijin: please parse axis raw values using the device’s reported HID logical min/max instead of assuming signed 16-bit. Unsigned ranges are valid per the HID spec, and modern hall-effect sticks increasingly report more than 32767 steps on X/Y. Per the linked thread this also affects Windows (e.g. Thrustmaster Warthog / TWCS), so it is not Mac-only.

The device vendor (FlashFire) has been asked for a firmware fix; a game-side parse fix would unblock all affected devices on all platforms.