Hey. I recently installed flight gear, and it looks great. However, whenever I load up the game (any plane, any airport), the camera just keeps spinning to one side. When I unplug my Saitek joystick, it stops spinning. Any ideas?

try right clicking with your mouse until you get the <-> cursor, and thsan left-click to center the camera.

Hmm.. I gave that suggestion a shot and it didn't work. When I unplugged my joystick, it stopped spinning. I guess something is not calibrated.

>the camera just keeps spinning to one side. When I unplug my>Saitek joystick, it stops spinning. Any ideas?That happens if the hat-switch axes don't match. Which joystick is it exactly? What does js_demo(.exe) say for joystick #0? (Exact name string, please, including trailing spaces and other garbage.)Alternatively, you can look up this name in the property browser (Menu->File->Browse internal properties) under /input/joysticks/js/id.

I'm not the original poster, but I have the exact same problem. The string you asked about is:id[0] = 'Microsoft SideWinder 3D Pro' (string)as reported from the Browse Internal Properties. Any ideas on how to fix it? I tried running fgjs.exe once, but it didn't make any difference.Looks like a pretty near flight sim, speically for free! Hope I can get it working with my joystick though.

> id[0] = 'Microsoft SideWinder 3D Pro' (string)OK. A driver for this joystick is included in FlightGear 0.9.9.First start the "js_demo(.exe)" program and move the hat switch. Note down the axis numbers that react to hat switch movements. They are probably "6" (left/right) and "7" (up/down) on MS-Windows.Now open the driver file, which is in the FlightGear data directory under .../Input/Joysticks/Microsoft/sidewinder-3d-pro.xml. (You can first verify in the property browser again if /input/joysticks/js[0]/source shows this same path, which means that FlightGear found the correct driver.)Open this XML driver file and search for the hat axis definitions: View Direction ...and View ElevationReplace "4" and "5" with the numbers that you got from running js_demo ("6" and "7").