MSFS2024 - Unable to click with VR controllers on any of the displays except OIS (works properly in MSFS2020)

[devil2311]

Hello, 

as stated above, I am unable to click and use the CDU and other displays when in VR using the VR controllers (Quest 3). Everything works as expected on the OIS. The cursor moves around just fine, but does not register any clicks (sometimes when you spam click it will register one click - but thats a 1/10 chance).

Strangely this behaviour is not exhibited in MSFS2020. But this exact behaviour is also seen in the A400 in MSFS2024. 

Is this a known issue and will be fixed at some point? At the moment you are forced to use the mouse to interact with the displays which breaks immersion :/

 

Sim - MSFS2024 (Tested on both release and beta versions)

Aircraft - A350 latest version (.07 I think?) and also A400

Steps to reproduce - Just load into the plane in VR and try to set up a flight in the CDU using just VR controllers.

Best Regards

[Nickelodeon228]

Same behaviour for me.

 

[Nickelodeon228]

Hello,

 

is there any process of it?

For me the plane is dead, as i am only fly in VR and cannot use the FMC.

[devil2311]

I don't think this will get fixed. Pretty sure this plane was never tested in VR 🙂

[thirteenstorm2]

I have this problem also. Just switched to 2024.. Didnt have this problem in 2020 just fwiw. The mouse works but the problem is as described in previous posts. 2024 su2 

[Lukasz Krajnik]

No issues on my side with A350 in VR. Not clickable cockpit can be related to FS2024 issue when one exits cockpit to menu while in VR. As a rule max a few times switch between menu and cockpit helps. I do not know if this is the issue on your side. Just trying to help.

edit - are you sure it has nothing to do with WASM?

Edited May 25 by Lukasz Krajnik

[richboy2307]

Hi,

We have some testers who have used this aircraft in VR primarily since pre-release (both sims) without any major issues, even going in-and-out throughout longer flights.

There is a known sim limitation specifically in VR or when using headtrackers/camera shake addons (like FSRealistic) that affects the accuracy of hit registration of mouse clicks on the MFD, which is being worked in FS24 SU3 Beta based on user reports.

Please confirm that the aircraft is functional in 2D, if not, try to clear your WASM folder and launch directly onto a runway on first load to ensure proper WASM compile.
Thanks!

[devil2311]

Glad to hear a fix is being worked on! Apologies for implying it was not tested in VR. I'm happy to be wrong. Hope a solution is found 🙂

[Lukasz Krajnik]

On 5/25/2025 at 2:47 PM, Lukasz Krajnik said:

No issues on my side with A350 in VR. Not clickable cockpit can be related to FS2024 issue when one exits cockpit to menu while in VR. As a rule max a few times switch between menu and cockpit helps. I do not know if this is the issue on your side. Just trying to help.

edit - are you sure it has nothing to do with WASM?

Well, after 1.0.12 I got same issue with „frozen cockpit” - not only displays but also sidestic and throttle not responding. Is this issue known to IniBuilds? The only thing I changed was A350 version (from 1.0.10 to 1.0.12, following all rules when updating) and some standard Windows 11 updates. No changes to FS2024 or graphic driver. I never had this one before, spent already 3 days trying to figure out things without any conclusions. Now I am expert in departure briefing but nothing more. I read here many writing about similar bugs but also many writing they have it just perfect. The latter one was my case also until now. And when it happende the airframe is good for training at the gate (no freezes in 1-2 hours) but as soon as engines go alive the clock starts ticking… It would be nice to get some feedback if developer is aware of this issue and does it affect FS2024 only or both simulator users?