What have I done? Paddle is mapped to DX Shift
-
@Zapper ok I think I figured out the main point of confusion. good news: I don’t think it’s because you’re dumb
apparently when you have a button mapped to one of the dx-shift commands, you can’t simply remap it to something else… because when you press it, AL thinks you want to press a shifted button!
there isn’t any obvious UI feedback, when you try – so, if you’re new to this stuff, it would be reasonably unexpected… it just looks like “it’s not working, wtf”
to unwind this, you’ll need to first (a) clear the dx-shift mapping on your physical paddle button, then (b) reassign the “paddle-switch” command to your physical paddle button.
-
search/filter for commands with the word “shift”
-
double-click the one that says “SIM: DX Shift” … currently assigned to your button #4 (I think) which is the physical paddle
-
click the “Clear DX” button, and then “Save”
ok, now we should be able to do what I said earlier…
-
search filter for commands with word “paddle”
-
double-click the one that says “STICK: PADDLE SWITCH”
-
now tap your physical paddle switch
-
click “Save”
-
-
Oh Happy Day!
Thanks so much for your very patient help.
If I can risk stretching the friendship -
This line:
SimHotasShift -1 0 0XFFFFFFFF 0 0 0 1 “SIM: DX Shift”should have read
SimHotasShift -1 0 0X1E 0 0 0 1 “SIM: DX Shift”That Right?
-
@Zapper said in What have I done? Paddle is mapped to DX Shift:
This line:
SimHotasShift -1 0 0XFFFFFFFF 0 0 0 1 “SIM: DX Shift”
should have read
SimHotasShift -1 0 0X1E 0 0 0 1 “SIM: DX Shift”
That Right?those are keyboard-mapping lines, nothing to do with your Warthog
0xFFFFFFFF means “not bound to any key”
0x1E is the scan-code for the [A] keybut of course the beauty of Alt Launcher is you should never have to see or know about hexadecimal scan codes
-
Hi, Zapper, glad you got it fixed! Don’t feel bad. My first week in BMS I couldn’t get the jet to taxi because in those days in had to invert the brake axis’ to get them to unlock, and I didn’t know that.