I'm trying to figure out the logic of the G1000.  If I pull up a landing procedure and select load, I expect it to load only.  Instead the plane veers off toward a transition point that wasn't intended.  If I select activate then it should go directly to the IAF, correct?  Any advice is appreciated.  

52 minutes ago, curt1 said:

I'm trying to figure out the logic of the G1000.  If I pull up a landing procedure and select load, I expect it to load only.  Instead the plane veers off toward a transition point that wasn't intended.  If I select activate then it should go directly to the IAF, correct?  Any advice is appreciated.  

Would help to provide more detail.  There are known issues with the MSFS Garmin glass panels.  Some have been corrected with freeware modifications that are placed into the MSFS Community folder.  Other issues are more inherent in the simulation itself. 

Would help if you provide some information about your route, the approach procedure you chose, and your location when you activated the approach.  I personally have not had any strange behavior with loading an approach.  Only with activating the approach.  The issue has been discussed many times in related topics here.  If you do not have the G1000 mod from Working Title in place in Community, then you must activate the approach before reaching the last waypoint in your flight plan that precedes the IAF.   So say the flight plan is:

 ................CID V503 RST V82 FGT KSTP

and you want to fly the RNAV (GPS) RWY 32 approach into KSTP.  The IAF from the direction of FGT is LDASH.  To get the unmodded MSFS G1000 to behave you must Activate the approach before reaching FGT.  Not right in the real world, but that is the way it is in the sim.  If you wait until after FGT to activate, the default G1000 will turn you around and fly you back to FGT, and amazingly will continue to fly your flight plan in reverse from there.  The Working Title G1000 mod fixes that.

https://www.avsim.com/forums/topic/587196-doing-a-u-turn-after-loading-an-approach/?tab=comments#comment-4379145

Edited November 5, 20205 yr by fppilot

1 hour ago, curt1 said:

I'm trying to figure out the logic of the G1000.  If I pull up a landing procedure and select load, I expect it to load only.  Instead the plane veers off toward a transition point that wasn't intended.  If I select activate then it should go directly to the IAF, correct?  Any advice is appreciated.  

Put your/the IAF or FAF in the FP as final waypoint sequenced before the APPR

3 hours ago, fppilot said:

Would help to provide more detail.  There are known issues with the MSFS Garmin glass panels.  Some have been corrected with freeware modifications that are placed into the MSFS Community folder.  Other issues are more inherent in the simulation itself. 

Would help if you provide some information about your route, the approach procedure you chose, and your location when you activated the approach.  I personally have not had any strange behavior with loading an approach.  Only with activating the approach.  The issue has been discussed many times in related topics here.  If you do not have the G1000 mod from Working Title in place in Community, then you must activate the approach before reaching the last waypoint in your flight plan that precedes the IAF.   So say the flight plan is:

 ................CID V503 RST V82 FGT KSTP

and you want to fly the RNAV (GPS) RWY 32 approach into KSTP.  The IAF from the direction of FGT is LDASH.  To get the unmodded MSFS G1000 to behave you must Activate the approach before reaching FGT.  Not right in the real world, but that is the way it is in the sim.  If you wait until after FGT to activate, the default G1000 will turn you around and fly you back to FGT, and amazingly will continue to fly your flight plan in reverse from there.  The Working Title G1000 mod fixes that.

https://www.avsim.com/forums/topic/587196-doing-a-u-turn-after-loading-an-approach/?tab=comments#comment-4379145

Thank you for the feedback.  Frank, I am using the G1000 mod, I should have mentioned that earlier.  Many of my flights are direct-to, such as KPIA to KSTL.  If I select an approach and with the cursor select "load", I expect the approach to be loaded but the plane stay on course direct to KSTL.  What happens with me is when I select "load" the plane changes course as if I had selected "activate".  That is not what happens in P3D with my GTN units, and the behavior with the G1000 seems illogical.

 

EDIT:  To clarify further, I just set up a quick flight from KBMI D-TO KPIA.  I tested using the ILS 31 approach and applied "load".  The GPS changed to the transition waypoint MACIN.  I then started again this same flight but instead of selecting "load", I selected "activate".  I got the exact same result, next waypoint is MACIN again.  My understanding is "load" is to make it available to use when assigned an approach by ATC, but the sim treats "load" and "activate" as the same thing.  Feel free to enlighten me if I've got it wrong, but this appears to be a major bug with the Garmin.  

Edited November 5, 20205 yr by curt1
added more data

1 hour ago, curt1 said:

EDIT:  To clarify further, I just set up a quick flight from KBMI D-TO KPIA.  I tested using the ILS 31 approach and applied "load".  The GPS changed to the transition waypoint MACIN.  I then started again this same flight but instead of selecting "load", I selected "activate".  I got the exact same result, next waypoint is MACIN again.  My understanding is "load" is to make it available to use when assigned an approach by ATC, but the sim treats "load" and "activate" as the same thing.  Feel free to enlighten me if I've got it wrong, but this appears to be a major bug with the Garmin.  

You have picked a very short route.  The auto insert of MACIN may be based on a logic rule either in the sim, or in the Garmin logic.  Try a different flight, one a bit longer, and stick in at least one waypoint between the two airports. You can do it in MSFS on the World screen where you set up the flight.  Seems like it ought to be able to do what you wish, but in some cases Garmin has built rules into the logic.  In other cases Asabo (MSFS) has "wired" so to speak what happens. 

Plan a flight from Bloomington to Moline, with an interim waypoint of PIA (the VOR).  Then try loading an approach again.

1 hour ago, curt1 said:

Thank you for the feedback.  Frank, I am using the G1000 mod, I should have mentioned that earlier.  Many of my flights are direct-to, such as KPIA to KSTL.  If I select an approach and with the cursor select "load", I expect the approach to be loaded but the plane stay on course direct to KSTL.  What happens with me is when I select "load" the plane changes course as if I had selected "activate".  That is not what happens in P3D with my GTN units, and the behavior with the G1000 seems illogical.

 

EDIT:  To clarify further, I just set up a quick flight from KBMI D-TO KPIA.  I tested using the ILS 31 approach and applied "load".  The GPS changed to the transition waypoint MACIN.  I then started again this same flight but instead of selecting "load", I selected "activate".  I got the exact same result, next waypoint is MACIN again.  My understanding is "load" is to make it available to use when assigned an approach by ATC, but the sim treats "load" and "activate" as the same thing.  Feel free to enlighten me if I've got it wrong, but this appears to be a major bug with the Garmin.  

 

I have noticed the same thing, I think it's a bug. When we press load it shouldn't activate. It is doing the same thing if we press load or if we press activate, which it shouldn't. I'm also using the G1000 mod, didn't try without it.

3 hours ago, fppilot said:

You have picked a very short route.  The auto insert of MACIN may be based on a logic rule either in the sim, or in the Garmin logic.  Try a different flight, one a bit longer, and stick in at least one waypoint between the two airports. You can do it in MSFS on the World screen where you set up the flight.  Seems like it ought to be able to do what you wish, but in some cases Garmin has built rules into the logic.  In other cases Asabo (MSFS) has "wired" so to speak what happens. 

Plan a flight from Bloomington to Moline, with an interim waypoint of PIA (the VOR).  Then try loading an approach again.

Frank, I followed your advice and set up a longer route.  It behaved as I would expect it to by loading the procedure without activating it...so thank you for pointing this out.  I do a lot of flights in the 80-100 mile range due to time restrictions and the Garmin must have a different logic when handling those shorter flights, or a different logic on D-TO flights without a middle waypoint.  In any case,  I'm no longer bewildered about it and I thank you for your help today!

26 minutes ago, curt1 said:

Frank, I followed your advice and set up a longer route.  It behaved as I would expect it to by loading the procedure without activating it...so thank you for pointing this out.  I do a lot of flights in the 80-100 mile range due to time restrictions and the Garmin must have a different logic when handling those shorter flights, or a different logic on D-TO flights without a middle waypoint.  In any case,  I'm no longer bewildered about it and I thank you for your help today!

I have a good deal of real world experience with the Garmin GNS and GTN series GPS models.  In regard to the behavior in MSFS with the G1000 and G3000, I believe that what we are dealing with is coding and logic within MSFS as the Garmin logic as I have been informed is literally the same.  In MSFS there have been issues with selecting and following an approach as well as using the [D→] function. 

I believe also at play in MSFS is what occurs when activating an upstream flight plan leg.  This is difficult to explain.  For instance. In your flight plan there is a 20° turn after the next waypoint.  In real life you request a Direct To the fix that comes after that turn, or better yet, activate the flight plan segment from that waypoint to the one that follows it.  In essence cutting off the dogleg.  If you do that in MSFS I believe it does not turn you direct to that waypoint from where you are at the time.  Instead I believe it turns you to intercept a line from the previous waypoint in your flight plan to that  upstream waypoint you selected.  i.e from a waypoint that is behind you.  That can result in a strange series of turns until it intercepts that line.  The larger the dogleg, the more unusual the response from the G1000.

By the way.  You are flying out of the wrong Bloomington.....  You need to try the Bloomington one state east of where you are at.

Indiana Hoosier here...

Edited November 6, 20205 yr by fppilot