OnCourse Software

drumsart wrote:

Via Mce I requested a FL070 (the original flight plan FL) because for a reason I don't know the control sent me to FL090. So, after requesting FL070 with the correct sequence "Control <indicatif>Request FL070" the Atc answered me to climb FL130 !?. I tried some others request and every time the result of the answer was never what I asked.

05/10/2016 01:09:22: 691 - Transcript: '  November 8665 Romeo resume own navigation  '
05/10/2016 01:09:38: 503 - ****** HotKey #10 detected!
05/10/2016 01:13:53: 949 - ****** HotKey #6 detected!
05/10/2016 01:13:55: 188 - Transcript: '  November 8665 Romeo Climb to Flight Level 90  '

05/10/2016 01:19:38: 185 - ****** HotKey #19 detected!
05/10/2016 01:19:38: 255 - Requesting altitude change of +7000' at current alt of 5337
05/10/2016 01:19:39: 307 - Transcript: 'Roger   November 8665 Romeo Climb to Flight Level 120  '
05/10/2016 01:20:05: 304 - ****** HotKey #19 detected!
05/10/2016 01:20:05: 371 - Requesting altitude change of +7000' at current alt of 5698
05/10/2016 01:20:06: 432 - Transcript: 'Roger   November 8665 Romeo Climb and maintain Flight Level 130  '

ThomasAH wrote:

drumsart wrote:

Via Mce I requested a FL070 (the original flight plan FL) because for a reason I don't know the control sent me to FL090. So, after requesting FL070 with the correct sequence "Control <indicatif>Request FL070" the Atc answered me to climb FL130 !?. I tried some others request and every time the result of the answer was never what I asked.

OK, here some log lines that may help you with debugging MCE:

Code: Select all 05/10/2016 01:09:22: 691 - Transcript: ' November 8665 Romeo resume own navigation ' 05/10/2016 01:09:38: 503 - ****** HotKey #10 detected! 05/10/2016 01:13:53: 949 - ****** HotKey #6 detected! 05/10/2016 01:13:55: 188 - Transcript: ' November 8665 Romeo Climb to Flight Level 90 '

HotKey #6 with Departure/Center/Approach is "Request higher altitude due to turbulence" and always gives you +2000 feet. This explains FL90, even if it is funny/inconsistent that PF3 uses the cleared altitude as reference here: Your aircraft was at 3017 feet at this point.

Code: Select all 05/10/2016 01:19:38: 185 - ****** HotKey #19 detected! 05/10/2016 01:19:38: 255 - Requesting altitude change of +7000' at current alt of 5337 05/10/2016 01:19:39: 307 - Transcript: 'Roger November 8665 Romeo Climb to Flight Level 120 ' 05/10/2016 01:20:05: 304 - ****** HotKey #19 detected! 05/10/2016 01:20:05: 371 - Requesting altitude change of +7000' at current alt of 5698 05/10/2016 01:20:06: 432 - Transcript: 'Roger November 8665 Romeo Climb and maintain Flight Level 130 '

HotKey #19 is "Request a Higher Altitude" (default key "H") and was pressed together with "7" for +7000 feet. One time at (rounded) 5000 feet and the second time at (rounded) 6000 feet, so the result is correct from PF3's view. It seems like MCE did not yet read the aircraft altitude to make the decision about which key to send.

drumsart wrote:

Maybe Mce can remedy this or better Pf3. The ideal would be to ask any flight level directly.

drumsart wrote:

In my case I should have asked for Altitude 2000 to go to FL 070 ? It's correct ?

drumsart wrote:

On an other side I don't remember me to have requested a "Request higher altitude due to turbulence" !? May be a Mce glitch ? Curious...

drumsart wrote:

An other thing I noticed...Control Atc contacts me in first every time ! I though that was corrected with the new version ? (I can open a new topic for that or you forward ?)

ThomasAH wrote:

You are using voice recognition, and I found in the logs that PF3 sometimes is very quick to move to the next call.
I suggest you set the "PTT pause interval" to somewhere between 5 to 10 seconds and/or use a PTT key to pause PF3 while you are talking.

ThomasAH wrote:

Now I know what you are talking about: The initial contact by Departure "Roger November 8665 Romeo Radar contact QNH 1047" without pressing HotKey #0 first.
I just found it burried inside Constantly problems with flightplans, because I created a corresponding thread with only this topic in the beta forum
But sorry, this bug has not been fixed yet, but maybe you can try the possible workaround mentioned in above thread:

ThomasAH wrote:

You are using voice recognition, and I found in the logs that PF3 sometimes is very quick to move to the next call.
I suggest you set the "PTT pause interval" to somewhere between 5 to 10 seconds and/or use a PTT key to pause PF3 while you are talking.

You already have "PTT pause interval" at 8 seconds (good), so just the first half isn't enough.
But the PF3 log does not show any usage of the PTT key, so using "and" instead of "or" might help.
I assume you are already using a PTT key for MCE. Can you assign the same key as PTT key in PF3?
If you already did, maybe MCE "eats" the key before PF3 sees it, in this case you could use some key mapper (the one built into FSUIPC, or autohotkey) to pass one key (or button) press to two programs (MCE and FSX, PF3 will see the FSX key), or convince MCE to pass this key to FSX (maybe an option?).

Even if all this does not work, you can still do the check-in with Departure (and other Center facilities), even if they already contacted you, so PF3 does not get confused due to a missing check-in. Edit: I just saw that you did this.

But I'll add this information to the thread in the beta forum to raise the priority.

drumsart wrote:

In my case I should have asked for Altitude 2000 to go to FL 070 ? It's correct ?

drumsart wrote:

An other thing I noticed...Control Atc contacts me in first every time ! I though that was corrected with the new version ? (I can open a new topic for that or you forward ?)

ThomasAH wrote:

You are using voice recognition, and I found in the logs that PF3 sometimes is very quick to move to the next call.
I suggest you set the "PTT pause interval" to somewhere between 5 to 10 seconds and/or use a PTT key to pause PF3 while you are talking.

drumsart wrote:

Thank you Thomas for your clear explanations and great support !

drumsart wrote:

1/MCE should have translated FL70 to +2000 (press H, press 2, release 2, relase H) for you by looking at the current altitude.
In my case to go to 070 from 090 it would be press L, press 2, release 2, release L, not H... Correct ?