Which file(s) needed for saving different FMGS states?

[Cheyenne Chief Pilot 829]

Hi devs and testers!

I've been pondering the idea of saving a variety of different FMGS states, corresponding with the different user-defined panel states. Question is, is it sufficient to take care of the UserSettings.FMS file, or do I have to deal with those *.LOG/*.CPY/*.TXT files, too?

My procedure would be something like this:

- Save the FSX flight situation (*.FLT, *.FSSAVE, *.WX, and, in my case, a *.RCD/RadarContactData file)

- Save the AAX panel state (*.ASC and UserSettings.FMS files, any others???)

(- * is a filename like DepArpt_DestArpt_AC_NmToDest.*, with the exception of the UserSettings.FMS file, which keeps being saved under this same name)

- Create a subfolder by the name of *

- Copy the UserSettings.FMS into the subfolder (withOUT renaming it!)

(- Saving done)

Reloading would be:

- Copy the UserSettings.FMS from the subfolder back to the main folder

- Load the FSX flight situation

- Load the AAX panel state (*.ASC file)

Is this procedure correct and are all necessary files covered appropriately?

Thanks!!!

[Cheyenne Chief Pilot 829]

Yep, it works, with only the UserSettings.FMS file backed up.

To complete the reloading procedure:

- Activate A/THR manually

- Set throttle(s) to CLB detent (if situation saved when A/C off the ground)

- Set TCAS mode according to flight phase

- Check TCAS tilt

(- Re-entering CRZ FL into MCDU may help, too, if not yet in DES phase, with managed speed issues in cruise, for example)

- Noticed in v1.15: 3 receivers are "stuck" after reloading the FMGS state - VOR1, VOR2, ILS - deleting all three 'manual' entries brings back the auto-tuning for all three of them

Not exactly PMDG-style, but I'm an even happier bunny now ...

EDIT:

Make sure, one checklist has been finished and the next one is "ready" - check the right MCDU, checklist section, before saving.

[Cheyenne Chief Pilot 829]

And, BTW, you have to delete all your older FMGS states with the v1.15 release, since v1.10 states are not compatible with (not recognized by) the v1.15 FMGS!!!