0
Planned

Issue with beginning of descent

Stephen H 2 years ago updated 2 years ago 5

Nice job on the new features!!  I've noticed that the beginning of descent is not displaying at the correct location on the map.  VFR from KJQF to KMCN at 6500 shows beginning of descent 19 miles from KMCN but the marker on the map is about 2.5 miles from the airport.

Answer

Answer
Planned

Thank you for that information. I was able to look at your aircraft template and based on that, we have discovered the issue. There is a bug that does not place the climb/descent points correctly on the map when an aircraft profile is set to use MPH/SM or KPH/KM instead of Knots/NM. The values shown on the NavLog appear to be correct but the markers on the map are misplaced. Our developers will be looking at this shortly and get a fix in place as soon as possible.


In the meantime, you can use Knots/NM and the points will be correct although I know this likely won't match your aircraft instrumentation.


Thanks again for providing the details as they were pivotal in helping locate the issue.

I have the same problem with routing from KHJO to KSAC.  The descent marker is beyond the airfield.

Under review

Could you provide the full details of your route so we can try to replicate the issue? When we plan a route between KHJO and KSAC, the top of climb and start of descent markers are in the expected locations along the route. There may be some other nuance that is causing the markers to display incorrectly so we would like to replicate it so we can fix it if there is something wrong.


Please provide the following:

  1. Departure Airport
  2. Destination Airport
  3. Route Waypoints
  4. Planned Route Altitude
  5. Aircraft Make/Model

Thanks in advance for your help figuring this out.


1. KJQF

2. KMCN

3. None

4. 6500'

5. PA-28

Answer
Planned

Thank you for that information. I was able to look at your aircraft template and based on that, we have discovered the issue. There is a bug that does not place the climb/descent points correctly on the map when an aircraft profile is set to use MPH/SM or KPH/KM instead of Knots/NM. The values shown on the NavLog appear to be correct but the markers on the map are misplaced. Our developers will be looking at this shortly and get a fix in place as soon as possible.


In the meantime, you can use Knots/NM and the points will be correct although I know this likely won't match your aircraft instrumentation.


Thanks again for providing the details as they were pivotal in helping locate the issue.

That's great!  Thanks!