It’s probably no surprise that this appeared at the same time as that new method of interaction with cockpit switches/knobs etc. was introduced. It’s also probably an unintended side effect, but hopefully those that worked on this will know exactly what’s happened, and undoing it should be relatively trivial.
I created a zenDesk Ticket for this on August 4th. Yesterday, September 20th I got an E-Mail that the bug has been solved. So maybe - MAYBE - with the next update this will be an issue of the past.
For Reference, here is the original E-Mail Text:
Thank you for submitting a bug report. Our team will review the information and try to reproduce the issue thanks to the information you provided.
WARNING - Bug reports are not to report technical or account issues that prevent you from installing, downloading or playing the sim. You will not receive further updates or an answer to this ticket.
Bugs and issues that have been successfully reproduced will be categorized and prioritized—game-breaking bugs will receive the highest priority, while middle-of-the-road and cosmetic bugs are prioritized based on reproduction and the number of times reported.
Be aware that the status of your ticket on Zendesk does not necessarily reflect the status of the bug in-game. For more information, visit Zendesk Bug Reporting FAQ or the Bugs & Issues forum.
Best regards,
Microsoft Flight Simulator Support Team
Unfortunately “Solved” on ZenDesk, according to their FAQ, means nothing more than the bug has been logged 
From their FAQ:
Solved: The bug report has been handled—our team has recorded the bug in our internal bug and issue tracker. Please note this does not mean you will see the bug fixed in the next update, but has been recorded and prioritized accordingly.
So… it appears they just took a few months to even acknowledge it 
Still… one can only hope…
1 Like
Yeah, I ripped someone a new one last week when my issue was marked as solved when it clearly wasn’t … i felt bad when I got their reply, then thought:
“You know what? That’s STUPID !! They should mark it as ‘registered’, and when it’s ACTUALLY solved, mark it as solved!”
I didn’t send that suggestion in …
My ZenDesk ticket was marked as solved immediate after i submitted it. So i dont know what to belive.
Ticket Statuses Explained (Bug Reports)
- Open: The report is in the queue. A bug report will remain open until it’s updated or marked as solved.
- Awaiting your reply: Our team contacted you to request more information and is waiting for your reply.
- Solved: The bug report has been handled—our team has recorded the bug in our internal bug and issue tracker. Please note this does not mean you will see the bug fixed in the next update, but has been recorded and prioritized accordingly
Source
Zendesk Bug Reporting FAQ – Microsoft Flight Simulator Support
3 Likes
Keepin’ this alive 'till something is done about it! 
Let’s see if we’ll still be here next year bois
7 Likes
@Jummivana weekly reminder that we have received no official word on this situation. Here’s hoping it can be addressed either here or in the upcoming Q&A.
5 Likes
Unfortunately I missed the Q&A session yesterday and it will be some time before I have time go to back and watch the vod. Was this addressed in any way in the Q&A?
bonjour, avez vous trouve une solution a ce problème cela est très handicap.
je confirme que cela arrive uniquement en mode vue cockpit
Merci
Didn’t notice anything unfortunately 
Guess we’ll just have to… wait.
Its not fixed, I dont know when it will be. Issue sounds like a very simple one…
1 Like
It is happening to me as well, this is very annoying …
1 Like
Patch notes are out. Not sure if it is fixed
I looked over those notes with the excitement of a kid on Christmas morning. I got coal… No word of any fix in the notes. And this thread is still being ignored. Feels great.
I gotta say, regardless of when (or wether) this bug is fixed, the communication (or lack thereof) has been appalling. Not asking for much, not asking for a fix, just some acknowledgment that this bug is known and a fix is investigated. Can’t be too hard to write some words down, can it?
To add insult to injury, we have a community manager posting right here in this thread, who picked an offtopic issue to respond to, all the while completely ignoring OP’s issue.
Turning to the community, as it seems we have been thoroughly ignored by Asobo/MS. Is there anyone who had this issue before and now has access to the beta that can confirm if this issue was fixed or not in SU6? (later edit:I was made aware that this might be asking people to break SU6 NDA. Whatever, I guess one can wait until the update lands)
5 Likes
The thread has “bug logged” on it now. There is the acknowledgement you seek.
You are asking people to break the NDA regarding SU6, so I’d avoid that if I were you.
bug logged means absolutely nothing in terms of acknowledging wether the issue is being actively worked on or not. So many issues have the “bug logged” tag and nothing has been done on them since launch. That, in my books, is not clear communication on this issue. Why, then, is it not part of the official known issues list?
Regarding SU6, I was not aware there was such a strict NDA on it, I’ll edit my previous commment.
That’s not possible as this tag has only existed for a few weeks, 16 days to be precise.
It will take time to go through all the bug threads to confirm whether they have indeed been logged with Zendesk, and confirm the issue has been logged internally.
Guys, this bug encouraged me to make a head tracker, using a webcam and infrared leds. I made it myself and spent only a few bucks. There are a lot of how-to tutorials out there. I highly recommend it to anyone who is having this problem with the camera. Once you get used to it, you can’t go back. Best of all, it works on all simulators, so it will continue to be useful on x-plane, which was another thing that this bug encouraged me to do 
That’s not possible
Factually incorrect. See Blurry lights on ultra-wide/4k resolutions. Logged in October '20, fixed in SU6 according to the patch notes, and that is just the most recent example, took 10 seconds to find it. There are more. Moreover, there are bugs that were “logged” after SU5 and are addressed by SU6, at least according to the patch notes. No such luck for this issue.
this tag has only existed for a few weeks, 16 days to be precise.
Look, I don’t peruse these forums on a daily basis, just to see what the Community team has been up to these days. I’m just a customer who spent way too much on this game, now rendered unusable by this bug, who is trying to make this issue break through the clutter. I would be happy if this issue at least made it to the known issues list.
And yes, for me, the game is rendered unusable in its current state, simply because of this bug. I tried working around it, either via different button assignments or via headtracking and neither are pleasant to use for me.
2 Likes