Usually, I avoid in-line answers, but they seemed appropriate this =
time...


"Ron Rosenfeld" wrote in message =
...
On Fri, 13 Feb 2004 21:34:05 GMT, "John R. Copeland"
wrote:
=20
=20

Regarding the choice of displaying DTK on a custom map page,
I believe that will not show the current bearing to waypoint under =
the
circumstance of having been vectored far enough away from course
that the bearing then differs from the DTK.
=20
I'm not sure what you mean here. In the example I gave in my previous =
post
(KEPM -- POM) the bearing and DTK are markedly different. What =
should I
set up to try to reproduce the issue you are talking about?
=20

Reproduce something like the following in your simulator:
When following a flight-plan leg, go to manual tracking,
and alter your heading 45=BA or so.
Note that the BRG to the next waypoint will gradually change,
reflecting the actual geometry of your position vs. the next waypoint,
but the DTK remains at the fixed value for the flight-planned course.

=20
If I'm then re-cleared direct to the next waypoint, I've always liked
seeing the correct bearing display without needing to punch any =
buttons.
=20
Again, I'm not sure I'm following you here. But I think the magenta =
line
will always intersect the DTK on the compass display.
=20

Yes, except that at long-range settings, the magenta line is curved a =
little.
No big deal, actually. You can eyeball the curvature reasonably well,
and guess pretty close to the local value of DTK.

But my point was that sometimes BRG is more important to me than DTK.
The button-pushing I mentioned was to compute a new Direct course.


Furthermore, my MX20 has a prominent display of that "Bearing" =
number,
which becomes the VOR radial reciprocal, too.
I haven't seen a way to change that MX20 field to the DTK.
But it's no big deal. I can cope with it, too.
=20
Did you find that bad spot in missed approaches on the Windows =
simulator?
=20
No. What is it?
=20

After you "Un-Suspend" waypoint sequencing in the Windows simulator,
and perform the missed-approach procedure, the aircraft position is =
computed
correctly as you proceed toward the Missed-Approach Hold Point,
but the distance and time to that next waypoint get continually reset to =
their
initial values.
The workaround is to force a "Direct-To" to the first waypoint of the =
procedure.
This bug does not occur in the actual CNX80 or its built-in simulator.

I have not heard back from my Apollo contact since I called his =
attention
to this bug three weeks ago.
I also have not tried downloading the Windows simulator again, to see if =
it's changed.
If you don't see the missed-approach bug, say so, and I'll get myself a =
fresh copy.
---JRC---