Challenges with Fighter Stick, ProThrottle, and Pro-Pedal in Falcon BMS
So where do I start…
I’ve been using my HOTAS and rudder setup for over a year in P3D and DCS pretty successfully. To get things to work in DCS, I have a profile in Control Manager and use mapped mode. I then set up my axis in DCS. Each controller shows up as CH Device 1, CH Device 2, etc… In P3D, I use control manager to assign button presses, but use direct mode and configure axis through FSUIPC.
I just reinstalled BMS after a long hiatus and for the first time since having a HOTAS, and I’m having a hard time getting the axis to work. I’ve tried two things, both with issues:
1. Mapped mode through control manager - seems to work OK, except that I only have 2 CH controllers showing up in BMS 4.33. The third device (pro pedals) doesn’t ever show up, even thought it’s there and functioning in CH Control Manager. I have no idea why. Any thoughts?
2. Without Control Manager - If I do it this way, all three devices are selectable in BMS by name (CH Fighter Stick, CH Pro Throttle, and CH Pro Pedals). I can select one controller at a time and assign it to the desired axis through the BMS controller set up. But then when I select another controller to configure the other axis, it resets all axis to whatever controller I’ve selected. So it seems like there’s an issue with saving my axis settings… Any thoughts?
FWIW - this is what my device manager looks like. I’ve go all three devices plugged into a powered USB hub and going into a USB port on my laptop. I have have plugged the USB hub into two different USB ports, and I’m wondering if that’s why the devices show up by name twice. I’m not sure if it’s always appeared this way in device manager, or if it’s just since I started mucking around with BMS.
Badger last edited by
With regards to scenario 2
Select your stick in the main drop down only.
Then you select and set the others from controllers>advanced settings.
Hope that makes sense. Going from memory.
Thanks. I’ll try that later.
JetwasH last edited by
what Badger said works great for me with same setup…
-Vandal- last edited by
A couple of the guys over at the UOAF suggested to me that after you get your controllers mapped out how you like them to make the following files “Read Only”:
I think those are all in your user/config directory. Falcon has this thing about trying to make itself flyable if you change your hardware. So if you start Falcon without your joystick plugged in or you plug in another device, or you have a CH mapping profile loaded usually but you forget to do it and start Falcon just one time, the game will “lose” your configuration. Making the files I mentioned above, for me, has stopped Falcon from overwriting my configuration.
Thanks guys. The above recommended order of setting up axis worked for option 2. About 45 minutes with the keystrokes generator and I have my profiles all set.
Good point about making the files read-only. I’ll do that as well.
Badger last edited by
Good to hear.