Jump to content

srcooke

Members
  • Posts

    3384
  • Joined

  • Days Won

    4

srcooke last won the day on March 29 2020

srcooke had the most liked content!

2 Followers

About srcooke

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

srcooke's Achievements

Collaborator

Collaborator (7/14)

  • Reacting Well Rare
  • Very Popular Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

394

Reputation

  1. Look forward to an explanation as PFPX is still sold albeit no longer via Aerosoft as a publisher.
  2. Hello Amir, There is a post in the Navdata section of this forum which has not yet been clearly answered as to whether the missing data is an error. I cannot see any reason at all why the data would be withdrawn.
  3. Is there an indication as to the cause of the crash in Windows event viewer?
  4. Hello Will, Try: <&RedispatchAlternateNavLog_Begin> <&RedispatchAlternateNavLog_End>
  5. Requestly supports various browsers, thanks for the heads-up Peter.
  6. Having released scheduled and non-scheduled flights for a week I can confirm all released 'scheduled' flights whether from the schedule list or individual flights created as scheduled have been retained. Non-Scheduled flights are only retained for a day.
  7. There certainly have been no changes made to the program. As I haven't used flights from the schedule recently I'll give it a try over the next few days and observe the outcome.
  8. Only retained if they were in the schedule. I haven't tested if an adhoc flight marked as scheduled is retained.
  9. Your only option is per my post above. You only need add the endurance figure as the Vatsim FPL Import ignores the E/ reference in the PFPX flightplan.
  10. Hello Andreas, I don't believe the prefile link can be user modified. However you can simply copy the ATC route and use the 'Import ICAO FPL' function on the Vatsim prefile page.
  11. Tested here without issue, can only suggest to make sure Microsoft Visual C++ redist are up to date along with graphics drivers.
  12. Additionally to the numeric suffix issue there are end-of-line tabs in the PFPX weather export that can prevent loading. These can be removed by editing the file with Notepad++ and using the find and replace function: Alternatively add the following Macro function to your notepad++ shortcuts.xml Macro's section located \AppData\Roaming\Notepad++ <Macro name="PFPX WX Trim" Ctrl="yes" Alt="no" Shift="no" Key="189"> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="\t\r\n" /> <Action type="3" message="1625" wParam="0" lParam="2" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="\r\n" /> <Action type="3" message="1702" wParam="0" lParam="768" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> </Macro> open the .wx file and run the macro from the menu or using CTRL -
  13. As the route is not airport to airport they are automatically sub-routes Andrej
  14. Hello Andrej, Using the route editor you can create 'sub-routes', essentially a route between two waypoints. PFPX will then use these predefined legs when route finding. Additionally they can be selected from the initial waypoint when constructing a route manually, just as selecting and airway.
  15. In order for the Weather uplink function to work the exported route file should be in the format ICAOICAO only and not have the numeric suffix. This is a change from previous PMDG products.
×
×
  • Create New...