Didn’t really find anything to switch between Modes via an external SimConnect Client. Did I overlook something?
I’d like to automate to step to get actually into the Cockpit.
(Why isn’t that a Setting - where to start the Free Flight - Aircraft vs Avatar? Why is everyone forced to start in that Mode?)
It seems that if you spawn at a gate, you start in Avatar mode whereas if you spawn on the runway, it goes directly in the cockpit.
As an aircraft developer, this is a bit confusing and we’d also like to give the user the option NOT to spawn in Avatar mode at the gate.
@FlyingRaccoon @Boris any suggestions / recommendations how this can be done?
Hello @simfan
I don’t think this is possible at the moment.
I’ll forward the idea but you should probably post on the forums and ask for a user setting.
Regards,
Sylvain
Hi @FlyingRaccoon -
glad to read your reply - thanks.
Would it also be possible to do this programmatically via SimConnect? (meant to say OR in the aircraft .cfg file) - edited.
That’s part of the discussion.
Can you elaborate on why you find this “confusing”?
Hi-
I am guessing it’s because there are not enough variables exposed to really know whether we’re in Avatar Mode so our code that checks if we’re past the “Ready To Fly” button then considers it needs to start initializing logic and several aircraft L: variables are not yet available in Avatar Mode for the aircraft, apparently (or we’re doing something wrong, which is always a strong possibility 
)
There are two Sim Variables to detect the Mode - “IS AVATAR” and “IS AIRCRAFT”. But they are totally useless to detect if the User is past “Ready to Fly” (respectively to detect if the Session is ready). They show both 1 and switch to 1 & 0 already while the Session is still loading / Ready to Fly not yet pressed.
I solved it by now to Focus the Simulator Window and send the Keystroke via the Windows API (since I have the “benefit” of having an external App). It is totally ugly, but the best Solution possible - given that Asobo forces a Feature on everyone without giving proper User-Options nor giving Developers any Means to workaround that.
Detecting Session Ready (“Ready to fly” pressed) via SimConnect is a Problem since 2020 - never addressed by Asobo. The 2024 Topic on this seems to go the same Route: Check if Session is running
To this Date, it is hard for me to fathom why Asobo does that by Force? Why can’t a User, not even a Developer, decide where to start? At least in Free Flight?
I really really love that this Mode was added. But getting it slapped into the Face, in every Session, is just a disgrace. (and don’t get me started on having Engines Covers on a big Airliner standing at the Gate).
The current State of its Implementation is contra productive to Immersion imho, not benefiting it.
Hi,
your workaround sounds smart, however it will break if the user assigns a different keystroke to the action, is that correct?
Correct!
Like I said, rather ugly as workaround ^^
That’s why at least a SimConnect Event / Call to change the Mode would be the Minimum that should be provided by Asobo.
(Or make it an User Option all together, so the User can decided and we all, including Asobo, just following the Users Preference)