Further observation: it seems the aircraft is losing track seconds after you go DCT OKAKI again.. tried it a few times and can't keep track to OKAKI. Crosswind is about 100kt from the left if that's something to consider too?

Let's start a survey amongst customers to see who's interested in extended failures even as a payware option to determine if it's value to develop it or not.

Could this be added/fixed in a coming update?

Thanks a lot by attention!

I have this time to time with more planes. It's something they cannot just fix, it's a MSFS thingy. We just have to live with that.

That's for sure But it is a wonderful bird!

I'm not able to replicate this on my side. The temperature is imported directly from the METAR (16C in the example below). [image: 33b28362-13e7-4fd9-99f9-ca4fca430e75.png] If this occurs again, it would be interesting to know the METAR that is being generated/imported. Mark - Just Flight

I had a hunch that could be related. If it happens again I'll be sure to let you know with a ticket.

Thank you for reporting this. I have logged this on our internal trackers for our development team to investigate further. Mark - Just Flight

Thank you for the feedback. I have passed that on to our IT team for further evaluation. Mark - Just Flight

On the EFIS Control Panels, the APP/VOR button needs to be selected to VOR in order to allow tuning of the VOR DME radios: https://support.justflight.com/en/support/solutions/articles/17000152234-how-to-tune-vor-radios- Mark - Just Flight

I've been able to trigger this pretty consistently. During a turn around if I cycle the FD, the message will appear.

I've submitted a bug report to zendesk- this is not Justflight's bug, but occurs for many users in MSFS 2024

Happening with en route waypoints also: EGSS CLN9R CLN M84 KONAN DCT KOK DCT CIV DCT SUTAL DCT GTQ DCT BAMEV DCT BLM BLM3G LSZH During the SID, given a DCT SUTAL and had the same drift behaviour. Yes, no airway segments there however wasn't only SID/STAR in FMC

@ScotchMist You're welcome. Last night I updated my snippet in Spad to fix the EFIS mode, turning off the displays if plane isn't powered and brightness logic depending on brightness knob in the plane.

@AlphaEcho Under your reminder, I found the knob. Thank you

Thank you for the feedback. We do have a fix for this currently in testing, and if all goes to plan, it should be included in the next update. Mark - Just Flight

For any AFCAS/FMS related feedback, could I kindly ask you to raise a support ticket with Just Flight Support at the following link: https://www.justflight.com/support The F70 & F100 Professional are complex products, so in order to give our support team the best chance at offering speedy assistance, and for any potential bugs to get properly logged and addressed, could you please include any screenshots/videos of the behaviour with your ticket, as well as attaching the log file generated by the product Instructions for locating the log file can be found here: https://support.justflight.com/en/support/solutions/articles/17000152594-where-to-find-the-log-file-s- Mark - Just Flight

The way I understand it, the real aircraft uses a mixture of an internal airport/terrain database, as well as flight data based on the ADCs/Radio Altitude, to determine the aircraft's proximity to terrain. The aircraft doesn't have a 'terrain radar' as such, so it uses the weather radar to detect any terrain surrounding the aircraft. Mark - Just Flight

Thanks for the feedback. It looks like we just need to slightly limit the rotation of the valve. I've logged this on our internal trackers, and we'll tweak that for a future update. Mark - Just Flight