Jarkko 39 Posted September 10, 2013 Share Posted September 10, 2013 PLEASE SEE POST #8 FOR THE CAUSE OF THE BUG! Hello, The route is as follows: GMAD ESS UG5 KORIS LXGB When I exported this to FSX using PFPX, I got a route that was about 5600nm long and bouncing north and south. The planned distance was ~460nm. Here is the generated file: <?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>GMAD to LXGB</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>38000</CruisingAlt> <DepartureID>GMAD</DepartureID> <DepartureLLA>N30° 19' 21.00",W009° 24' 41.00",253</DepartureLLA> <DestinationID>LXGB</DestinationID> <DestinationLLA>N36° 09' 04.19",W005° 20' 58.80",12</DestinationLLA> <Descr>GMAD to LXGB created by PFPX - Professional Flight Planner X (http://www.flightsimsoft.com/pfpx)</Descr> <DeparturePosition>10</DeparturePosition> <DepartureName>AGADIR/AL MASSIRA INTL</DepartureName> <DestinationName>GIBRALTAR</DestinationName> <AppVersion> <AppVersionMajor>10</AppVersionMajor> <AppVersionBuild>61472</AppVersionBuild> </AppVersion> <ATCWaypoint id="GMAD"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N30° 19' 21.00",W009° 24' 41.00",+000253.00</WorldPosition> <ICAO> <ICAOIdent>GMAD</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="ESS"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N31° 24' 04.48",W009° 41' 13.05",+000000.00</WorldPosition> <ICAO> <ICAOIdent>ESS</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="BARAM"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N32° 14' 49.00",W008° 53' 60.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>BARAM</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="RALEK"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N33° 00' 13.01",W008° 10' 46.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>RALEK</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="CBA"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N33° 31' 17.38",W007° 40' 37.87",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>CBA</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="TOLSI"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N34° 36' 02.00",W007° 00' 54.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>TOLSI</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="ROMSO"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N35° 26' 43.00",W006° 29' 33.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>ROMSO</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="KORIS"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N35° 49' 60.00",W006° 14' 21.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>KORIS</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LXGB"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N36° 09' 04.19",W005° 20' 58.80",+000012.00</WorldPosition> <ICAO> <ICAOIdent>LXGB</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan></SimBase.Document> When I exported the same route with Aivlasoft EFB, the route had the correct distance and waypoints: <?xml version="1.0" encoding="UTF-8"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>GMAD to LXGB</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>38000</CruisingAlt> <DepartureID>GMAD</DepartureID> <DepartureLLA>N30° 19' 30.00",W9° 24' 47.00",+000250.00</DepartureLLA> <DestinationID>LXGB</DestinationID> <DestinationLLA>N36° 9' 9.00",W5° 20' 54.00",+000015.00</DestinationLLA> <Descr>GMAD, LXGB</Descr> <DeparturePosition>10</DeparturePosition> <DepartureName>Al-Massira</DepartureName> <DestinationName>Gibraltar AB</DestinationName> <AppVersion> <AppVersionMajor>10</AppVersionMajor> <AppVersionBuild>61637</AppVersionBuild> </AppVersion> <ATCWaypoint id="GMAD"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N30° 19' 30.00",W9° 24' 47.00",+000250.00</WorldPosition> <ICAO> <ICAOIdent>GMAD</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="ESS"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N31° 24' 4.50",W9° 41' 13.10",+000000.00</WorldPosition> <ICAO> <ICAORegion>GM</ICAORegion> <ICAOIdent>ESS</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="BARAM"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N32° 14' 49.00",W8° 54' 0.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>BARAM</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="RALEK"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N33° 0' 13.00",W8° 10' 46.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>RALEK</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="CBA"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N33° 31' 17.40",W7° 40' 37.90",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAORegion>GM</ICAORegion> <ICAOIdent>CBA</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="TOLSI"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N34° 36' 2.00",W7° 0' 54.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>TOLSI</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="ROMSO"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N35° 26' 43.00",W6° 29' 33.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>ROMSO</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="KORIS"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N35° 50' 0.00",W6° 14' 21.00",+000000.00</WorldPosition> <ATCAirway>UG5</ATCAirway> <ICAO> <ICAOIdent>KORIS</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="LXGB"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N36° 9' 9.00",W5° 20' 54.00",+000015.00</WorldPosition> <ICAO> <ICAOIdent>LXGB</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan></SimBase.Document> Link to comment Share on other sites More sharing options...
Jarkko 39 Posted September 10, 2013 Author Share Posted September 10, 2013 Here are the screenshot how FSX reads them. First PFPX: Then EFB: Link to comment Share on other sites More sharing options...
Jarkko 39 Posted September 11, 2013 Author Share Posted September 11, 2013 Have you had time to look at this one? For me, this is a major problem, because VoxATC uses the PFPX generated flight plan. Link to comment Share on other sites More sharing options...
Jarkko 39 Posted September 11, 2013 Author Share Posted September 11, 2013 Todays route exported with PFPX: EDBC KENIG UZ716 GALMA UM736 BZO UM984 EVANO UZ185 BORDI LFMN Link to comment Share on other sites More sharing options...
Jarkko 39 Posted September 11, 2013 Author Share Posted September 11, 2013 Forgot to mention that the above route looked "normal" in PFPX, but once exported out of PFPX to FSX, something weird happens. Link to comment Share on other sites More sharing options...
Jarkko 39 Posted September 12, 2013 Author Share Posted September 12, 2013 Bump Link to comment Share on other sites More sharing options...
HercMighty 0 Posted September 13, 2013 Share Posted September 13, 2013 I saw the same thing using the PMDG 777 tutorial from VRMM to OMDB. Was going to try and use ATC in FSX (switched to a third party since) but when I tried to import the FSX Exported Flight Plan from PFPX I saw much the same issue you have here. Link to comment Share on other sites More sharing options...
Jarkko 39 Posted September 13, 2013 Author Share Posted September 13, 2013 CAUSE: OK, I found the problem and a way to fix it in PFPX! FSX and other programs do not like the way that PFPX generates the minutes and seconds in the coordinates. Extracted from the first post, notice how the coordinates are formed for waypoint BARAM: <WorldPosition>N32° 14' 49.00",W008° 53' 60.00",+000000.00</WorldPosition> Notice the 53 minutes and 60 seconds. It should be 54 minutes and 0 seconds. --- Same thing with waypoint KORIS: <WorldPosition>N35° 49' 60.00",W006° 14' 21.00",+000000.00</WorldPosition> Notice the 49 minutes and 60 seconds. It should be 50 minutes and 0 seconds. If I manually fix these errors in the PFPX generated FSX flight plan, all is well. Can we please have a fix for this? Thanks! Link to comment Share on other sites More sharing options...
HercMighty 0 Posted September 13, 2013 Share Posted September 13, 2013 Good Catch +1 Link to comment Share on other sites More sharing options...
marcon8122 58 Posted September 14, 2013 Share Posted September 14, 2013 The problem is that fsx have old VOR and waipoint database try this to avoid some errors http://www.aero.sors.fr/navaids3.html is free and easy to use and you can came back from change Link to comment Share on other sites More sharing options...
Jarkko 39 Posted September 14, 2013 Author Share Posted September 14, 2013 Nope, this isn't a problem with FSX. I explained the reason couple of posts up. FSX doesn't "use" the waypoint names in the flight plan to construct the route. Only coordinates matter in this case. The names are there only for display purposes. I could name all waypoints Foo1, Foo2 and so on. All that matters for FSX, is what coordinates I set to these waypoints. It seems to me, that when PFPX sets the seconds to full 60.0", FSX just cuts off the seconds part and pretends that it was 0.00" (and doesn't incrementing the minutes part by one). This is why you get those weird routes with the PFPX exported flight plans. Link to comment Share on other sites More sharing options...
FlightSimSoft.com 283 Posted September 14, 2013 Share Posted September 14, 2013 Thanks for the detailed report. Fixed in 1.07 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.