I don't have Windows at home, and I've never really tried FlightGear
on Windows before. Yesterday I had an opportunity to give it a spin on
a nice computer with Windows Vista.

The joystick I had with me is a Saitek Aviator (USB HID). FlightGear
doesn't have a file for this yet, but I have written my own (which I
am nearly ready to submit), and I put it in the appropriate place in
the data directory (Input/Joysticks/Saitek/Aviator.xml). This file
works fine in Linux and OS X.

FlightGear did not recognize the Joystick file, so I got the default
behavior. Actually, on closer inspection I learned that FlightGear did
not recognize the Joystick, and it had nothing to do with my file.
When I run js_demo.exe I see a message about not being able to find
the joystick name in the registry (or something to that effect) and it
identifies the joystick as a generic Microsoft joystick. js_demo does
report all the axes and buttons.

I then installed the Saitek drivers for the joystick from their
website, and tried again with the same results.

I'm aware that you can statically configure a particular joystick file
instead of using the "by name" approach, and that would be fine as a
workaround. Or there's always the calibration program. I'm not looking
for a workaround, I'm just reporting odd behavior and curious about
what's going on.

Is this an oddity of Vista? Or is it a known problem (or "feature") of
all Windows? I did try FG on Windows XP once with a CH Yoke and Pedals
and I seem to remember that worked fine, but my memory is hazy.

-- 
Hans Fugal
Fugal Computing

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to