Stuck Axes, Losing Bindings

[Zerbob]

So I’m in the process of setting up my controls for Falcon 4 BMS but have encountered some problems. To start, my set is as follows:

• CH Combatstick
• CH Pro Throttle
• Saitek Pro Flight Rudder Pedals
• Home-built IR head tracker with PS3 Eye and Facetracknoir.

Now I’ve got the head tracking just fine. However one issue I’ve run into is that the game keeps losing my axis binds. Not only that, but some of them seem stuck and won’t change. Namely the Pitch and Yaw Deadzone axes are stuck bound to my Combatstick’s X and Y axes. Has anyone encountered this issue before, and if so do they have a solution?

Many thanks,
Zerbob

[Frederf]

You probably are starting BMS with a different selection and and ID order of game controllers. If you configure BMS, quit, and then start again with a different array of controllers yes the arrangement will be compromised. This includes missing controllers from the last time and extra ones. I think it is possible to reorder the IDs which will also have a similar effect. The head tracker is not a factor.

Here is a small software utility ( http://airgroup51.net/forum/index.php?topic=2435.0 ) which will display, save, and load DirectX controller ID arrangements. You will find that if you start BMS with the same ID arrangement used in the previous setup, axes will never be lost. Discover what behavior of changing controllers is causing a different ID arrangements.

Pitch and Bank are required to be the Y and X axes of the primary controller. The primary controller is the one selected in the drop down menu in setup (not the advanced menu). Whichever controller is selected as primary must be those two axes. It is normal and correct that there is no option despite the drop down showing other controllers. The only reason it is present at all is to give the user the opportunity to set the deadzone/saturation options which is why it has that name.

[Cali]

When I had my CH set up, the same thing happen to me. I would lose all my settings also and it happened about 4-5 times before I figured what I was doing. I had to start CH manager first and then BMS, that fixed the lost axis bindings for me. My start up procedure was

1. start CH manager
2. start trackir
3. start bms

I still use that start up even when I had my cougar and now warthog.

[Icarus]

@Cali:

When I had my CH set up, the same thing happen to me. I would lose all my settings also and it happened about 4-5 times before I figured what I was doing. I had to start CH manager first and then BMS, that fixed the lost axis bindings for me. My start up procedure was

1. start CH manager
2. start trackir
3. start bms

I still use that start up even when I had my cougar and now warthog.

Correct.
The only way around the dance is to have CH Control manager start with Windows and with the latest profile. BMS rewrites the callsign.pop when it sees a different controller setup. Perhaps also making callsign.pop read only might help.

[Cali]

@Icarus:

Correct.
The only way around the dance is to have CH Control manager start with Windows and with the latest profile. BMS rewrites the callsign.pop when it sees a different controller setup. Perhaps also making callsign.pop read only might help.

I didn’t find out that until after months later, but I didn’t mind doing it my way. It was kind of a post start up procedure.