[FrenchToast]

Hello, hopefully I'm posting this in the right forum, I'm always a bit lost in a new place.     Also sorry if this has already been asked, the Forum's Search function doesn't seem to like me...

If I understand correctly FS2 Open only recognizes one controller.  I am using CH Products gear and indeed my CH Fighterstick gets recognized without any problem.

However, since FS2 offers several axis I want to use my CH Throttle and CH Pedals also. Normally this is not a problem because the latest version of the CH programming software can "combine" several physical controllers into a single virtual controller so as to fool old games : they see only one controller with a rather high number of axis.    The virtual controller will appear as "CH Control Manager Device 1" in Windows' Game Controllers applet.

Somehow this doesn't work in FS2, however. The Launcher sees the virtual device ok (I'm assuming it sees anything Windows recognizes as a controller anyway), but from within the game itself (the option screen) the device is not recognized. The game doesn't react when I move an axis to assign it at the Option screen. I even created a new map that reports only 4 axis and 4 buttons to Windows, thinking that maybe FS2 doesn't like controllers with too many buttons and/or axis, but no luck.

Technically, the virtual device should be undistinguishable from a physical controller for Windows and for games (and indeed I used that trick in other games without problems), so I'm a bit at a lost.

Any idea?  Or maybe I'm missing something obvious, it wouldn't be the first time.   

FrenchToast

[Pnakotus]

FS2 certainly uses at least four axes: I play with a PS2 controller, and all four analog axes work fine for me.  Perhaps the problem is in your virtual device implementation?

[StratComm]

Silly question, but you have your controller selected in the launcher, right?

[FrenchToast]

Yes, the controller is selected in the launcher.   


Also, Pnakotus you are most certainly right, if I use only the joystick in direct mode (i.e. _not_ combined with the throttle or other controllers), then I can assign axes to it without problem. It's only when I use the "mapped" mode (i.e. the virtual joystick) that FS2 doesn't see it.

I did ask the same question on CH's support board, I think the problem is definitely with the virtual stuff and not with FS2.


FT

[Nuke]

did you try one of the force controller options? force it to whatever number corelates to the index of the virtual controler. now your real controlers might be using up the first two indexes, so you might want to move it to another index. windows xp doesnt seem to let you change a controlers index but i remember older versions let you. you might try uninstalling all controlers, and install the virtual device first, followed by the real controlers, that is if the software lets you.