Max_D

Good reminder thanks Alex, I know I normally use the drop down box selection at the top on the world map screen, but in my testing I may have used the runway selector on the zoomed in map view on occasion as well (can't recall right now).

Yes I found it a bit hit and miss when it came to the sim ignoring my departure runway from LNM. I wasn't sure if the sim automatically suggested the best runway based on wind direction at the time (more testing required to confirm if this is the case). I also found that when the flight path (from departure airport to the approach procedure) was missing, I could manually program my departing runway into the G1000 (took a bit of fiddling!), but then it joined the approach leg in the G1000 map.

Thanks again for looking into this Alex. At least you got the planning screen to show the correct departure runway. What method did you use in LNM to specify your departure runway (was it the little green 'select a start position' button)? Like I say it only takes a minute to define the correct approach in the G1000 prior to take off, then the duplicate departure paths go away and you get your nice single GPS path. Cheers, Matt

Apologies - flight plan was meant to be inserted using the 'code' function: <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>YBBN to YBSU</Title> <FPType>IFR</FPType> <RouteType>LowAlt</RouteType> <CruisingAlt>4000</CruisingAlt> <DepartureID>YBBN</DepartureID> <DepartureLLA>S27* 22' 58.54",E153* 6' 24.85",+000013.00</DepartureLLA> <DestinationID>YBSU</DestinationID> <DestinationLLA>S26* 36' 12.00",E153* 5' 27.94",+000015.00</DestinationLLA> <Descr>YBBN, YBSU created by Little Navmap 3.0.5</Descr> <DeparturePosition>1L</DeparturePosition> <DepartureName>Brisbane Intl</DepartureName> <DestinationName>Maroochydore/Sunshine Coast</DestinationName> <AppVersion> <AppVersionMajor>11</AppVersionMajor> <AppVersionBuild>282174</AppVersionBuild> </AppVersion> <ATCWaypoint id="YBBN"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>S27* 23' 2.79",E153* 7' 3.19",+000013.00</WorldPosition> <ICAO> <ICAOIdent>YBBN</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="RW01L3"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>S27* 20' 18.59",E153* 7' 56.70",+000966.57</WorldPosition> <ICAO> <ICAOIdent>RW01L3</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="YBSU"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>S26* 36' 12.00",E153* 5' 27.94",+000015.00</WorldPosition> <SuffixFP>Y</SuffixFP> <ApproachTypeFP>RNAV</ApproachTypeFP> <RunwayNumberFP>31</RunwayNumberFP> <ICAO> <ICAOIdent>YBSU</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document>

Thanks Alex, I appreciate your reply. It's such a privilege to speak with the actual developer of this awesome program 🙂 I've continued testing the same flight plan in several configurations: 1. Inserting the departure runway in LNM and exporting (with runway set). 2. Only having the departure set from the airport (and using that 'start position' function to set runway / parking spot. 3. Only having departure set from airport, but manually adding waypoints (route change) to the runway I want and another 3 miles out in runway direction. The results are either two paths ('V' shaped) from the airport, or no path from the airport and the GPS path only starts at the iaf (first point in my approach). Image captures: https://imgur.com/a/UohFLeH Example flight plan: <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>YBBN to YBSU</Title> <FPType>IFR</FPType> <RouteType>LowAlt</RouteType> <CruisingAlt>4000</CruisingAlt> <DepartureID>YBBN</DepartureID> <DepartureLLA>S27* 22' 58.54",E153* 6' 24.85",+000013.00</DepartureLLA> <DestinationID>YBSU</DestinationID> <DestinationLLA>S26* 36' 12.00",E153* 5' 27.94",+000015.00</DestinationLLA> <Descr>YBBN, YBSU created by Little Navmap 3.0.5</Descr> <DeparturePosition>1L</DeparturePosition> <DepartureName>Brisbane Intl</DepartureName> <DestinationName>Maroochydore/Sunshine Coast</DestinationName> <AppVersion> <AppVersionMajor>11</AppVersionMajor> <AppVersionBuild>282174</AppVersionBuild> </AppVersion> <ATCWaypoint id="YBBN"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>S27* 23' 2.79",E153* 7' 3.19",+000013.00</WorldPosition> <ICAO> <ICAOIdent>YBBN</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="RW01L3"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>S27* 20' 18.59",E153* 7' 56.70",+000966.57</WorldPosition> <ICAO> <ICAOIdent>RW01L3</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="YBSU"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>S26* 36' 12.00",E153* 5' 27.94",+000015.00</WorldPosition> <SuffixFP>Y</SuffixFP> <ApproachTypeFP>RNAV</ApproachTypeFP> <RunwayNumberFP>31</RunwayNumberFP> <ICAO> <ICAOIdent>YBSU</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document> For now, I've worked out the easiest method is to include the runway in the LNP export (even though MSFS changes this to another departing runway facing the wrong way!), then manually change your starting runway in the SIM, then if you get the dual paths on the G1000, just go into PROCEDURES and SELECT APPROACH, LOAD APPROACH, it makes the dual path lines from the airport disappear and it follows the single GPS path to the IAF transition perfectly (and continues down the glidepath to the runway thanks to VNAV). Thanks, Matt Dual paths : Manually set waypoint on runway - still dual paths: No path to IAF (GPS path only starts at the beginning of the approach): The result of dual paths means the AP keeps flying 'over' the iaf and fails to turn left to commence the RNAV approach procedure (*note the small pink line on the flight plan page below):

I'm testing the export to FS2020 option and finding mixed results with the G1000 (in the 172) for the departure. FS2020 World Map screen (after import) often changes the runways (sometimes for arrival as well as departures), and other times you end up with a 'V' pattern on your GPS departure before they merge at a later point. So basically if I want to start ready to go on a runway (in the Sim), should I NOT select a starting runway in LNM (only a departure airport), then in the export options, ONLY click save (ie. don't select a starting point in that LNM export dialogue box), then when I load up the SIM, the G1000 shouldn't be confused with multiple paths from the airport departure area? I'm trying to nail down a repeatable procedure for having IFR flight plans that I've prepared in LNM, then export to MSFS, where both the Sim and the G1000 closely match what I planned in LNM. So far...the results are all over the place. Sounds like the best way so far is (as stated above) - remove the departure details, then export, then re-add them back in?