Please put your post in the correct forum.
Today we had to move over 150 posts manually.  We do feel the forum structure is logical and the section names are clear. As redirecting posts pollute the forum a lot we will not add them anymore. So if you are unable to find your post, look for it in the most logical forum section.

Jump to content

Neuerscheinungen und Updates

Was wurde in letzter Zeit veröffentlicht.

386 topics in this forum

    • 0 replies
    • 260 views
    • 14 replies
    • 3142 views
    • 11 replies
    • 950 views
    • 1 reply
    • 422 views
    • 1 reply
    • 378 views
  1. TBM 900

    • 16 replies
    • 927 views
    • 0 replies
    • 572 views
    • 1 reply
    • 993 views
    • 3 replies
    • 852 views
    • 2 replies
    • 1540 views
    • 2 replies
    • 1165 views
    • 2 replies
    • 1246 views
    • 1 reply
    • 1619 views
  2. AS320 SP1

    • 4 replies
    • 1768 views
    • 0 replies
    • 1681 views
    • 1 reply
    • 2485 views
    • 5 replies
    • 2276 views
    • 0 replies
    • 2509 views
  3. Simwings Balearen

    • 11 replies
    • 2954 views
    • 30 replies
    • 4702 views
    • 4 replies
    • 3036 views
    • 3 replies
    • 4519 views
    • 5 replies
    • 2816 views
    • 5 replies
    • 3240 views
    • 3 replies
    • 3297 views


  • Posts

    • I think I just found the culprit: SOVIL DCT SITNI DCT BAGSI DCT MATIG DCT TRAUN L856 AKABI UZ613 TRA Z69 OLBEN UN869 BENOT -> PFPX ignores the restriction, however it's the automatic route found by PFPX   If I manually change it to: SOVIL DCT SITNI DCT BAGSI DCT MATIG DCT TRAUN L856 RAVED/N0453F340 L856 TRA/N0440F330 Z69 OLBEN UN869 BENOT -> PFPX gets it correct   That is really strange, because the route restriction is RAVED L856 NEGRA MAX FL345. This portion of the route is before AKABI, so PFPX should always take this restriction into account.  To answer your question: I get the same results irrelevant if I'm using MAX or OPT FL.
    • Interesting observation. Installed PFPX on a clean system. Subscription expired. PFPX crash after loading. I don’t have time to enter the subscription code, since crash after loading. Turned off the Internet. PFPX started and did not crash. I got to the window for entering the subscription activation code, entered it. He turned on the Internet and began to press the activation button. Subscription activated. After rebooting PFPX, everything began to work.
    • I meant to say fuel not file. Sorry
    • If I remember correct there was a selection next to generate loadsheet. I have to check. Maybe that was dropped and is now an error in the docs.
×
×
  • Create New...