"Saitek Pro-Flight-Rudder-Pedals's name differs in windows from linux,
and the axis for the rudder is 3, not 2... assumes Mac uses same channel
as windows, but could be wrong... linux is set to channel 2, and windows
and mac is set to 3"
(This fgcommand was broken for a few weeks. Now it's fixed, but the
wrapper use is desirable, as this allows easy redefining.)
- cyborg gold: cosmetics
(if <name> isn't defined, "Axis #0", or "Btn #2" etc. are used in the
joystick info dialog; <name>s should at least be used for entries with
OS specific indices)
property /rotors is available at joystick driver laod time. Note that
the FDM creates /rotors *afterwards*, so it needs to be defined in the
*-set.xml file already (which is the case for all helicopters in CVS).
A simple, self-ending <rotors/> tag should do.
I got a new joystick, a Speedlink Black Hawk (USB) with force feedback for
which I have written a setup xml file (see attachment) since with the default
setup, the rudder control didn't work.
Perhaps you could include it in the next version of Flightgear, such that
other users with the same joystick could immediately use it. The xml file
contains a description of the axis/button setup and should be self-explanatory.
I am using Windows XP but I guess the configuration should at least work on
all Windows platforms, no idea whether it works under Linux.
It would be great if one could get the vibration function to work (for
touchdown, running over uneven ground, plane stalling and the like) but I
frankly don't know how to do it. Has anybody already implemented force feedback?
Let me stress that Flightgear is a great sim and that I really enjoy it a lot!
You all are doing a great job!
I've just purchased a Logitech Attack 3 usb joystick and it
works great with Flightgear.
It has 11 button and a throttle control.
I have attatched an xml file for inclusion into Flightgear.
The buttons are as follows:
Trigger Button 0 : Brakes
Button 3 : Elevator trim up
Button 2 : Elevator trim down
button 6 : Elevators up
button 7 : Elevators down
button 8 : Brake left
button 9: Brake right
With buttons 11 - Gear up
Button - 10 Gear down
joystick configuration for a Wingman Force 3D USB.
mfranz:
This driver is supposed to work for the non-USB versions, too, so
I'm replacing the non-USB driver with this one, and add its <name>s
here. If it turns out that we need a separate driver, it's better to
derive it from this file, as this is adapted to the newest methods
(nasal wrappers, etc.), while the old driver was only partly functional.
Here is an other one to the data directory. It updates the carrier launchbar
command and catapult launch command to reset itself if the key is no longer
pressed. That fixes the odd behavour, that once a carrier launch happened, a
second lauch happens no longer immediately at arresing time.
The proper file ( the one with axis assignment set correctly for all OSes ) was too quickly removed, certainly because of its -win suffix.
I merged the good things in one file, discarding the problematic ones.
Initial revision. This is the only joystick that the Walmart next to my
house is selling. (What are you going to do?) Buttons 2 and 4 are still
unmapped awaiting any good suggestions.
- to support "old-style" gear/flap control (operation as long as button
pressed/lever pushed -> b29/hurricane), let bindings not only report
up/down, but up (-1), stop (0), down (1).
- let controls.flapsDown() ignore "stop" so as to remain compatible with
prior behavior
- adapt all joysticks/aircraft (sigh)
- some minor cosmetics in joystick configs, such as indentation fixes
avoids the obscure and ugly "which" workaround
Note that the input subsystem sets variable "this" to this joystick's
base property path; This is useful to be able to access the driver's own
information from the property tree. Example:
data = props.globals.getNode(this).getNode("data");
where "this" contains string "/input[0]/joysticks[0]/js[0]" if the js is
the first in the system
for operation-modes; only one user visible change: the speed brake toggle
does now also show a popup like the thrust reverser and the parking brake;
I hope that this is seen as useful help rather than annoyance.
The one hat axis should be 4 for Unix/Linux and 6 for windows (according
to someone on IRC), while the other hat axis is apparently 7 for all
systems. Changed the throttle to Nasal, too.
I didn't nasalify the rest, because that's error-prone and I wouldn't
be able to test it.
