July 16, 201510 yr I've had a good old rummage around for an answer before posting so be gentle with me. Loading a flight plan into ASN (5665) results in only a partial display. I.E. LJPZ to LIPV via....screen shots do it better! This is my flight plan in Plan G. Duly exported to FSX format. Loading into ASN gives me this: I've poked and poggled but can't figure out why. Help appreciated. The World is divided into two groups. Those who say "Give me a link" and those that provide the link. WWG1WGA
July 18, 201510 yr Author OK, perhaps there's no point in loading a flight plan into ASN anyway. :rolleyes: Thanks for looking though. The World is divided into two groups. Those who say "Give me a link" and those that provide the link. WWG1WGA
July 18, 201510 yr can you post the .pln file? maybe there's something unusual in the formatting. presumably it loads all the points as expected in fsx? cheers -andy crosby
July 18, 201510 yr Author It loads perfectly in FSX. "Error You aren't permitted to upload this kind of file" Neither .pln nor .zip. I wonder what kind of file you can upload. Try THIS ONE Thanks for answering. The World is divided into two groups. Those who say "Give me a link" and those that provide the link. WWG1WGA
July 18, 201510 yr hi, it looks like all of the waypoints that are missing are marked as ATCWaypontType Airport the ones that show up are marked as User. i'm guessing that ASN only expects airport waypoints for the start and end of the plan so it gets confused and ignores the other ones. you can probably change the type to User for the other points and it would work by forcing it to interpret them as normal ones. in the text below i swapped them and stripped out the ICAOIdent fields for the intermediate waypoints as well. if you cut and paste this into a file i think it will work as you expect. you are also correct that it's probably not that critical to load a flight plan in this case. i don't know exactly what ASN does with the start and end weather..i know some of the options like ATC wind lock and area suppression could be influenced with that information, but typically that is more applicable to longer tubeliner flights. for a shorter VFR hop in a localized area the weather probably is not going to be much different between departure and arrival anyway.. anyway cheers! -andy crosby <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>LJPZ to LIPV</Title> <FPType>VFR</FPType> <CruisingAlt>13500</CruisingAlt> <DepartureID>LJPZ</DepartureID> <DepartureLLA>N45° 28' 37.91",E13° 36' 43.09",+000006.00</DepartureLLA> <DestinationID>LIPV</DestinationID> <DestinationLLA>N45° 25' 42.00",E12° 23' 17.00",+000009.00</DestinationLLA> <Descr>LJPZ, LIPV</Descr> <DeparturePosition>15</DeparturePosition> <DepartureName>Portoroz</DepartureName> <DestinationName>San Nicolo</DestinationName> <AppVersion> <AppVersionMajor>10</AppVersionMajor> <AppVersionBuild>61472</AppVersionBuild> </AppVersion> <ATCWaypoint id="LJPZ"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N45° 28' 37.91",E13° 36' 43.09",+000006.00</WorldPosition> <ICAO> <ICAOIdent>LJPZ</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="wpt01"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N45° 31' 49.45",E13° 33' 55.33",+000000.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="wpt02"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N45° 39' 08.81",E13° 46' 11.96",+000000.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="LIPQ"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N45° 49' 38.50",E13° 28' 19.18",+000036.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="wpt6"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 9' 53.47",E14° 34' 40.18",+000000.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="LJLJ"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 13' 28.16",E14° 27' 21.77",+001272.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="wpt04"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 22' 31.29",E14° 33' 49.50",+000000.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="wpt05"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 36' 52.36",E14° 29' 02.76",+000000.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="LOWK"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 38' 34.00",E14° 20' 14.00",+001469.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="LOWZ"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N47° 17' 34.00",E12° 47' 17.00",+002467.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="LIPB"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 27' 38.80",E11° 19' 35.30",+000787.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="LIDT"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N46° 1' 19.48",E11° 7' 31.91",+000606.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="LIDA"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N45° 53' 15.75",E11° 30' 59.35",+003408.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="LIPT"> <ATCWaypointType>User</ATCWaypointType> <WorldPosition>N45° 34' 18.00",E11° 31' 37.00",+000127.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="LIPV"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N45° 25' 42.00",E12° 23' 17.00",+000009.00</WorldPosition> <ICAO> <ICAOIdent>LIPV</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document>
July 18, 201510 yr Author Andy, I really appreciate your response. Something to live with I guess. I've just been informed on TeamSpeak that your answer is spot on. :smile: The World is divided into two groups. Those who say "Give me a link" and those that provide the link. WWG1WGA
Create an account or sign in to comment