Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

Recommended Posts

Reference to the image below.

 

As you can see, in the MCDU it shows 13 nm to T/D while on the ND it shows much closer.

 

Which one should I be following? This has always left me wondering. Normally, I follow the ND T/D marker.

Desktop Screenshot 2019.03.09 - 00.22.57.84.png

Share this post


Link to post

Thanks so very much for writing to us about this!

 

This is interesting, and I don't recall ever having seen it!  I'll be doing a flight later today and will give it a look to confirm.

 

I'll post after my flight, which won't be for another 7 hours or so.

 

Thanks again!

 

Best wishes!

 

Share this post


Link to post

Please always add the flightplan for these issues.

Share this post


Link to post

Just a quick update... real world events prevented me from booting up the computer yesterday... I'll test this over the weekend and report back.

 

 

Share this post


Link to post
On 3/8/2019 at 7:34 PM, Mathijs Kok said:

Please always add the flightplan for these issues.

 

Hi Mathijs,

 

Here's the FP used for this route: RBV J230 COPES J75 MXE CLIPR2

 

Share this post


Link to post
7 hours ago, jmrtlara said:

 

Hi Mathijs,

 

Here's the FP used for this route: RBV J230 COPES J75 MXE CLIPR2

 

 

Airport ICAOs?  Also, was there a SID?

Share this post


Link to post
On 3/17/2019 at 10:24 PM, DaveCT2003 said:

 

Airport ICAOs?  Also, was there a SID?

 

Hi Dave,

 

This was KJFK to KDCA.

 

SID used was JFK5, and the STAR in to KDCA is CLIPR2 for the RNAV app to rwy 19.

Share this post


Link to post

Hello,

 

Just an update on this.

 

I noticed that if the situation is like this:

 

FIX1 - 10 nm

T/D - 10 nm

 

It displays correctly in the MCDU. But as soon as you pass over FIX1, instead of showing the T/D with the proper distance to go, which in this example, let's say 10 nm, it gives an odd distance. See example below.

 

I think it might just be a minor visual bug I thought of pointing out again, as long as it properly descends on the profile, I'm happy. :D 

 

 

2019-4-7_18-52-57-58.png

Share this post


Link to post

During my tests I have noticed similar behaviour as well. I will add this on our to do list, but cannot give any eta for fix at this moment.

Thanks for the reports!

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...