Porthos 1 Posted August 17, 2020 Share Posted August 17, 2020 Hello all. Does anyone have any idea if/what the export format for the XPlane 11 default flight has been updated to the match XPlane 11 format? Reason I ask is some are having trouble getting the iniBuilds A300 to recognise the default XPlane /fms flight plans. A contributor has suggested the current PFPX might not be exporting the XPlane 11 files in the latest format. Any ideas? Link to comment Share on other sites More sharing options...
srcooke 422 Posted August 17, 2020 Share Posted August 17, 2020 There have been no changes made in PFPX, export has not been updated for XP11 Link to comment Share on other sites More sharing options...
Porthos 1 Posted August 18, 2020 Author Share Posted August 18, 2020 Thanks Stephen for the quick reply. Is there any intention so to do please as the new inbuilds A300 requires the latest XP 11.fms format to see the flight plans. Link to comment Share on other sites More sharing options...
DemonTraitor 3 Posted August 29, 2020 Share Posted August 29, 2020 Yes, this needs sorting. Really poor development team not keeping up with the times.... Link to comment Share on other sites More sharing options...
srcooke 422 Posted August 29, 2020 Share Posted August 29, 2020 My personal view is why do we persist with so many different route formats for addons .txt, .xml. .mdb, .db3, .sql, .pln, .fpl, .rte to name but a few and within those various route layouts and data Why are developers not simply using a common FAA/ICAO format in text ? Indeed there are a few that will uplift an OFP route directly. It is the addon developers that need to keep up with the times and have a common route format and common navigation database. Everyones life would be easier instead of reinventing the wheel 100's of times over. Link to comment Share on other sites More sharing options...
DemonTraitor 3 Posted August 29, 2020 Share Posted August 29, 2020 1 hour ago, srcooke said: My personal view is why do we persist with so many different route formats for addons .txt, .xml. .mdb, .db3, .sql, .pln, .fpl, .rte to name but a few and within those various route layouts and data Why are developers not simply using a common FAA/ICAO format in text ? Indeed there are a few that will uplift an OFP route directly. It is the addon developers that need to keep up with the times and have a common route format and common navigation database. Everyones life would be easier instead of reinventing the wheel 100's of times over. I am also thinking of the aircraft performance data for both PFPX and TOPCAT. When were thry last updated, for the Lancaster Bomber? lol Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.