Gentlemen

 

During the Tutorial #1 learning cycle for me, I, of course, utilized the Flight/Save function extensively so that I could repeat certain segments over and over without restarting the whole flight from scratch. Doing this I noticed that each time I would have to set the Land Alt back to "0", because it would default back to the "50" setting it has at the start of the Tutorial. I thought at first this was a "newbie oversight" error, but after deliberately setting it to "0" and immediately Flight/Saving, I ended the flight and exited FSX to desktop. I then restarted FSX to the default "trike" and loaded this newly saved Flight. After the 20 second panel restoration load, the Land Alt reverted back to the default "50" setting instead of the "0" setting that was just placed in it prior to saving. My apologies if this has already been reported. It's probably such a minor thing that it was not noticable before and if I hadn't been crosschecking between the Tutorial #1 PDF to check for newbie errors I probably would have missed it.

 

Regards

I have noticed this on my flights to EHAM and LTAI. LAND altitude changes from 0 to 50 and from 200 to 250 respectively.

In other airports everything is ok. Turn this selector on one position is not hard.

 

Maybe NGX knows wrong airport elevation, but I'm not sure.

Auto landing deployed speedbrakes are not being saved either.

 

I landed at EHAM, the first tutorial, departed the runway and stopped to save the flight. Upon reloading the flight (from a complete FSX restart, then Load from the "trike"), the flight loads up with the speedbrakes already stowed instead of where they were left prior to the save. To confirm this, I reflew the flight, landed again, checked the speedbrakes externally which were fully deployed, checked the speedbrake handle which was correct also, then saved. Reload the flight and nada.

 

This saved panel state feature is not as useful as it ought to be for mid-flight saves.

Guys, LAND ALT setting really is quite the non-critical item. No need to worry about that. Submit a ticket and chances are PMDG will repair it somewhere along the line.

 

And re Speedbrakes, I fail to see how that can be a problem. Besides, why even save just after you landed?

Guys, LAND ALT setting really is quite the non-critical item. No need to worry about that. Submit a ticket and chances are PMDG will repair it somewhere along the line.

 

And re Speedbrakes, I fail to see how that can be a problem. Besides, why even save just after you landed?

 

Since it might not be so obvious...

 

The most useful reason for saving flights and their quite useful accompanying and supposedly accurate panel states is for breaking down the flight into a more easily managed training segments.

 

Regards

 

 

Probably it might be nice to have a nap before starting to taxi. EHAM requires a loooong way to go before you may find an empty parking position. :rolleyes:

Honestly, I can understand Michael as I usually continue flying from the airport I landed before. Mid-flight saving seems not to be the real idea behind this feature 'cause it takes quite while before the plane even reacs properly after restoring and this might lead to trouble...

 

Regards,

Axel

The most useful reason for saving flights and their quite useful accompanying and supposedly accurate panel states is for breaking down the flight into a more easily managed training segments.

I understand that, and I understand you would want to save your flight for ex. on finals for touchdown training. But after landing, before at gate?

I understand that, and I understand you would want to save your flight for ex. on finals for touchdown training. But after landing, before at gate?

 

In the tutorial #1 flight: After you pull off the remote runway at EHAS, there's an "After Landing Procedure" to perform BEFORE taxiing a good mile+ to the gate. I'm breaking down the flight into the necessary segments for my own training purposes. My posted threads here are to point out to PMDG that there are some flaws in the saved flight/panel functions which are mostly of use for training replay purposes. If the flight/panel reloads incorrectly, it ruins the value of the training segment because you have to recheck "stuff" that shouldn't have changed. It's possible this is an FSX issue, but since PMDG is saving the panel states separately, I can't rule out that the issue lies with PMDG's panel save code.

Fair enough, it would never occur to me to consider after landing flow for saving and reloading.