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.

Out of Las Vegas on the way to Jackson Hole [image: 9c8fb7c9-01eb-46b1-bdca-02b764a0771f.jpg] And a different sort of screenshot, I knew I was flying the Starship quite a bit since it's been out, but I didn't think it'd be at the top of my list for the year in Volanta [image: c985b3e8-37d5-45de-be9f-87ffe58975c6.png]

@SadBucket I can check the MSFS 2024 menu later, but the event you're looking for is called "pitch leveler". The lack of mode change with CWS is because there is no way for me to detect CWS mode in MSFS. That's also why a CWS annunciator does not appear on my other aircraft if you bind with the native "pitch sync" event instead of using one of my L:Vars. It's just a simple oversight, probably going back 20-30 years in MS Flight Sim. The same is true of go-around mode, but there I can do a process of elimination, at least.

@Moonflower_414 Thank you very much for sharing this workaround, I really appreciate you taking the time to explain it. I’ll give it a try and report back if it works for me. Thanks again!

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

So glad that was it! I really wasn't thinking about that at all until I watched your video. I may have never thought of it without your video, in fact. The brain responds to the smallest visual stimulus. Let me know if you have any other questions!

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