1 hour ago, jrw4 said:

These videos pertain to the real world G1000 and there are 17(!) of them, but they give a really good idea of how these devices are actually used. I got the strong impression that the correct sequence for approaches was to load first, confirm that the correct approach was displayed on the MFD, and then activate when cleared for the approach.

Thank you!  These are excellent videos and I agree with your sequence above... 🙂

1 hour ago, Bert Pieke said:

Previously, the approach would get sequenced before the destination airport, but I am now getting situations where there is a discontinuity in the flightplan, because the approach is sequenced after the destination airport which means that a waypoint needs to be manually deleted from the flightplan, or a DTO to the IAF, or the approach activated before it can be flown.

So, this is really as intended. The theory goes that when you add an approach, it shouldn't change your routing without some additional intervention. If, for example, you were on an IFR flight plan, the approach is not included in the plan. Unless an arrival procedure is part of the plan, or the clearance you receive, the clearance limit for your plan is the destination airport. When you add an approach you don't want to actually fly from your last enroute waypoint to the IAF of the approach you loaded until you've been cleared to do so, or more likely, you're vectored there. As a result, Garmin has determined that in their logic, they don't want to change the plan unless the pilot proactively does that, either by going direct to the IAF (activating the approach) or by consciously deleting the destination airport from the enroute flight plan. This is why, when you add an approach, in most circumstances, it will add the destination airport at the end of the enroute segment. This won't happen if there's an arrival procedure loaded. It also shouldn't happen if there was not previously a destination loaded...but that is logic that, I don't think, made it into this build. It is in the next build, however.

Anyhow, here's a couple quick snaps of what happens when you are on KSBS-KHDN and add an approach (in this case ILS10 via REVME).

1 hour ago, cwburnett said:

The theory goes that when you add an approach, it shouldn't change your routing without some additional intervention. If, for example, you were on an IFR flight plan, the approach is not included in the plan.

I am learning something new here.. actually makes sense 🙂

Thank you!

ps... Can you change the RNAV1L listing to RNAV01L at some point..? 😉

Edited September 14, 20214 yr by Bert Pieke

3 hours ago, cwburnett said:

Anyhow, here's a couple quick snaps of what happens when you are on KSBS-KHDN and add an approach (in this case ILS10 via REVME).

Too late to edit it, but a third snap would have been valuable showing how it appears once the approach is activated.  Snap two only shows it loaded.

With regard to the soft keys associated with VNAV in that second picture, how do I get those to appear? I was trying to enter a "cross XXXXX at 12000" into the flight plan the other day and couldn't figure out how to do it.

Thanks.

1 hour ago, fppilot said:

Too late to edit it, but a third snap would have been valuable showing how it appears once the approach is activated.  Snap two only shows it loaded.

40 minutes ago, jrw4 said:

With regard to the soft keys associated with VNAV in that second picture, how do I get those to appear? I was trying to enter a "cross XXXXX at 12000" into the flight plan the other day and couldn't figure out how to do it.

Thanks.

not implemented yet.

No problem. It's going to be an outstanding contribution to the MSFS community, and it's great to have a chance to work with it now.