You should have a look at the bindings in your joystick.xml file as there a bunch of defaults in there that you probably won't like.
I locally have a chproducts.xml file which is used inside the preferences.xml file instead of the standard joystick.xml file, so that CVS doesn't keep whingeing about all my little local variations. > Hello again, > > To set the stage, running the current CVS version of everything, on a > P2-300 Linux machine with kernel 2.4.18. Interfacing with CH Flight Sim > Yoke USB and CH Pro Pedals USB. Working great with the default c172, now > that the old (failed) Nvidia card is replaced with a GeForce2MX. > > Just tried the c310, triggered by comments on its progress, and I fully > agree. Did some tweaking to my .fgfsrc to handle the dual engines, and > everything looked good at first. An extract of said file is below (cut a > bit to save space). Further trials showed an interaction between the > rudder pedals and the right throttle. > > Initially, throttle worked as expected, ganged because of a shortage of > input axes. A slight touch on either pedal makes the right throttle jump > to half scale, and then the throttle tracks the pedal movement. With > pedals still, any change of the hand throttle recaptures control. > > This is what I would expect if event records from the rudder pedals were > leaking into the throttle "circuit". I checked for other interactions, > such as the reverse direction, but > this is the only one I could spot. The question is where and why. > > Running js_demo shows all axes working, and no interaction in this > program. Is there a small bug in the command parsing or (more likely) an > error in my configuration caused by my limited understanding? > > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/property=/controls/throttle[0] > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/command=property-scale > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/squared=false > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/dead-band=0.00 > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/factor=-0.5 > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/offset=-1.0 > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/property=/controls/throttle[1] > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/command=property-scale > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/squared=false > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/dead-band=0.00 > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/factor=-0.5 > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/offset=-1.0 > # > --prop:/input/joysticks/js[0]/axis[2]/binding/property=/controls/rudder > --prop:/input/joysticks/js[0]/axis[2]/binding/command=property-scale > --prop:/input/joysticks/js[0]/axis[2]/binding/squared=false > --prop:/input/joysticks/js[0]/axis[2]/dead-band=0.00 > --prop:/input/joysticks/js[0]/axis[2]/binding/offset=0.0 > --prop:/input/joysticks/js[0]/axis[2]/binding/factor=1.0 > # > > -- > Bill Earnest wde3@ptd-dot-net Linux Powered Allentown, PA, USA > Computers, like air conditioners, work poorly with Windows open. > > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
