Auto select of A/C

Hi, THanks for reporting that. Let me quickly check, should be easy to reproduce. Hang on.

BrianS wrote: This doesn't seem to work, I seem to always get the last profile I used.

Question -> are you using profiles you saved before v1.1.1 released? There have been some schema changes. You can upload the profile from the app if you like, I can take a look at it. Just press the share button in your profiles section.

Try this build https://ffb-bridge.com/dl/diag/cTRnv0jCUz9ApRCVdAju5I8OYxthBR_tk0Kvx2w_nEo

It's limited to 50 downloads and three days, if anyone needs more let me know.

If this is confirmed working, I'll include it in an upcoming hotfix (this week).

Yep, the profiles were pre 1.1.1, look it's not a big deal, I'll delete them and re do them in 1.1.1

I haven't been able to do much for a couple of days but will report back.

No worries. The app should auto-migrate, that's a real bug, You shouldn't have to delete and recreate. Give the hotfix a shot and let me know if that solves it without you deleting it.

OK I did a quick check and , with the original 'piper' profile I changed it to the Kodiak 100 cargo OK BUT when I exit the sim the profile is showing Piper as selected (ie use this profile).

That's after putting in the patch above.

Is ther are way to post a picture here? Can't see how so will send it to you via the report page on the app.

I think I have it fixed., Let me include this in an upcoming hot fix.

OK I just copied my piper profile and deleted the old one and same for Kodiak and now they stay as they should ie select Kodiak and stays kodiak. So I'd say you have fixed it and maybe something strange with the older profile json file or if they are exact copies of the originals it all seems ok now with the hotfix. So if the files are the same maybe needed a re boot or something to get it working.

BrianS wrote: OK I just copied my piper profile and deleted the old one and same for Kodiak and now they stay as they should ie select Kodiak and stays kodiak. So I'd say you have fixed it and maybe something strange with the older profile json file or if they are exact copies of the originals...

Good to know. Yes, it's happening because the profile schema changed over the beta period, but going forward it will not happen again.