Author Topic: Force feedback plea  (Read 120 times)

Offline -luny-

  • Zinc Member
  • *
  • Posts: 2
Force feedback plea
« on: November 04, 1999, 04:39:00 AM »
Hiyas all...I've been flying AH (offline only) and there doesn't seem to be any force feedback yet. At least I haven't found any such tab in the setup.

If it hasn't been implemented yet, I'd like to take this opportunity to plead for us CH Force FX owners. CH Products and Immersion have ceased to support the CH Force FX because it's an I-force 1 device, whereas the current FF sticks use the I-force 2 API.

I-force 1->2 "translating" drivers for DirectX use were released and supported until mid-1998, but now there will not be any more DirectX driver updates. The latest drivers are from July 1998 and were written for DirectX 5. (Quitting all support like this is infuriating because the stick has only been around for 3-4 years or so, and is so bomb-proof that it will last a lifetime - and it's an excellent stick too, allowing external pedals and throttle without any problems, making it the stick of choice for many hardcore flight-sim enthusiasts).

This is causing serious problems - for instance, in Warbirds the CH Force FX DirectX drivers cause system freezes in online play. The force feedback you get in DirectX is crude compared to the old non-DirectX CH Force FX driver.

So, here's my plea: AH folks, when you implement force feedback, please make the I-force 1 non-DirectX force feedback support an option. This used to be the standard in the last Warbirds 1.x versions before DirectX became the only supported FF API in WB 2.0. There are plenty of I-force 1 sticks around (they all happen to be called CH Force FX) with very dedicated pilots behind them.

I'm currently trying to persuade WB folks to re-install the old FF support as an option in WB/DoA too...I sure hope they'll be so kind.

Luny

Offline -luny-

  • Zinc Member
  • *
  • Posts: 2
Force feedback plea
« Reply #1 on: November 10, 1999, 05:34:00 AM »
And foithermore...  

Once the FF code gets looked at, would it be possible to have separate trim force sliders for aileron and elevator? Well, FF pedals are probably just a matter of time, so better make it 3 sliders...

Are there any plans to support a zillion analog axes through a USB port, btw? I understand this would require coding support for, say, 10 control axes and letting the user assign them to trim, toe brakes, prop pitch, whatever. Oooh, I would love to have toe brakes and analog trim and prop pitch  

Getting carried away here...avoiding the CH Force FX DirectX freeze bug is still my AH concern n 1.

Luny