With my peripherals, my custom configuration profiles are nothing like the defaults.
I have set my “Single Engine Fixed Pitch” control profile for my Honeycomb Bravo as my default.
What I just noted is that when I entered a twin turboprop aircraft for the first time I needed to cycle through my control profiles to get to the “Twin Turboprop” profile I’d made. For reasons I don’t understand, when you click the right arrow to cycle to the next control profile, the default Asobo profile is the first one to be selected.
Switching profiles is a “hot” or “live” action where whatever is set in the profile you’ve just selected is going to have a potential effect on the state of the aircraft as it or any subsequent profile is selected – there isn’t a confirmation process required to have the profile affect the aircraft.
In my case, since my control profiles are so different to that of the default Asobo profile, a number of aircraft systems were altered due the switches on the Honeycomb being assigned settings that Asobo (or Honeycomb?) have set by default. This caused the aircraft’s electrical system to shutdown, and who knows what else to be changed.
Obviously(?), this isn’t going to be an issue on subsequent loads into the aircraft as my correctly selected profile is going to be retained for future use with the aircraft.
I’m bringing this up, because it is possible this is happening to people on first load of an aircraft without their realizing it and it could be leading to aircraft configuration/state issues that seem like bugs or some other oddity.
The easiest way to avoid this is to select a new aircraft (one you’ve not used before) from Free Flight, then go straight to Settings > Controls and select the peripheral profiles that you wish to use with that aircraft before you load into it on the apron/runway or in the air.
