This issue should be really logged as a bug. please, please, please… it is really intrusive.
ISSUE DESCRIPTION
The intrusive “Device Disconnected” pop-up still appears in MSFS 2024 SU5 when Meta Quest 3 controllers enter sleep mode.
When flying in VR with a Quest 3, the VR controllers automatically power down due to inactivity (which is normal), the simulator displays a large “Your controller has been disconnected” notification on screen.
This pop-up is very disruptive in VR. Since we use the controller frequently to action switches, It breaks immersion and is completely useless.
That issue was inexistant in version previous SU4.
This issue was already reported (but not bug logged) previously and remains present in SU5.
FREQUENCY OF ISSUE
Occurs every time the Quest 3 controllers go into sleep mode during a VR session.
REPRODUCTION STEPS
Start MSFS 2024 SU5 in VR mode using Meta Quest 3 via Link (USB).
Use physical flight controls (yoke/throttle) and do not use the Quest controllers.
Wait for the Quest controllers to automatically enter sleep mode.
Observe the “Device Disconnected” pop-up appearing in the simulator.
YOUR SETTINGS
The issue occurs with no mods and no add-ons.
What VR headset and peripherals are you using:
Quest 3 connected with link. Same thing happend with virtual desktop over WIFI
[PC Only] Are you using Developer Mode or have you made any changes to it?
no/no
[PC Only] What GPU (Graphics Card) do you use?
Nvidia 4090
[PC Only] What other relevant PC specs can you share?
i9-13900 CPU, 32GB RAM.
I honestly find it strange that this issue isn’t getting more attention. It’s clearly not an isolated case, I’m not the only one experiencing it, and others have confirmed the same behavior. There is even a mod published to fix it.
This is not a minor cosmetic glitch. In VR, the “Device Disconnected” pop-up is intrusive and breaks immersion every single time the Quest controllers go to sleep, which is normal during cockpit flying.
I also don’t understand why this hasn’t been logged as a bug yet (for you community manager!). It’s an obvious issue that shouldn’t remain as-is, especially in a VR environment where immersion is critical.
It seems to me that this was actually a deliberate decision by someone at Asobo, who thought it would be a good idea (?!?!?) As it is there by design, Asobo would not classify this topic as a bug report, but only as a Wish-List entry. Given the progress of considering long-standing Wish-List items, I’m not too hopeful of a fix.
This is the main grievance I have with Asobo. They have done many things which most simmers disagree with (and are even scientifically incorrect), but they will never consult with us before implementation, and are reluctant to admit they have made a wrong move after implementation. I really can’t see them changing any time soon.
Thank you for the bug report. We have asked the team if this would quality as a bug or a wishlist item and will reclassify depending on their answer.
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
Having a notification if my yoke or honeycomb throttle disconnected for some reason is fine. Having notification each time we use a VR controller is not ok. It even stay as long as I don’t use the mouse. We just use it very frequently and those devices should be excluded from the notification system.
Even better, let the users choose which notifications they want!
