Axes from only one device responding in the sim at a time

[EyebrowZing]

I’ve been slowly taming the terrifying control assignment beast while trying to get into the sky, and I’ve run across an issue that all the tips and tricks I’ve found on the web haven’t helped me solve yet. Falcon is only recognizing axis input from one device at a time in the simulation, and it depends on the last controller selected in the dropdown menu in the controller settings screen. Each device axis (stick, throttle, pedals) work perfectly in sim independent from each other, just as long as it was the last device selected in the menu. All DX buttons on all devices work at all times regardless of whether or not the axes are responding in game.

Now before you jump to conclusions, let me tell you everything I have done.

Win7 - 64bit

Devices: Warthog HOTAS - stick and throttle. TARGET is not installed. Fanatec Clubsport pedals - Virtual rudder enabled.
Warthog is connected to a powered UBS hub, pedals are connected directly to the motherboard.

Keyfile: Edited BMS - Full.key - All DX assignments were made in Notepad++ and work flawlessly, including shift state.

I got around the controls page screwing with my axes binds by editing DeviceDefaults.txt to include the following:

# Joystick - HOTAS Warthog
GUID = {0402044F-0000-0000-0000-504944564944}
AXIS_PITCH = Y
AXIS_ROLL = X

# Throttle - HOTAS Warthog
GUID = {0404044F-0000-0000-0000-504944564944}
AXIS_THROTTLE = RZ
AXIS_THROTTLE2 = Z
AXIS_ANT_ELEV = SLIDER0
AXIS_CURSOR_X = X
AXIS_CURSOR_Y = Y

# Clubsport Pedals
GUID = {18390EB7-0000-0000-0000-504944564944}
AXIS_BRAKE_LEFT = RX
AXIS_BRAKE_RIGHT = RZ

I haven’t had an issue with axes resetting since, however, all other advanced control options still reset (roll linked NWS, large deadzone settings…).

After figuring out all my keybinding and getting the axes to stay put on each device, I completely deleted and reinstalled BMS 4.33.

AFTER REINSTALLING

Edited DeviceDefaults.txt to contain only my three controller settings that I had worked out before.

Edited in my changes to BMS - Full.key.

Started the game and immediately started the first training TE from the taxiway.
All DX buttons worked properly, but only joystick axes were responding to inputs, nothing from the throttle or pedals.

Exit game. Set joystick.cal and axismapping.dat to read only.

Start game again and look at the controllers in the setup page, confirmed all axes were mapped properly and moved with input.
Duplicated original tests and confirmed that the last controller selected in the dropdown menu is still the only controller that the sim responds to axis commands from.

I’m out of ideas at this point. Maybe it’s time to go learn the MIG21 in DCS now.

Thoughts?

[Blu3wolf]

Yeah, theres a reason for that. Its because the dropdown menu is for selecting which joystick you want the sim to use as a joystick. In other words, its not a bug, its a feature.

If you want to use multiple controllers, how about you set them correctly in the advanced controllers window? Setup->Controllers->Advanced.

If you thought Falcon’s controller interface was complex, I dont know how much luck you will have with DCS though… Id recommend giving BMS another shot tbh.

[Frederf]

I think that drop down should say “Select Your Primary Controller.” You set the device that has pitch-bank on it and never change it again. If you have other devices you set them in advanced.