Bugs: Difference between revisions

Jump to navigation Jump to search

Bugs (view source)

Revision as of 17:25, 18 March 2010

3,346 bytes removed ,  18 March 2010
removed list of fixed bugs
m (out of date)
(removed list of fixed bugs)
Line 700: Line 700:
support for 2D instruments.
support for 2D instruments.


==== Broken startup banner. ====
==== Broken start-up banner. ====


On startup, the simulator prints Author: Unknown and prints a bogus Date.
On start-up, the simulator prints Author: Unknown and prints a bogus Date.


The printout comes from JSBSim and refers to the (lack of) author, date and version fields in the JSBSim flight model XML file for the aircraft. According to the schema for JSBSim-ML (the markup language specification for JSBSim aircraft) the author, creation date, version, and description are not required fields, so the message that is printed out should account for missing elements.
The printout comes from JSBSim and refers to the (lack of) author, date and version fields in the JSBSim flight model XML file for the aircraft. According to the schema for JSBSim-ML (the markup language specification for JSBSim aircraft) the author, creation date, version, and description are not required fields, so the message that is printed out should account for missing elements.


== Fixed Bugs ==
If the fix refers to a version number that hasn't been released yet, it means that the fix is in CVS (this makes life easier maintaining the page - status doesn't have to be changed each release).
==== Out-of-bounds array reference in JSBSim ====
This is in the interpolation table code.
This bug has been fixed in the [[http://jsbsim.sourceforge.net/ SF CVS]] version of JSBSim.
==== Memory leak in JSBSim ====
This is in the "message" handling code.
This bug has been fixed in the [[http://jsbsim.sourceforge.net/ SF CVS]] version of JSBSim.
==== Wild accelerations at low speeds. ====
Improper inclinometer ball indications have been observed:
* When parked, the ball was pegged to one side.
* When taxiing at low speeds (a few knots or less) the ball oscillated wildly back and forth.
This was observed in the c182 model and in the default c172 model.
Tracing indicates that the problem is not within the slip_skid_ball.cxx
code, but rather upstream of there, in the flight dynamics.  Tracing
shows that the y-accel-fps_sec values are wildly fluctuating in
direction, and enormous in magnitude.
Additional evidence pointing to the FDM comes from the fact that
the problem is observed with JSBSim and not with larcsim (although
larcsim has other problems, such as drifting slowly sideways while
parked).
This is important from a procedures training point of view. 
If you want to have a realistic flight, one of the checklist items is to verify, insofar as possible, that the instruments give correct indications during preflight and taxi.  In a real aircraft, a pilot who found the
inclinometer pegged would cancel the flight before even starting
the engine.
Note: This has probably been resolved in the latest release of JSBSim that is now incorporated into FlightGear. It may have stemmed from bad ground reactions modeling. Standalone tests with JSBSim and the C-172 sitting on the runway show the following properties steadily holding at zero:
*velocities/vdot-fps
*velocities/a-pilot-y-ft sec2
*velocities/n-pilot-y-norm
* '''This bug has been fixed in 0.9.11.'''
==== Misdirected diagnostic in JSBSim.cxx ====
The file JSBSim.cxx directed the last four lines of a five-line diagnostic message to cout.  This made both the log and the console record hard to interpret.
* '''This bug has been fixed.'''
==== Linux and perhaps Windows crashes when specifiying --lon or --lat ====
The 0.9.8 version of flightgear has an issue with starting coordinates that are lie on the boundary before tiles or coordinates.
Workround: Specify the latitude as a slight offset to what you require. Eg instad of --lon=16 make it --lon=16.0001 The difference visually is next to nothing. :-)
* '''This bug has not been observed in 0.9.10.'''
==== 0.9.5 - 0.9.8 - Windows - Crash on start reporting "Could not gen source" ====
Any further reports or stacktraces on this bug would be appreciated.
Workround: Launch two copies of FGFS in quick succession: one should work. You may need three.
Update your sound card drivers.
* '''This bug has been fixed in 0.9.8a'''
==== 0.9.7 - ? Linux - Joystick crash with correct config files ====
Workround: Comment out any unused axes (and, possibly buttons) in the config file - if your joystick has 3 axes, comment out axes 4 through end.
* ''' This bug has been fixed.'''


== Related content ==
== Related content ==
Michaelfavor
240

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/20108"

Navigation menu