you can assign as many keys as you want 😀

Hi robertmo,

ok, so how do you assign SHIFT + UP ARROW in order to use just the coolie UP instead of SHIFT+UP ?

XenonS

same way as one key, just don't remove the old one, so it is actually easier 😉

Thanks robertmo. Will retry this out immediately, but i think this will only work when hitting SHIFT and using UP on the coolie.

Greets,
XenonS

Me again,

It works !!
I had to set all collie hat directions for the shift AND the right ones for the arrow keys

Thanks a lot 😎

XenonS

Mmm, I think this feature (mapping a two-key combination to a joystick button) isn't very obvious. I couldn't find it at first.

It would be nice to have an example of how to do it in the readme.txt included with dosbox.

I think it's not completely clear to the user that he/she has to add a bind to the same button TWICE, in two different keys (the ones that he/she wants to be pressed at the same time)

Also, the manual is quite misleading in the description of the emulated joysticks. It says that you can only use 3 axis with the FCS, but that's not completely true.

It's possible to use all 4 axis of your joystick by mapping the fourth axis to some keys.

I find it really strange that the keymapper hides some of the available axis of your real joystick depending on what kind of joystick is being emulated.

That's annoying, because you lose several axis of your real joystick and cannot map them to useful keys when the emulation is set to "2axis".

Why is that? Dosbox should take advantage of all the features of my real joystick and let me remap all my axis, regardless of which particular joystick is emulating internally.

Why is that?

To not screw up everything if a different type of joystick(s) is plugged in.
But feel free to post fully-tested working patches.

Aahm, sorry, I wasn't aware of that. I was under the impression that the mapper file had to be recreated from scratch whenever the real joystick changed.

The problem is more complex than I thought, then.

I was under the impression that the mapper file had to be recreated from scratch whenever the real joystick changed.

In the first place it was tried to design it so swapping joystick(s) or adding
a joystick to a previously keyboard only layout but with joysticktype!=none
was possible, but don't know if it fully works now. Resetting the mapper file
may be required/surely doesn't hurt.