Well, during my last Ifr flight (EGPH to EGPE), the clearance was : climb Alt 3000 then FL80 ten minutes after departure.
After the resume own navigation, departure control left me at Alt3000, I never received the order to climb to my cruising altitude FL80.
This is a known issue and has only been fixed in the latest beta (3.3.4) from yesterday.
Great to know ! Hope the update will come soon !? 
After a moment I decided to climb. Of course departure control says me to descend and maintain 3000 (no problem it's normal).
Then departure asked me to contact approach (I was at + 65 miles of my destination
. At this subject PF3 everytime (very often) asks me to contact approach control at +-80 miles...!? Is it normal ?).
Your cruise altitude was 8000 feet, which is the default center altitude. This sometimes caused handoffs to Approach for me, too, when flying only few feet below 8000.
Dave changed the behaviour in 3.3.3 to make this better, now it should be:
Handoff to Center triggered when your altitude is >= xxx
Handoff to Approach when your altitude is <= xxx - 250
(but I haven't tested this yet)
Is possible to change the default center altitude ?
After landing and vacated runway the tower sent me a message as "report downwind" or something !
04/04/2017 06:21:22: 050 - Transcript: 'Lancair Fox-Trot Papa Victor November November Contact Tower on 122.6 when clear of the active '
04/04/2017 06:21:42: 710 - ****** HotKey #10 detected!
04/04/2017 06:22:53: 830 - ****** HotKey #2 detected!
04/04/2017 06:22:56: 030 - Transcript: 'Lancair Fox-Trot Papa Victor November November report turning base '
|
Hotkey #10 is Roger. With Hotkey #2 you reported entering Downwind, which is always followed by "report turning base". Do you think it is worth adding code to catch this and reply something more suitable? Or just assume that this might happen in real-life, too, if a pilot reports turning base while on the ground?
I thought it was a "glitch" because I don't remember to have used the hotkey "2". I flied in voice mode with Mce. Of course no need to add code to catch this and reply something more suitable. Understood.
Last but not least, I have from the day one in all PF3 versions the following :
Just after Taking Off and entered the departure frequency, the center contact me with the radar contact message before I contact him. I thought this "glitch" was fixed in the last version !?
Unfortunately this has not been fixed yet, I have just asked Dave to raise the priority for this.
If I'm very quick with check-in after changing the frequency, this is OK for me. But if I'm not, I just check-in afterwards, because otherwise problems may occur.
Great to hear it will be fixed one day !
