(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.
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.
controls in the cockpit vs. which wheels they apply to. FlightGear now
sets /controls/gear/brake-left, /controls/gear/brake-right, and
/controls/gear/brake-parking. It should be up to the FDM to sort out
which wheels under which circumstances are affected by these controls
and ultimately what happens to the physical motion of the aircraft.
I'm using a different Joystick now, but these changes
were on my harddisk for a while and should be in CVS:
replace "squared" by "power 3" (the X8-30 is of rather
bad quality, and the 3 help to avoid jitter). Add
"interval-sec" settings.
Since several people on the list have been asking questions about this Saitek joystick and the comments at the top of this xml file in cvs were wrong and confusing, I am posting this update with the following changes:
1. Removed the confusing/wrong comments.
2. Added throttle bindings for engines 2 thru 7 (required for the b52).
3. Changed the hat axis to rotate the view continuously (required to see the mag switch in the p51d and just a lot nicer with any 3d cockpit).
This last change makes the hat point the line of sight more like moving your head. This is the way the CH pro-yoke-USB is set up.
If you are not used to this set up and you use aircraft with 2d pannels, you will likely need to use shift-nuberpad-8 to get the original forward view once you look arround.
