Hey guys, do you any trouble using multiple controllers?
I'm on the Combat Demo, and I can't get it to recognize my rudders in the options screen.
I suspect it's because it can't see more than 3 controllers at the time, as this is hinted at, in a couple of threads on the official forum.

However, I was wondering if this is specific for the Combat Demo, or if it's also a problem in the full game?

Oh, and fyi I have the Warthog, TrackIr, separate G25, pedals and shifter, and a set of simpeds on a Bodnar board plugged in, through various hubs and extensions. It would be a bit of a hassle, having to unplug all that to play..

I have no problem in the actual game as this issue was fixed, using the full CH pro setup (rudder using yaw). I see 3 +, still *should* have been fixed from what I read.

I use *Way* more than three devices and it now works perfectly. NOW is the keyword. It took a coupla patches to get it right.

But now development hit gamma we shouldn't see any more of those blunders.

Roger, it's probably just a demo thing then.
Makes sense, as it does stil say Combat Training Demo 1.00 on the startup screen, even though the launcher updated when I fired it up today.
Oh well, back to standby for the 16. then, no reason to fiddle too much with the control setup until then.

It'll be your Bodnar board and the way its axes are setup. If the pedals don't use a regular X and Y axis Elite will not recognise them. This has been discussed at length on the Frontier forums but as far as I'm aware it's not been resolved.

I had exactly the same issue with my gameport CH pedals which I'd converted to USB with a Bodnar BU0836A. I originally had the pedal axis on z rotation and the toe brakes on sliders, which Elite wouldn't recognise. Had to open them up and change the connections so the toe brakes used the standard X and Y axes and then they worked ok. Unfortunately this buggered the toe brakes in DCS, but I'm not doing much flying at the moment.

It's just occurred to me that you should be able connect any old pots to the X and Y axis so that they're recognised but not used. It may even be possible to fool Windows into recognising them by putting jumpers across the connections. The other alternative would be axis remapping software (such as vJoy and UJR) but personally I hate having to mess about with that stuff.

Running x52, Saitek pro rudders, g27 with pedals and shifter, tracker and it works fine.


Though someone posted a link to a USB hub with power switches, I think that would be handy, instead of having the g27 constantly powered on

Good info there Brun, I'll have a look at the axes later on!
I wonder if simply disconnecting the toe brakes and just leave Z rotation, would do the trick..?

Don't think it will. Here's a shot I found of the Saitek rudder properties...



The toe are brakes on the X and Y axis, which means they're recognised ok. From what I understand any device which doesn't report those to Windows (obviously not limited to rudders) won't.