This began happening to me after SU6 and has continued (worsened) since SU7, totally wrecking ATC communications sequences.

After takeoff and selecting a new cockpit camera (Ctrl+ appropriate number) ATC will respond as if I had pressed the single number and inappropriately proceed with the wrong response/instructions.  This happened occasionally after Sim Update 6 (never before) and has continued after Sim Update 7 to the point that it's occurring at least once or more on every flight.  After selecting a camera view, ATC has mistakenly:

• Canceled my IFR flight plan (which I didn't request)
• Approved an ascent to a higher altitude (which I didn't request)
• Approved a descent to a lower altitude (which I didn't request)
• Cancelled my approach (which I didn't request)

In most cases, I am able to eventually restore my IFR flight plan (if the disconnect happens early enough in the flight).  I am forced to first establish Flight Following then request a restoration of my original IFR plan.  I've had my IFR plan cancelled up to 3 times in one flight by simply changing camera views.

• In a couple instances my approach was cancelled when I was on final and on the glide slope.
• Today my IFR plan was canceled during climb-out.  After that I could not reconnect in any way to ATC communications (no menu selections available) so I made the 2-hour flight in total silence.

Check your keyboard bindings. Use the "Search by input" field on the left side. Click once in that field, then press the key combo for your camera change and see if it also shows an ATC command.

...jim

 

I'll check that out, though these are not my camera assignments - these are MS/Asobo's.  These are their standard Cntrl+1-0 bindings that they set up for every default aircraft.

They've also set their ATC keyboard bindings to 1-9.  The sim is apparently reading my changing cameras Cntrl+1, Cntrl+2 as "1" or "2", etc. and responding as though I made ATC requests.  Now, if nothing else works, I might set the ATC 1 - 4 responses to something else (joystick buttons, etc., though that would be a pain.

Just for info.. I do things a little bit differently.

I removed all the keyboard bindings for ATC. Instead, I use the mouse to select the response I want, until I'm at the runway hold point, ready to contact tower for take off clearance. At that point, I hand over ATC stuff to the co-pilot AI. I can still use the mouse to select stuff that the co-pilot does not, such as altitude increase/decrease requests.

After doing that, I changed the default camera views CTRL-2 through CTRL-0 to just 2 through 0. I left CTRL-1 as is, as I use 1 for my custom pilot view. Other custom views are assigned to ALT-1 through ALT-0. All of these are using the top row numbers, not the numpad numbers.

It's just one way of doing things, and is the way I like to do it. YMMV. 😉

...jim

 

Yeh - I've been thinking of doing something along those lines, though I prefer to not use the AI.  I have a complete set of custom ALT+ cams I use for each aircraft, so I prefer to not alter those and I've gotten used to each of their cam assignments.

One thing I might try is to "reverse" all of the assignments... set all of their views to number keys only and reset all of the ATC commands to Cntrl+...

OK - I can now verify that there are absolutely no duplicate bindings for the Cntrl+ number views or the single digit ATC selections in my assignments.  So, this is all an error with the sim's recognition of a combination key-press and a single key-press.

Since not everyone is experiencing this issue, I'm guessing this comes down to hardware - those of us who have keyboards/systems that occasionally generate this error within the sim and those who don't.  Since I don't have this issue with any other program, I would also guess there is a way for MS/Asobo to change the timing on reading key-presses?