I've got a Saitek ST290-Pro joystick. It's recognized by both js_demo and jstest. I see that there is an xml file in Input/Joysticks/Saitek but I dont think it's being used. The axis 0,1, and 2 work (elev, aileron, throttle) but nothing else listed in the ST290-Pro xml file work. Axis 3 (twist) is supposed to be for rudder and 4 and 5 (HAT) are for view changes. These dont work for me so I'm assuming Flightgear is using some other joystick defaults or something. How can I set things so FG uses the proper xml file for my joystick?

>I've got a Saitek ST290-Pro joystick. It's recognized by both>js_demo and jstest. I see that there is an xml file in>Input/Joysticks/Saitek but I dont think it's being used. The>axis 0,1, and 2 work (elev, aileron, throttle) but nothing>else listed in the ST290-Pro xml file work. Axis 3 (twist) is>supposed to be for rudder and 4 and 5 (HAT) are for view>changes. These dont work for me so I'm assuming Flightgear is>using some other joystick defaults or something. How can I set>things so FG uses the proper xml file for my joystick?Assuming that you are using a rather new FlightGear version (>= 0.9.9): check in the property browser (Menu->File->Browse Internal Properties) in /input/joysticks/js[0]/ if the path[0] property contains the path to the ST290 driver, and if the id[0] property is identical with one of the name[] entries. It could be that your joystick doesn't send one of the name[] strings. In this case, open the driver and add an additional ... entry with your *exact* joystick id. Then try again.

ok it was not the same value. The name tag/property in the supplied xml file read "Saitek ST290 Pro" while my system ids it as "SAITEK Saitek ST290 Pro". I changed it in the xml file and now all axis and buttons work as expected. Thx much! :-)

>ok it was not the same value. The name tag/property in the>supplied xml file read "Saitek ST290 Pro" while my system ids>it as "SAITEK Saitek ST290 Pro". I changed it in the xml file>and now all axis and buttons work as expected. Thx much! :-)There's no need to change the original line, rather the right approach would be to provide an additional entry for the string that's used.When you have modified your file in this fashion, it is usually appreciated to send it to a FlightGear mailing list, so that it can be committed to CVS, so that future versions of FlightGear will automatically recognize joysticks such as yours: http://www.flightgear.org/mail.html