@Black-Square if only Microsoft allowed freeware on the marketplace...

@neinnunb great. Thank you for the answer. Maybe I will buy it and give it a try

+1 - really hope the team can seriously consider / explore the 650s as a post-release update.

I'm not able to replicate that behaviour on my side with the latest version of the 146 and GSX, so it'll definitely be worth creating a ticket with Just Flight Support. In the ticket, if you could provide the information that you have in this thread, plus the video that you have recorded, then that will put our support team in the best position to attempt to replicate that, and log it for further investigation if required. Mark - Just Flight

From our internal testing of the post-SU4 updates, we reliably see the correct state recalled on the first flight of a session, and then it becomes inconsistent on subsequent flights in the same session. Mark - Just Flight

Sorry, I didn't give much thought to the term "optional". Your explanation is clear. Thank you.

Ok, clear. Thank you

That workaround seems to work for me. Thank you for the suggestion.

@GJDober can I ask how you turn the alarm off? I ran into this exact situation a few times and could not figure out how to turn the alarm off. Very new to this aircraft so I appreciate any help. Thanks!

Yes, that's correct. I must have eliminated that variable during development. You can use the B:Var, K:TOGGLE_PROPELLER_DEICE, A:PROP DEICE SWITCH:1, or set the circuit directly with A:CIRCUIT SWITCH ON:30.

I’ve identified the issue — it turned out to be a simple misconfiguration in SPAD.neXt.

@Black-Square Thank you very much for the quick reply. Everything is beautiful and works great — the only downside is the persistence saving. I guess I’ll have to come to terms with that. It is a bit strange that the Hobbs shows 2 hours, which means it must have been saved at some point. I have a feeling that the method of ending the flight and then immediately reloading the aircraft, and only after that exiting to the main menu, actually worked — I’ll verify it tomorrow. Otherwise, I really don’t know what else to try. At this point I’ll probably just have to wait. I’m not sure how others are dealing with it. Most likely the same way — they’re waiting too.

Now that I noticed this behavior I cannot unsee it. You mentioned third party GPS already make use of the default NAV IDENT variable, which explains why you coded it this way. But could you make it more realistic when using one of the non-third party units? For example, when using the "default" GNS 530/430 and/or your KX155B/KNS81 combo (the so-called no-GPS config), would it be possible to give us at least the option to disable to automatic flipping of the relevant switch on the audio panel (perhaps selectable via the tablet)? I'd love to click both the PULL IDENT and also the NAV 1 swtich on the audio panel myself, rather than having some "invisble" hand manipulating switches I never clicked. I love Black Square for the ultra realism, and the current solution, while understandable, does not match the level of detail of the rest of the systems. First, the PULL IDENT click does not physically pull that knob, I'd love to see the knob animated. And second, clicking a static (non-animated) knob even triggers a different switch to physically move is kind of immersion-killing (for me). Please, at least for the default units (GNS 530/430 and your own KNS81), rework this to make it more realistic so that the pilot needs to click the PULL IDENT as well as the appropriate switch on the audio panel, rather than the NAV 1 switch moving by itself. I hope it's something you can implement.

Yeah, I love these aircrafts Bonanza and Baron... but I hope one day we have a working visual beacon during daytime. It is possible on other aircraft it seems.

Hi Mark... Uninstalling and reinstalling worked... no message about out of date nav data... thanks, Rob

Thank you Mark.

Yeah I have them both off to avoid random crashes. But it still happened. Did another flight today and all was good.