[Flightgear-devel] Re: uneven brakes mystery
* Joacim Persson -- Wednesday 09 November 2005 21:30: I tried a setprop to 0.3 for right wheel in the js config file, and got a 1.0 in the browse internal props dialog. Somewhere control/gear/brake-right is set to 'true' (i.e. not zero). Is this the development version (cvs/head)? m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: uneven brakes mystery
On Wed, 9 Nov 2005, Melchior FRANZ wrote: Is this the development version (cvs/head)? Yes, but it has been the same for shipped versions too. How can I tell which version of fgfs I'm running? fgfs --version didn't work on the version I have installed in /usr/local/... anyway. Think it's the last official stable release. In that installation I've replaced the calls to interpolate with setprop in the js config file, when I first noticed the problem after buying a new js. But it's an a few hours old cvs version I'm working on now. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: uneven brakes mystery
I have pinned down the exact moment in gdb when brake-right is set to 1.0
(without a cause, so to speak), but I feel I don't have enough knowledge
about how FG is designed to come further.
gdb backtrace below. This is after initialisation is done, FG is up and
running and the fire button (apply all brakes) is pressed and held. Just
before this br stop, there was another one with the correct value (from the
nasal setprop to 0.3, which I used for testing instead of interpolate() in
the js config file). I have not a clue where this spurious 1.00 comes
from, nor why it only affects the right wheel brake. It seems like more
than one function has been bound to the button in question, or some list
handler is running amok.
--
Breakpoint 1, FGControls::set_brake_right (this=0x0, pos=1) at controls.cxx:40
40 {
(gdb) bt
#0 FGControls::set_brake_right (this=0x0, pos=1) at controls.cxx:40
#1 0x080a1624 in SGRawValueMethodsFGControls, double::setValue (this=0x0,
value=1)
at props.hxx:404
#2 0x0848f900 in SGPropertyNode::setUnspecifiedValue (this=0x89fa878,
value=0x8af39fc 1.00) at props.cxx:408
#3 0x0805b154 in do_property_assign (arg=0x8af2c70) at fg_commands.cxx:795
#4 0x082f9b92 in FGBinding::fire (this=0xbf4d0f8) at input.cxx:127
#5 0x082f9d8f in FGBinding::fire (this=0xbf4d0f8, offset=1, max=-1) at
input.cxx:139
#6 0x08301368 in FGInput::_update_button (this=0x4baa9008, [EMAIL PROTECTED],
modifiers=204483636, pressed=true, x=-1, y=-1) at stl_vector.h:501
#7 0x082ff5c3 in FGInput::_update_joystick (this=0x4baa9008,
dt=187.94)
at input.cxx:811
#8 0x082fa653 in FGInput::update (this=0x4baa9008, dt=187.94) at
input.cxx:203
#9 0x084c0698 in SGSubsystemGroup::Member::update (this=0xb966d68,
delta_time_sec=187.94) at subsystem_mgr.cxx:237
#10 0x084c0041 in SGSubsystemGroup::update (this=0x891711c,
delta_time_sec=187.94)
at stl_vector.h:501
#11 0x084c0c49 in SGSubsystemMgr::update (this=0x8917100,
delta_time_sec=187.94)
at subsystem_mgr.cxx:297
#12 0x08052b6c in fgMainLoop () at main.cxx:495
#13 0x08088592 in GLUTidle () at fg_os.cxx:114
#14 0x400a4929 in __glutRegisterEventParser () from /usr/X11R6/lib/libglut.so.3
#15 0x400a50ad in glutMainLoop () from /usr/X11R6/lib/libglut.so.3
#16 0x08055567 in fgMainInit (argc=3, argv=0xb424) at main.cxx:1007
#17 0x080519d6 in main (argc=3, argv=0xb424) at bootstrap.cxx:193
(gdb)
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: uneven brakes mystery
Joacim Persson wrote: Andy Ross wrote: Which stick [...]? Saitek Cyborg Evo [...] I have pinned down the exact moment in gdb when brake-right is set to 1.0 (without a cause, so to speak), but I feel I don't have enough knowledge about how FG is designed to come further. What this is showing is a joystick button (not a key) causing a property-assign binding to fire, which is setting your brake property. The problem is, the Cyborg Evo joystick definition doesn't *have* any property-assign bindings. It does everything with nasal scripts. Something odd is going on -- apparently some other stick's binding for the right brake only is being picked up by your configuration. Have you modified the name properties of any of you joysticks files? Can you verify that your base package is unmodified? If you want to continue playing with the debugger, you could try stepping through the joystick initialization (or, alternatively, selectively removing files from your Input/Joysticks directory) to figure out which stick is being incorrectly loaded, and why. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: uneven brakes mystery
On Wed, 2005-11-09 at 21:54 +0100, Joacim Persson wrote: On Wed, 9 Nov 2005, Melchior FRANZ wrote: Is this the development version (cvs/head)? Yes, but it has been the same for shipped versions too. How can I tell which version of fgfs I'm running? fgfs --version didn't work on the version I have installed in /usr/local/... anyway. Think it's the last official stable release. In that installation I've replaced the calls to interpolate with setprop in the js config file, when I first noticed the problem after buying a new js. But it's an a few hours old cvs version I'm working on now. You have more than one version of FlightGear installed? To find out which copy is being loaded when you type fgfs, open up a terminal and type which fgfs and you should get something like /usr/local/bin/fgfs. Perhaps a command line parameter could be added to display the version of the binary and the version of the fg_root data. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: uneven brakes mystery
* Andy Ross -- Thursday 10 November 2005 00:37: stepping through the joystick initialization (or, alternatively, selectively removing files from your Input/Joysticks directory) to figure out which stick is being incorrectly loaded, and why. ... or simply look in the property browser under /input/joysticks/js[0]/. You'll find there these entries: name[0], name[1], etc. ... all joystick IDs that the driver was made for id ... the joystick's ID string; this is one of the name[]s and the reason why this driver was picked up source ... the file path to this driver m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
