https://bugs.winehq.org/show_bug.cgi?id=40658
--- Comment #31 from Rémi Bernon rbernon@codeweavers.com --- I'm definitely not opposed to make the axis mapping configurable somehow, to help with bogus devices and users, just that doing it in DInput like it was done before doesn't seem right anymore.
Wine now exposes any host joystick as an HID device internally, and DInput is only one of the many ways to access them. Applications may use HID APIs directly, and I know several middleware are doing it instead of DInput which is kind of considered as legacy.
So having a customizable mapping in winebus.sys instead, for when where we convert evdev axes to HID usages makes more sense, it's just not implemented yet.
Of course, that won't cover cases where Wine simply acts as a pass-through, like with hidraw devices, or where the mapping is already done elsewhere, like with SDL.