OnCourse Software

Center keeps asking the VC to contact xxx Center the same frequency I am using. After I call a new voice responds and ask again the same thing. The main problem he forgets to descend me, I was at 40 miles at cruise FL300 so I started descend on my own, finally I had to declare emergency and that made the controller switch me to approach!

this is happening me on every flight.


Windows 10
Prepar3d v.3
FSLabs A320
EZDOK 2
AS2016 using historical weather mode+ASCA
PFPX
Ultimate Traffic Live
PF3
GSX
FSUIPC registered
Intel i5/GEFORCE GTX

I suspect the two consecutive XXX waypoints between SNAKR and MYDIA trigger a bug in PF3. Dave?

PF3 noticed that you have reached your TOD, but I guess above problem caused problems with giving you descent instructions.
In such situations you can request a lower altitude (if needed multiple times) to get below center altitude, which will cause a hand-off to approach.

Until this is fixed, you could try adding a waypoint between the two XXX waypoints and tell us if this helps.

ThomasAH wrote: *

Tue May 16, 2017 7:58 am

I suspect the two consecutive XXX waypoints between SNAKR and MYDIA trigger a bug in PF3. Dave?

PF3 noticed that you have reached your TOD, but I guess above problem caused problems with giving you descent instructions.
In such situations you can request a lower altitude (if needed multiple times) to get below center altitude, which will cause a hand-off to approach.

Until this is fixed, you could try adding a waypoint between the two XXX waypoints and tell us if this helps.

MYDIA is only 5nm from XXX so that might be the issue. Oh and another problem the fpl is back to front (the section between SHAKR and MYDIA that is). What flight planner are you using?

This is a better fpl
DHP V3 MNATE FIS G765 MAXIM G765 ANALI G765 NUKAN G765 URTOK G765 IMOLO R519 DUGNI

This 'could' be a problem with the 'direct to...' request so I'd appreciate you trying the same flight without using any 'direct to...' requests and report back

dmarch wrote: *

Tue May 16, 2017 10:13 am

This 'could' be a problem with the 'direct to...' request so I'd appreciate you trying the same flight without using any 'direct to...' requests and report back

I'll let you know. This time avoiding any Direct to.

Thanks

ThomasAH wrote: *

Tue May 16, 2017 7:58 am

I suspect the two consecutive XXX waypoints between SNAKR and MYDIA trigger a bug in PF3. Dave?

PF3 noticed that you have reached your TOD, but I guess above problem caused problems with giving you descent instructions.
In such situations you can request a lower altitude (if needed multiple times) to get below center altitude, which will cause a hand-off to approach.

Until this is fixed, you could try adding a waypoint between the two XXX waypoints and tell us if this helps.

I don't see any XXX waypoints in my flight plan. Do you refer to TOC and TOD "waypoints"?

I am using PFPX for flight planning.

Rgds,

vololiberista wrote: *

Tue May 16, 2017 9:57 am

ThomasAH wrote: *

Tue May 16, 2017 7:58 am

I suspect the two consecutive XXX waypoints between SNAKR and MYDIA trigger a bug in PF3. Dave?

PF3 noticed that you have reached your TOD, but I guess above problem caused problems with giving you descent instructions.
In such situations you can request a lower altitude (if needed multiple times) to get below center altitude, which will cause a hand-off to approach.

Until this is fixed, you could try adding a waypoint between the two XXX waypoints and tell us if this helps.

MYDIA is only 5nm from XXX so that might be the issue. Oh and another problem the fpl is back to front (the section between SHAKR and MYDIA that is). What flight planner are you using?

This is a better fpl
DHP V3 MNATE FIS G765 MAXIM G765 ANALI G765 NUKAN G765 URTOK G765 IMOLO R519 DUGNI

I am attaching my PFPX flight Plan that I used for this flight. This flight is loaded once I am in P3D. I don't see any XXX waypoint there. Maybe XXX was generated by PF3??

massimo390 wrote: *

Tue May 16, 2017 12:50 pm

vololiberista wrote: *

Tue May 16, 2017 9:57 am

ThomasAH wrote: *

Tue May 16, 2017 7:58 am

I suspect the two consecutive XXX waypoints between SNAKR and MYDIA trigger a bug in PF3. Dave?

PF3 noticed that you have reached your TOD, but I guess above problem caused problems with giving you descent instructions.
In such situations you can request a lower altitude (if needed multiple times) to get below center altitude, which will cause a hand-off to approach.

Until this is fixed, you could try adding a waypoint between the two XXX waypoints and tell us if this helps.

MYDIA is only 5nm from XXX so that might be the issue. Oh and another problem the fpl is back to front (the section between SHAKR and MYDIA that is). What flight planner are you using?

This is a better fpl
DHP V3 MNATE FIS G765 MAXIM G765 ANALI G765 NUKAN G765 URTOK G765 IMOLO R519 DUGNI

I am attaching my PFPX flight Plan that I used for this flight. This flight is loaded once I am in P3D. I don't see any XXX waypoint there. Maybe XXX was generated by PF3??

No you won't see XXX waypoints in the PFPX fpl as they are added by PF3. They represent Centre boundaries. They don't usually cause any problems though. I guessed your fpl software was PFPX as what it did is a common mistake in its algorithm. It's always a good idea to check a generated fpl against the real charts!

After the flight plan is loaded into PF3 but before you connect, click the Adjust Altitudes button on the main PF3 screen and you will see where the XXX waypoints have been added.

Dan77 wrote: *

Tue May 16, 2017 1:57 pm

After the flight plan is loaded into PF3 but before you connect, click the Adjust Altitudes button on the main PF3 screen and you will see where the XXX waypoints have been added.

Additionally there will be a .json file in the Flight/FPP directory which you can load in http://geojson.io/ to see a map of your flight plan with these XXX waypoints included. PF3 inserts them where it expects a hand-off from one center to the next.