From another post: If no baro-altitude data is supplied, altitude leg types must be manually sequenced;

Using the sim, I'm doing the LNAV 34 to L45.  Crossing the FAF I enable the miss so when I reach the MAP, I'm expecting the sim to climb to 1200 ft before either turning on it's own assuming the sim has baro-altitude information, or requiring me to manually sequence this leg.

Nieither happens, the sim doesn't wait until 1200 ft, it usually starts turning somewhere around 950 ft.

What should I expect to see?  Will a LSK option show on the FMS page that says activate leg similar to enable missed or do I have to scroll in the flight plan, select the leg, then hit activate leg?  It would be nice if would be automatic like enable the miss.  As with the enable miss that I've mentioned previously, I'd recommend adding this prompt to the MAP page as well so you don't have to switch pages to enable the missed or activate the altitude legs.

The manual activation of a leg is prompted by a blue CAS message in the bottom right corner of the display.  I've added some content to the Rel 10.1 Pilot Guide that adds some text and pictures and can post that in a week or three.

BTW, one change we've also made in Rel 10.1 is an option to automatically have the missed approach get enabled, thereby removing the need to manually command that on every approach.

Interesting. You threw in some logic, like aircraft past the MAP, aircraft climbing, etc., to auto-activate it?

* Orest

This isn't to identify or fly the missed.  When you load an approach, the missed is automatically loaded, but it is not enabled.  If you flew past the missed, it would not sequence the flight plan.  Between the FAF and the MAP, you can go to the FMS page and select the "Enable Missed" LSK that says that you want to sequence the flight plan past the MAP.  I suggest putting this prompt on the MAP page as well so you don't have to remember to switch pages to enable the missed.

It looks like the way they are going to go is to add an option that allows the user to maintain the current behavior or to have it always automatically enable the missed.

Yes, I remember that conversation.

But you wouldn't want to have the missed sequencing if you land, hence my question if there was something that would hold back the missed auto-sequencing, if it were set to do so.

* Orest

Perhaps it should be GO MISSED instead of enable missed.