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

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

I tried many things including reinstalling the sim but the problems with the gps are not solved. 750/650 does not start up and the 530/430 has always the message of no gps. I use the premium version of the gtn750 in many aircrafts without any issues. Only in the caravan this happens.

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

@jmarkows I know you implemented the VS properly with 200 fpm increments but I kinda love that you can make it increment by 100 fpm and the dial animates to a spot between the digits. "No... I really want to descend at 500 fpm, thank you."

There are NAV and GPS labels on tne button, but when you have the RNAV511 selected, pressing the button toggles between RNAV and NAV and I have annuciators for both. It does mention that the RNAV doesn't work if you have a GPS unit installed as it can't have all three at the same time.

There isn't a single simvar for that since the current course heading could be either: L:var_Rnav511_OBS_R or L:var_Rnav511_OBS_L if the RNAV computer is driving navigation and depends on which waypoint button is pressed A:GPS OBS VALUE or A:GPS WP DESIRED TRACK if GPS is driving navigation and depends on if the GPS is in OBS mode or not A:NAV OBS:1 if you're just doing ordinary VOR navigation without the RNAV or GPS I might be missing something if you have the GTN 750 installed... I only use the 530. I ended up writing a custom .lua script to derive the MC60 OBS value and basically followed the same logic that the panel instrument uses. I suppose it'd be more convenient if there were a separate "read-only" LVAR for the MC60 OBS value.