Unable to interact with aircraft controls using mouse or VR controllers

[JCSLOVE]

Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

Concern is present with developer mode on or off.

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue.

Concern present will all mod disabled and community folder empty (FSUIPC, Mobiflight, pop-out manager).

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

All aircraft are affected.

Brief description of the issue:

After the latest update I am unable to interact with the cockpit using the mouse or VR hand controller. When I hover over a control (knob, dial, switch) it turns blue like it should, but I can’t interact with it. One day everything was working the next day there was a small 613Mb update; then this issue. I cleared everything out of the community folder. I also changed the mouse inputs in the menu. I tried on 5 different aircraft. Same issue with all of them. This happens whether in VR or not.
Was also able to reproduce this concern on my laptop (CPU: i9-12900H, GPU: 3080 ti, 64Gb memory, 2-2Tb NVMe drives.

Provide Screenshot(s)/video(s) of the issue encountered:

N/A

Detailed steps to reproduce the issue encountered:

Just run the game.

PC specs and/or peripheral set up if relevant:

CPU: 5800x3D, GPU: 6900XT, 64 Gb memory, 2-2Tb NVMe drives.

Build Version # when you first started experiencing this issue:

1.37.19.0

---

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:

[DementedCorn327]

Hi @JCSLOVE ,

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

[JCSLOVE]

Hi @DementedCorn327
I Don’t understand how this isn’t a bug. Program worked correctly, program performed mandatory update, program stopped working correctly. Plus you moved it to the VR help section when I clearly stated that the concern is present in both VR and 2D modes and on 2 separate machines.

Just did some digging in YouTube. Found that the cockpit interaction system setting in the options menu was set to “Locked”, instead of “Legacy”. Never knew this option was there, let alone changed it. Something in the 631 Mb update that was installed today was probably the culprit, considering nothing else was changed on either machine.

[DementedCorn327]

Moved to Aircraft & Systems since may fit better in that category. If it was a bug, many users would already have reported it. Looks like an incorrect configuration on your side. Is your default mouse profile set to “Default” ?.