Thank you for the feedback. For any AFCAS/ATS 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

@SinkRate https://discord.gg/G75JYXzdc

In 2024 you have made an empty profile for the Alpha and Bravo and thats the one you are using right?

I think people are calling the fact that the compass card moves when the gyro spins up "auto initializing," and that's where the disconnect stems from.

Full state saving in the Starship? gulps Need to get those checklists ready!

I've been thinking of the simplest way to troubleshoot this. What color is the VOR icon on the ND or PFD once it's received? Otherwise, a screenshot would obviously be very helpful for me to see what's going on. Thanks.

The mail is probably being blocked. Your best bet would be to contact Just Flight Support. There is a link on the Support pages with an email address for "orders".

I do wish this plane had dynamic dirt, but you can't have everything you want I guess

It repeatedly seems to not work at all when lightning is very close, but seems to work fine when the lighting is at least 10 miles from me.

It'd be good to get an answer to this.

Just for the record, I tested this again with Grand Duke after the MSFS2024 SU6 update, and unfortunately experienced the same non-save behaviours.

@SadBucket That's the procedure, thanks! I actually did the following: leave in HDG mode, angled towards the localizer, in VLOC mode. Wait for the needle to get close, then put it in NAV mode so it intercepts the localizer. Then hit APR to arm glideslope mode, and let it descend. However, be ready to fly it manually if something's not quite working. I did three approaches with FSIPanel, worked each time. This especially comes in handy when flying in IMC. I think I crashed my Caravan trying to follow ILS while hand flying in heavy precip into PANC on Vatsim once...very embarrassing.

Ok, simple testing complete. Active pause will not stop failures from triggering, whereas esc pause does. That suggests tay esc pause does indeed stop the code from executing, but of course does continue to allow the passage of time. It even automatically turns off active pause, which means my workaround doesn't work. Still, good to know where we are! Edit: but wait, if one manually locks time with the flow widget, then it will stay locked during an escape pause! So true pause does seem to be available with msfs2024. A bit annoying that you need a piece of (paid) third party software to do it, but it does seem to work.

I updated to latest SU and sure enough the display is working again. Imagine that Microsoft SU breaking/fixing things

That's better, all working now...thanks for your help..

@Raller that's it! I do, indeed, use your 851TB livery. Thanks so much for taking the time to figure this out. I've been flying the TBM quite a bit lately since the new sound pack was released, but I'd given up on the 530 as nav/com2. Looking forward to going back to it!

@Voxen exactly how it works. the cabin heat knob is a valve that controls the flow, not the temp, and the outside air controlled by the cabin air knob is routed through the same vent as the cabin heat.