fly/flightgear
1
0
Fork 0
Code Activity

Proposed fix for #251: Waypoint handling

Browse source 
Do not consider destination/runway waypoints as done, when these
are far away - even if the course is off by > 90 degrees.
This commit is contained in:
ThorstenB 2011-01-28 00:06:23 +01:00
parent 91d001ff4e
commit f68f300bb3
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/Instrumentation/rnav_waypt_controller.cxx
View file

@ -221,7 +221,7 @@ private:
/** /**
* Special controller for runways. For runways, we want very narrow deviation * Special controller for runways. For runways, we want very narrow deviation
* contraints, and to understand that any point along the paved area is * constraints, and to understand that any point along the paved area is
* equivalent to being 'at' the runway. * equivalent to being 'at' the runway.
*/ */
class RunwayCtl : public WayptController class RunwayCtl : public WayptController
@ -252,7 +252,7 @@ public:
double _courseDev = brg - _targetTrack; double _courseDev = brg - _targetTrack;
SG_NORMALIZE_RANGE(_courseDev, -180.0, 180.0); SG_NORMALIZE_RANGE(_courseDev, -180.0, 180.0);
if (fabs(_courseDev) > 90.0) { if ((fabs(_courseDev) > 90.0) && (_distanceM < _rnav->overflightArmDistanceM())) {
setDone(); setDone();
} }
} }