CH FS&PT Keymap
-
Hey everyone,
I’m new to BMS and trying to understand how this keymapping works.
Unfortunately, some of the documentation that comes with 4.33 refers to 4.32 files and conventions.
I’ve created my DX controllers properly and put them in mapped mode (although Falcon shows my DX Controller 1 starting at Button 33 and DX Controller 2 starting at Button 65). The only other peripheral I have installed is a Logitech G13 I’m hoping to use as an IPC/DED display, and it’s not being used as a DirectX device.
I’m trying to use LO and AOO to create a CH FS&PT key file but the import feature doesn’t appear to be working as the ReadMe says it should, and any attempt to load one I create ends up showing my Stick buttons as ProThrottle commands.
It appears as if something is acting as DX1 Buttons 1-32, and it’s not my Stick, and it’s bumping all of my key commands to the right.
How do I fix this?
-
I’m not sure what LO and AOO is, sorry, but i still might be able to help.
Once you’ve bound commands to DX buttons in the UI, you won’t NEED a map in CHCM. Personally, i used CHCM to make sure my POV hat was recognized as DX buttons, set a couple of buttons on the back of the throttle to map commands used outside of falcon (teamspeak transmit, centre track IR and screen recording software) and I use the CMSTART.EXE utility to set the controllers into mapped mode when windows boots. I rarely have to open CHCM. Everything else is done through the UI.
I don’t think it matters how your controllers are numbered if you’re going to manually bind the commands, which i would recommend. The CH layout is very similar to the F-16 HOTAS so you can map it close to real in little time. Setting up a “pinky shifted layer” takes a little more time and some editing with notepad, but you can tackle that once you’ve got the basics mapped.
With respect to 4.32 and 4.33 conventions – don’t sweat it. There are some new callbacks in the stock 4.33 keyfiles, but i don’t believe anything has changed with regards to how you set up your gear. There’s a great article in the docs folder that you should read if you haven’t already at C:\Falcon BMS 4.33\Docs\Key Files & Input\Joystick Setup Guides\CH Fighterstick & Pro Throttle
-
Thanks for the reply, Harlequin.
LO is LibreOffice and AOO is Apache OpenOffice.
I did the same thing as far as ensuring my throttle POV hat was being recognized as DX buttons and CHCM was being run in Mapped mode prior to starting BMS, but the documentation that shipped with 4.33 said I should use the Key File spreadsheet rather than mapping them directly from the BMS UI (I wonder if this has to do with DX Shifting functions?).
I temporarily fixed my issues by telling the Key File Generator spreadsheet that my FS was Device 2 and my PT was Device 3, which ended up shifting all the binds appropriately for use in the sim.
Most of my time spent after that was trying to figure out the in-game Idle Detent for the ramp start. I didn’t know you had to click the paddle switch with the mouse when pulling the throttle back to Idle. Is there some reason pressing the button on the joystick doesn’t work?
-
Most of my time spent after that was trying to figure out the in-game Idle Detent for the ramp start. I didn’t know you had to click the paddle switch with the mouse when pulling the throttle back to Idle. Is there some reason pressing the button on the joystick doesn’t work?
Left pinky switch on the PT mimics position of idle cutoff (paddle switch) lever on real throttle. In CHCM, set that switch to Dx mode (Device 3, button X), then map it to Idle Detent in BMS Setup/Controllers. Voila, no more mouse click of idle cutoff lever needed.
f1