OnCourse Software

Did you have proper spaced out waypoints on your FSX flight plan up to shortly before the destination airport?

I just did a flight and got all instructions from departure to arrival, what I did was have 3 VOR waypoints spaced out through the flightplan.

It seems when you request a higher altitude midflight that stops any descent instructions later...so I have to do L+3 etc to start a descent and as I'm descending request vectors using "7". This then leads to automatic descent and approach instructions again, usually around 20,000.

dmarch wrote:

There were no waypoints in your flight plan... you must have at least one

I just do the generic GPS direct flightplan from FSX and load that in PF/PFE. It always worked for me before pre 2.14.

I did two flights, one with "DP active" checked with "alt compl" at 0, and one flight with "DP active" unchecked. For both flights I got told to fly runway heading, but without any altitude instructions...the interactions just after takeoff included, "Gulf xxx at 1...

I have also had problems. I use "easy atc" and "dp active" settings but I still have to manually increase and decrease my altitude, and invariably it doesn't work. I didn't have this problem pre 2.14. I've emailed you Dave with my debug monitor. Thanks.

AI Smooth might help?

Is this about my log or daveo? Dave, Just taken another look at your log and despite being told several times to turn to heading 300 you never did... after departing you turned and continued turning till reaching 330. Then after a couple of nags you then turned to heading 027. Now, I'm not saying we...

I have SID/DP and easy atc selected, so pre-2.12 I was usually told that I'm "cleared to 8000 (etc) delta papa." But now with 2.12 I was told to "fly runway heading" then at 300ft I was told to "resume own navigation", I was given no altitude instructions throughout the...

Yeah, the new and improved TGS gauge doesn't work for single monitor gaming.