Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Serge75

  1. No worries. Good to hear it's working for you. Cheers, Serge
  2. I haven't come across this error before so not sure what's gone wrong to be honest. Have you run the spreadsheet and exported the routes with success previously? What's the Output tab on the spreadsheet look like? Similar to this below?
  3. No worries. Great to hear it's working again for you.
  4. I really should update the spreadsheet to put a check in for the quotes and to remove them if found.
  5. I just download the latest prefroutes_db.csv file to check and found it contains quotes (check it in a text editor, not excel). Using this file as is will cause the error you encountered. Once I removed the quotes using a text editor the spreadsheet worked. Regards, Serge
  6. Can you check the downloaded prefroutes_db.csv file. On very rare occasions the FAA prefroutes_db.csv file includes quotes in each route. Not sure why this happens. This will cause an error similar to what you are encountering. If this is the case, an easy fix is to open the downloaded prefroutes_db.csv file in a text editor and use the find & replace function to remove the quotes. You can then use the fixed file in the spreadsheet. Regards, Serge
  7. I knocked those spreadsheets up a few years back now. PM me your idea and I can have a look. Be warned though, I'm certainly no expert at this, really only got this done by googling along with plenty of trial and error. Regards, Serge
  8. Thanks for the tip. Only doing short haul/regional flights at the moment so no need for ETOPS however losing the TOC/TOD would be a minor inconvenience. Regards, Serge
  9. Sorry, not related to North Atlantic Tracks but to NATS UK. It's a spreadsheet that converts standard routes from a XLS file downloadable from the NATS UK website and converts them into routes PFPX can import. There is also a similar one for FAA standard routes. You can grab the spreadsheets from here if still interested: PFPX Route Translator Spreadsheets - PFPX - AEROSOFT COMMUNITY SERVICES Regards, Serge
  10. I was just playing around with a few options to see if it could be disabled but you've just confirmed my suspicion. It's also great to hear those spreadsheets are still useful. Thanks again for your assistance. Cheers, Serge
  11. Thanks for the prompt response Stephen. Is this something new with v2? It's great to still see you around here helping out. I'm only just getting back in it again with MSFS after an absence of around 2 years so I only recently upgraded to v2.04 after using v1.28 and don't recall seeing this previously. Also just gave my NATS spreadsheet a run and surprised it still works. Regards, Serge
  12. Hi all, I'm currently running v2.04 of PFPX and notice I get extra airports included in the OFP Navlog. In the attached OFP extract my planned route is as follows: YCAR CAR B469 TOPIR L514 REVOP Q38 JULIM JULI5A YPPH You will notice YCUN included before and after the TOC along with YPPH after the TOC. Does anyone know what is causing this? This issue happens in any flight plan I create. The errant airports change to suit the locale of the flight plan. Regards, Serge
  13. Version 1.3


    PFPX Route Translator Spreasheets for NATS UK routes, FAA USA routes and DECEA Brazil Routes. These spreadsheets enable you to translate the route files downloaded from NATS (XLS file), the FAA (CSV file) and DECEA Brazil (CSV file) into a file suitable for import into PFPX. Instructions are contained in the spreadsheets. These spreadsheets were created with Excel 2016 but should still work with earlier versions such as 2013 and 2010. Macros need to be enabled for these to function.
  14. G'day Jon, Thanks very much for that. Much appreciated. You must have some good contacts mate. Data for the JS41 is impossible to find. Cheers, Serge
  15. Hi Jon, Thanks very much for these performance files, particularly for the JS41 which has been sort after by many for a long time. So far flying with the PMDG JS41 I find the fuel calcs to be pretty close to my actual values in flight so job well done with this. I do have one small request though with the JS41 performance file. As we can't edit these ourselves would it be possible for you to change the engine value from "ALLIED SIGNAL TPE331-14 (1500SHP)" to just "TPE331-14". This will bring the formatting inline with most other aircraft however the main reason though is to help with the OFP output as a long engine value throws out the formatting for a few templates I use. This is an extremely minor issue however it would be appreciated if you considered it. Regards, Serge
  16. Version 2.0


    PFPX routes for the UK and Ireland. Routes have been derived from the NATS UK & Ireland Standard Route Document. This document can be found online here: http://www.nats-uk.ead-it.com/public/index.php%3Foption=com_content&task=blogcategory&id=186&Itemid=258.html STAR’s (where applicable) and Flight Level restrictions for the route have been added to the remarks section of each route. How to install: Download the file. Open PFPX --> Route Database. If you have a previous version installed, type NATS in the remarks field of the filter (all the previous NATS routes should be selected), then click delete. Click on "Import" then select the downloaded file. In the Route Import window choose the “Overwrite existing routes” option, ensure the “Include Route Remarks” option is checked and then click “Apply” to import the routes. Please note that importing the NATS Routes may take a few minutes as there are over 6000 routes! Also, you may need to restart PFPX for the route database to update correctly after the import process has completed. If you wish to convert the routes yourself, including the ability to create sub-routes, then you can you the PFPX Route Translator Spreadsheet available here: http://forum.aerosoft.com/index.php?/files/file/4109-pfpx-route-translator-spreadsheets/
  • Create New...