Mapping ANALOG DirectX-buttons

[DonULFonso]

Hm, I hope I don't come across as bitching or not thankful, but this in fact is a bummer:

Only the 1st controller is recognized and accepted, not even the one set to be the default controller in the properties.

This means that if I really want to use this new feature (and THX for adding it!) I need to unplug all other controllers and just leave the one connected that I want to use.

This IMHO is not perfect yet, since as it happens game-port devices are sorted in 1st before USB-devices. Opposite to USB-devices they don't support (or even fancy) hot-plugging, so I'd have to power down, crawl under the table, unplug my game-port gear and start up again.

Would it be (too) much asked to please look into this and at least use the controller that's set as standard, or even allow to specify which of the connected controllers to use?

[ericd]

Hmm.. It's suppsed to enumerate all controllers available in the system and use them. I'll take a look at the code and see what I can discover.

Please let me know which devices you are using so we can try and test with them. There are lots of different devices out there so the more we can cover the better.

[DonULFonso]

I've got a Thrustmaster F-16 FLCS and TQS stick and throttle with the digital chipset, hence an SWF22, at the game-port (this is the only controller 'seen' by the TrackIR's 4.00.23 software), a Thrustmaster HOTAS Cougar stick and throttle plus RCS pedals at an USB-port (this one's specified as the default controller to be used), plus a Thrustmaster Firestorm Dual Power 3 gamepad at another USB-port.

[ericd]

I think I may have found the problem. I need a couple of testers with non-joystick devices to email me so I can try out my fix. Please email ericd@naturalpoint.com and we'll go from there.

Thanks!