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.

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

@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.

If you use those H-events then it'll work in all circumstances: NAV/GPS and RNAV modes.

I've just looked into this, and the manuals list the absolute Maximum Weights of the F70 and F100. Between the two aircraft, there are almost 20 different Maximum Weights that the real aircraft are certified for. Those can vary based on the specifications the aircraft left the factory with, as well as service bulletin modifications. The aircraft we simulate are each based on one of those Maximum Weights, but they aren't based on the absolute Maximum Weights listed in our Operations Manual. The F70 we simulate has a MTOW of 37,995kg, and the F100 has a MTOW of 44,450kg. We'll make a note to take a look at the weights in the Operations Manual the next time it's updated. Mark - Just Flight

Not to beat a dead horse. But any news on adding the ability for you to broadcast the FMS so we can use it on hardware equipment. I personally use spad next. But others use different things. This is the only single payware plane I own that doesn't support this feature. It's important. thanks

We are just coming to the end of a full rewrite of the holding pattern logic, and we intend that work to form the basis of the v1.4 update. Included with that will be some improvements to the missed approach logic, but we'll share the exact changes closer to the v1.4 release. Mark - Just Flight

Thank you for the feedback. This is something our IT team has on their list to implement in the future. Mark - Just Flight