@Black-Square Yeah everything is completely fine now. I just wanted to ask, even though it’s a bit of a different topic and I don’t want to create a new thread for it—I noticed that the aircraft is already a bit dirty by default, which is nice, but does it no longer get visually dirtier along the way?

Sound update - the quality of the sound of the Baron is MUCH better than the Duke IMO (piston duke). So good on the Baron that I taxi with the pilots window open to hear it better :).

I think that's exactly right. IIRC I got those SIMCONNECT Vars from within Developer Mode (Tools -> Behaviors) I think they are correct, since assigning button presses to them results the breaker tripping/resetting in the virtual cockpit. But in SPAD Data Monitor 'CIRCUIT CONNECTION ON:40' isn't changing state. Same for 41,42,43,44,45. I'll look at Dev Mode to see whether the Vars are changing state there.

@AlphaEcho You're more than welcome to join the server anyway. You don't have to be an RJ maniac. The topics will stay focused on the 146/RJ though.

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

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.