Hi Am on iMac G5 with Flightgear and a Saitek ST290 Pro stick. Recently found Flightgear and love it. Problem is I'm not a developer - and I have NO idea how to get my joystick to work properly. Right now it just about works, but no rudder (it's a twist stick) and no throttle lever.Makes steering on take-off impossible and today I landed a P51 mustang by 'blipping' the engine on and off because I had no throttle levers for it.Anyone else with a non-programmer solution to joystick problems? Thanks!

[saitek ST290 Pro]>I have NO idea how to get>my joystick to work properly. Right now it just about works,>but no rudder (it's a twist stick) and no throttle lever.Start fgfs, open the property browser (Menu->File->Browse internal properties), go to /input/joysticks/js/ and look what the "name" entries, the "id", and the "source" entries say. We have a driver for the "Saitek ST290 Pro", but my guess is that it isn't used and "name" is "default". If so, run the "js_demo" application, look which name it outputs for joystick #0, and whatever it is, add a second entry with this name in file $FG_ROOT/Input/Joysticks/Saitek/ST290-Pro.xml. Run fgfs again and check in the property browser if the js is now found. If this worked, tell us the name that you had to add.

Where abouts is the js_demo application hidden in the Mac OS distribution?I've had a hunt around for it, and haven't been able to find it (Have been looking inside FlightGear.app)I'm in a similar sort of boat. I've got the ST90 (which I figured would be the perfect portable joystick for my perfect portable laptop, but it recognises the axes wrong (z is used for elevation and x is throttle while y is roll - absolutely bizzare to try and fly).Now that I know where to look to see if which xml config document, I should be able to work the rest out.That said, a reference document for the input XML documents *would* be kinda cool.I've also got two of the Saitek Cyborg USBs, the ones before the Cyborg Gold which still have the left-drift problem. What it *looks* like is that the raw data for the x, y center position is about 90, 90, which it's happy to accept as center. BUT it doesn't seem to want to take any values for the axes above 100, so I can bank left and dive, but that's about it (just like one of those annoying radio controlled cars that has two speeds, forwards and turn-left-while-going-backwards).(I'm not looking forward to configuring my X36)

> Where abouts is the js_demo application hidden in the Mac OS> distribution?no idea, but you don't need it anyway> I'm in a similar sort of boat. Then read what I have explained above and do it. The rules are the same for all in this boat. Reading /input/joysticks/js/id in the property system tells you the joystick name. /input/joysticks/js/source tells you the path to the used joystick driver. And /input/joysticks/js/name* tells you why it was chosen.

>Now that I know where to look to see if which xml config>document, I should be able to work the rest out.>>That said, a reference document for the input XML documents>*would* be kinda cool.Well, there IS a reference document about Joystick setup under $FG_ROOT/Docs/README.Joystick.htmlIf this is does not work for you, you may want to augment it when configuring your own joystick and send your augmentations to the FlightGear developers, so that this file can be updated.>I've also got two of the Saitek Cyborg USBs, the ones before>the Cyborg Gold which still have the left-drift problem. What>it *looks* like is that the raw data for the x, y center>position is about 90, 90, which it's happy to accept as>center. BUT it doesn't seem to want to take any values for the>axes above 100, so I can bank left and dive, but that's about>it (just like one of those annoying radio controlled cars that>has two speeds, forwards and>turn-left-while-going-backwards).>>(I'm not looking forward to configuring my X36)Well, are these devices in general set up properly for your system? That is, do other simulators work just fine with them?

>Well, are these devices in general set up properly for your>system? That is, do other simulators work just fine with>them?Well yes and no.Under Mac OS X, there isn't a 'directX' type application that everything talks to to get information on game controllers.There is a game controller API tied into the OS, but not everybody uses it (it seems to me like FlightGear might not be using it, but I haven't looked through the source).Saitek in particular don't offer any Mac support at all and list their products as not being Mac compatible. That said, the copy of Nanosaur that came with my machine allows me to set center, max and min values for each axis and everything works fine.>Well, there IS a reference document about Joystick setup under>$FG_ROOT/Docs/README.Joystick.html>If this is does not work for you, you may want to augment it when>configuring your own joystick and send your augmentations to the>FlightGear developers, so that this file can be updated.I had a look through the joystick readme, but at the time (before I found out how to see what xml file was being used) it wasn't much help to me.I reckon I'll sit down and have a crack at it next weekend.The X36 is a hands-on-throttle-and-stick system and is a nightmare to set up for any software (It's got something like 60 buttons and 5 axes).