alpha117

member
  • Content Count

    861
  • Joined

  • Last visited

Community Reputation

44 Excellent

About alpha117

  • Rank
    Privat Pilot - SEP

Recent Profile Visitors

4407 profile views
  1. That's no problem, at least those will get him started
  2. Cheers Tom, Forgot about them
  3. Hi All Does anyone know of any 'good' tutorials you tube or whatever, for a beginner who has just purchased PFPX Not for me btw, a colleague from Leonardo Software. He does not want a full dispatcher course, just something to get him up and running Many thanks
  4. alpha117

    PFPX v2 missing things

    MaddogX export is fixed in V2.03
  5. alpha117

    V2.03 where to download

    Why not on Christian's site, or is AeroSoft not bothered about users who were on board from day 1
  6. It's not on FlightSimSoft's web site, so where do we download it from for those that purchased from Christian direct before AeroSoft got involved? Thanks
  7. alpha117

    PFPX 2.01 hotfix

    No issues here when using AS as the current weather engine 1. Can you confirm that you have the 'TERRAIN' DB file in your Public Documents PFPX DATA folder 2. Can you confirm that you have setup PFPX to point to the correct Active Sky file, and if so does the AS file have the 'current data' in it? 3. Confirm that you did Run Active sky before you started PFPX?
  8. alpha117

    PFPX 2.01 hotfix

    Looks like the issue is when ANY alternate route is 'Direct', then you will be 'stuck'. Like I a m here, right now The way around this, until Christian gets around to fixing/changing this is to delete the DCT Alternates like so: Now you can complete the planning process. It's not perfect BUT is is a current work around
  9. alpha117

    PFPX 2.01 hotfix

    EFB export OK here
  10. alpha117

    PFPX 2.01 hotfix

    Hi All, The Maddog route export, still misses the last 2 waypoints from the PFPX route. Looks like the issue is with 'Directs' Exported route(MDR) KSFO KBOS/KPVD DIRECT TIPRE 38.205833 -121.035835 Q126 EKR 40.067444 -107.924950 J100 OBH 41.375736 -98.353592 J10 IOW 41.518963 -91.613251 J146 GIJ 41.768612 -86.318451 J554 JHW 42.188606 -79.121307 PFPX generated route
  11. I've just done KSFO > KBOS and the export on this route has missed the last 2 legs. Strange. OK, back onto it. @Stephen can you let Christian know, or do you want me to?
  12. They are both wrong......hmm
  13. Here is the PFPX route KSFO > KPHX, that it has just given me WESLA4 NTELL Q158 BIKKR Q15 CHILY J6 DRK V257 MAIER MAIER5 ...and here is the loaded exported MDR file into the LM Unless we are all missing something??
  14. Myself and one of the Development team checked to make sure that this worked as it should and it does. I have also just had conformation from the lead programmer of the MaddogX that it works as it should, route only. I've asked the MaddogX BETA team to recheck that the export still works as it should. As Stephen has said it was fine before release. Can you also attached the mdr file From the Real World Pilots in the development team: Where I work you don’t even select the planned arrival. It uploads to the last waypoint prior to the planned STAR In my company, company routes or datalink route uplinks do not include rwys/sids/stars Thanks