VR with Quest 3 : controllers aiming sometimes not working

Bug Reporting Hub Virtual Reality (VR)
,
1

ISSUE DESCRIPTION

Description of the issue:
While using MSFS2024 with my Quest 3 in VR mode, aiming the dashboards buttons work fine until I interrupt the current flight to go to the menu, then when I resume the flight, I cannot aim no dashboard buttons anymore. I need to restart the flight from the beginning to be able to aim the dashboards buttons again.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
community folder is empty

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
very close to always, flights where i do not meet this bug are rares.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Start a flight in VR mode using a Quest 3.
  2. Aim any button of the dashboard and you will see they become blue, showing you you can act on them.
  3. Press the escape key (you will then leave the flight and display a menu).
  4. Click on “resume” to resume your flight.
  5. Aim any button of the dashboard and you will see they don’t become blue anymore, showing you that you cannot act on them anymore.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are currently plugged in, as well as your VR headset? Please name all of them as there could be a potential conflict.
Quest 3 connected via the USB link cable, USB keyboard/mouse

[PC Only] Are you using Developer Mode or have you made any changes to it?
no

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?
4090

[PC Only] What other relevant PC specs can you share?
Alienware R15, 64GB RAM, 4090 GPU, i9 CPU, Windows 11.

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

2

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Sort of.

I have additionally noticed on three occasions, the cockpit stopped reacting to the Quest (or even mouse controller). I hadn’t had any such issues since moving to the SU2 builds. When this happens even though my controller “laser pointer” is visible it cannot manipulate any controls. This issue does seem to be triggered by changing out of cockpit view or going to menus, but I think in one case it was just the former (changing to a different custom view and back) and not hitting escape to menus.

Provide extra information to complete the original description of the issue:
• Possibly related, possibly a separate bug, I’ve noticed a regression in my quest 3 controller “laser pointer” since SU2 builds started. I notice, at times, the Quest controller “laser pointer” starts rapidly flickering between indicating something in the cockpit (Asobo 737) and pointing thru the cockpit into the ether beyond. This gets triggered for me most often when I have the controller well off to the periphery of my view (such as when leaning over to program the FMC). When this flickering starts, I am unable to select anything. Pulling my head back and putting the controller forward in my view stops the flickering.

If relevant, provide additional screenshots/video:
•

3

anyone on Quest 3 got to the update tool and Get V76. improvements across the board in tracking.

4

Thanks for the heads up.

Unfortunately, the flickering “laser pointer” problem I’ve been having as of late that I referred to above was not solved by V76. I’m not convinced my issue is related to the Quest controller because the position of my controller itself seems to be tracking just fine at all times. It’s as if the pointer in MSFS suddenly has issues intersecting with the cockpit (as if the cockpit itself were flickering in and out of existence).

I haven’t seen any other mention of this flickering issue, though. I wonder if it’s unique to me. I wish I knew what triggered it.