DInput axis mapping explanation

[vsq]

I'm trying to understand Wine's DirectInput axis mapping feature. The documentation at http://wiki.winehq.org/UsefulRegistryKeys gives some details but seems to assume you already know how the feature works.

This maps axes of joystick "joystick name". The "axes mapping" is comma-separated list of "axis type"s - one for each joystick axis (hat-pov uses 2 axes).
"axis type" is one of: X, Y, Z, Rx, Ry, Rz, Slider1, Slider2, POV1, POV2, POV3, POV4.
To find the joystick name run 'WINEDEBUG=+dinput wine game.exe 2>&1 | grep joydev_enum_device'

This tells me I can make a registry key with the same name as my joystick device and a value that's a comma-separated list of "axes" and that somehow acts as a "mapping". But it gives me no idea how this mapping works, nor how to construct a mapping that will accomplish what I want.

I've tried experimenting while using joy.cpl for feedback, but I can't even construct a mapping that does anything other than break everything. It would help if I had a better understanding of how the mapping works!

[vsq]

Anyone? To reiterate, I'm looking for an explanation of the axis mapping that can be done via a registry key in HKEY_CURRENT_USER\Software\Wine\DirectInput.

[dimesio]

This thread may help you: viewtopic.php?t=14899.

[vsq]

This thread may help you: viewtopic.php?t=14899.

I've read that thread. Unfortunately it doesn't give me any more idea of how the mapping works than the wiki page I mentioned.

[vsq]

Is there another place I could ask? I already tried wine-users.

Would it be appropriate to ask on wine-devel? Hopefully there'd be developers there who could answer this.