August 6, 201114 yr Hi there, First time I tried to load the VFR flight-plan generated by PlanG v2.0.5.493 in .PLN format through ASE's Briefing page but upon loading the flight-plan, ASE shows departure and destination airports only, no user waypoints / intersections. Initially, PlanG saved waypoints in this format: <ATCWaypointType>User</ATCWaypointType>. When ASE didn't recognized it, I changed it to <ATCWaypointType>Intersection</ATCWaypointType>. But this didn't help either... Btw, I didn't have this issue with AS6.5. I'm putting the flight-plan below for review and will be grateful for your help! <?xml version="1.0" encoding="UTF-8"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>YSWL to YSWH</Title> <FPType>VFR</FPType> <CruisingAlt>5500</CruisingAlt> <DepartureID>YSWL</DepartureID> <DepartureLLA>S37° 4' 14.97",E142° 44' 27.53",+000803.00</DepartureLLA> <DestinationID>YSWH</DestinationID> <DestinationLLA>S35° 22' 33.00",E143° 31' 58.00",+000232.00</DestinationLLA> <Descr>YSWL, YSWH</Descr> <DeparturePosition>29</DeparturePosition> <DepartureName>Stawell</DepartureName> <DestinationName>Swan Hill</DestinationName> <AppVersion> <AppVersionMajor>10</AppVersionMajor> <AppVersionBuild>61472</AppVersionBuild> </AppVersion> <ATCWaypoint id="YSWL"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>S37° 4' 14.97",E142° 44' 27.53",+000803.00</WorldPosition> <ICAO> <ICAOIdent>YSWL</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="wpt06"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>S36° 56' 57.63",E142° 56' 17.91",+000000.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="wpt10"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>S36° 31' 24.85",E142° 57' 19.09",+000000.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="wpt8"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>S36° 22' 11.57",E142° 58' 43.75",+000000.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="wpt9"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>S35° 40' 51.61",E143° 21' 15.90",+000000.00</WorldPosition> </ATCWaypoint> <ATCWaypoint id="YSWH"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>S35° 22' 33.00",E143° 31' 58.00",+000232.00</WorldPosition> <ICAO> <ICAOIdent>YSWH</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan></SimBase.Document> Regards,Victor Quebec
August 6, 201114 yr Hi, Load the plan in FS and re-save it and then load it in ASE and see what happens.
August 6, 201114 yr Author Hello Jim, Thanks for very quick response but this didn't help, unfortunately! Btw, I also noticed that when I import the FSX-saved flightplan, ASE doesn't want to read cruise altitude data from the flightplan either. You can see below that Cruise Altitude still shows "zero" and I have to put it in manually. The other strange thing I cannot still comprehend is why "Waypoints" equals to "-1" (see: below). Can you explain that as well? I attach the image of what I get after flight-plan processing. Regards,Victor Quebec
August 6, 201114 yr Please send me the plan as an attachment in your regular e-mail: jim(AT)hifisim.com I would like to test it here.
August 7, 201114 yr Author Ok, it's strange but true! This is what I did while waiting for your test and response: 1. I made a similar flight-plan using FSCommander 9.0 and exported it to FSX. Loaded and worked ok under FSX!2. Then, I opened the same FP in ASE - again, worked as it should, i.e. existing (FS-native) and virtual waypoints displayed under Briefing page.3. I compared this newly made FP with original one created by PlanG and re-saved with FSX and noticed that the following section was missing in the latter: <ICAO> <ICAORegion>KK</ICAORegion> <ICAOIdent>Fix 01</ICAOIdent></ICAO> 4. I applied the above section for each waypoint in original flight-plan (just renaming the instances of Fix ##) and the problem now seems resolved - no more display issues under Brieifing page! Can you comment on this 'cuz it seems simply irrational to me WHY ASE experiences display issues only because a portion of flight-plan (evidently irrelevant to ASE) is missing? Thank you very much! Regards,Victor Quebec
August 7, 201114 yr Hi, Because without that section all the other waypoints were mis-numbered so ASE couldn't read the points from the plan.
Create an account or sign in to comment