http://bugs.winehq.org/show_bug.cgi?id=58743 Mike Mestnik <cheako+winehq@mikemestnik.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cheako+winehq@mikemestnik.n | |et --- Comment #2 from Mike Mestnik <cheako+winehq@mikemestnik.net> --- @Austin English please don't ask people to retest with newer versions unless you know there have been changes that are relevant. @bgoodwin I'm assuming this is a HID device. In that case it's important to know a few things. HID(either USB or BT) specifically makes no mention of what button and axis IDs mean, the IDs used "by each device" are essentially random from both wine's and the applications perspective! It's the application's, and not wine's, responsibility to take the vendor:product pair and turn that into a map of what the HID IDs are/mean. Thus there will never be a solution to this issue. Reading the HID specification closely reveals that device manufacturers are barred from having unused IDs, each device shale make use of IDs from 0 to `n` where `n` comes from id-max in the HID descriptor. With this constraint it's impossible for device manufacturers to standardize the IDs. For example an 8bit nes controller would have buttons A,B,select,start while another gamepad without select and start would need to use IDs 2 and 3 for something else. Thus you'll need to find out how to configure whatever game you are playing with the correct ID mapping. For SDL applications you can set `SDL_GAMECONTROLLERCONFIG` env var. For DirectInput and XInput there are control panel "views"... I say to just ignore these, I don't have proof but my assumption is that they don't match what the game uses/sees. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.