torsten [Wed, 24 Mar 2010 14:25:36 +0000 (14:25 +0000)]
Bugfix:
- METAR changes caused strong aircraft movements if the station temperature or field elevation changed. Temperature and dewpoint are now also slowly interpolated to reach the new value.
- Probably unnoticed bug: calculation of the interpolation speed was wrong.
- some minor code-cleanup
torsten [Sat, 6 Mar 2010 15:40:17 +0000 (15:40 +0000)]
Just a tiny change adds a <reference> input to FGDigitalFilters. This is nice to have to calculate differences of signals using gain-filters.
Old calculation was
output = input * gain
and is now
output = (input-reference) * gain
Note: the PI(D) controller use (reference-input) which effectively reverses the sign. Our notation was picked for backwards compatibility to not break the myriads of <filter> elements currently existing.
jmt [Sun, 21 Feb 2010 20:44:17 +0000 (20:44 +0000)]
GPS / route-manager: add new custom widget to display the waypoints list.
Supports various new editing features, including dragging to re-order, and
+/- keys to adjust the target altitude for a waypoint. Also displays some
additional information, and will display *even* more once I land airways/
SID/STAR support.
jmt [Fri, 19 Feb 2010 00:31:38 +0000 (00:31 +0000)]
bug #80, exception flying west from NZAA (Auckland, NZ). The underlying
issue is numerical problems in _wgs84_inverse, triggered by the traffic-manager
testing enormous distances geodetically.
Changes
- refactor AISchedule::update, so the aircraft approximate position
calculation is simpler.
- refactor AIAircraft to no longer use exceptions as a return value mechanism
- change AISchedule::update to use cartesian math for in-visible-range check
jmt [Wed, 10 Feb 2010 19:28:35 +0000 (19:28 +0000)]
Bugfix #35 / denker #20F:
Guard against invalid font names in panel XML files, and make font name
comparisons case-insensitive so that 'helvetica', 'Helvetica' or 'HELVETICA'
work as expected.
durk [Sat, 30 Jan 2010 15:40:33 +0000 (15:40 +0000)]
A couple of last-minute patched / bugfixes to mitigate the probability of collisions between user controlled aircraft and AI traffic.
* AI aircraft distance to user proximity detection works again (lat/lon were inverted).
* The parking uses by the user aircraft is marked as such to prevent it being reused by an AI aicraft
* AI aircraft won't receive permission for pushback until the user aircraft is at a fair distance.
torsten [Fri, 22 Jan 2010 17:00:32 +0000 (17:00 +0000)]
bugfix
Patrice Poly:
After investigation, it appears that the probes are reversed due to a
little mistake when someone changed how the probe calculations are made.
probe 0 is under the plane. probe 4 should be downwind, probes 1,2 and 3 should be upwind.
durk [Sun, 17 Jan 2010 19:41:47 +0000 (19:41 +0000)]
John Denker:
Subject: [PATCH] Make terrasync more usable, more like a proper daemon.
-- writes pid to file
-- normally does not exit until signalled
-- uses blocking and non-blocking I/O as appropriate.
jmt [Sun, 10 Jan 2010 23:35:53 +0000 (23:35 +0000)]
GPS: improve reliability (at the expense of some in-development features) for pending release.
- default to an invalid altitude in routes, instead of cruise altitude (temporarily)
- only set an altitude on the autopilot, if valid
- only add departure airport/runway to the route, if not airborne
projects / flightgear.git / log