Hello,
again i have the problem with mouse not working in the cockpit.
(left click doesn’t do anything)
Problem, i swithed binding to default, and tried to switch to “legacy mode”, bu now this option is locked …
So I don’t know how to interact with my cockpit…
I use a mouse, quast 2 and X52,
Thanks if you have a tip!
I think you mean …“Still”
almost 3 years later
Hello
Actually problèm was solved indeed 3 years ago and i updated after long time no play…problem is back but with no solution
I really don’t know what to do, default biding doesnt do…
Unplug and plug it back in.
What about right-click, or wheel button? With the updates being implemented by WT, I know I needed to use these rather than the left click I was used to - for me, now the middle button is PULL and right button is PUSH.
I came in to add, I’ve been having vanishing mouse cursor lately. Toggling VR off and on can recover if that doesn’t cause a CTD.
It usually happens to me when I turn off the overhead lights on the C172. I wish they were not on by default.
Was just coming to report this.
Been flying in VR on my Quest2+6700xt very happily for over a year.
Since the latest update (MSFS or Oculus ??) when flying (trying) the DC3 you can click a few switches, then nothing works. Exit VR and re-enter. Can click a few more then nothing.
Also, rudder pedal (Logitech G29) and my Bravo Throttles stop responding until I go out of VR and then back in.
Weird thing is throttles etc stop responding in the cockpit, if I switch to the externbal camera they are fine and I can fly the plane, but as soon as I hop back in the VR cockpit they stop responding.
I can’t imagine this would go un-noticed by Asobo in testing. They have really put a lot of effort into VR.
I wonder if it is some other piece of software (OpenXR , FSrealistic etc, Oculus etc) having issues with the latest update. After all, all these pieces of software get updated.
This is the price to pay for using PC. Has always been the way.
I will try and do some trouble shooting.
I know I’m invisible on this topic, but against my better judgement and for those who read and don’t just post.
Disable VR controllers, disable game controllers in Steam, unplug the mouse and plug it back in.
FIXED IT…still no idea what it was.
before firing up the sim, I renamed my Community folder to BAD_COMMUNITY so MSFS would create a new empty folder
Fired up the same plane (DC3) at the same airport and joy of joy’s was able to click to my hearts content. All my controls worked fine. Had a quick flight . Landed, taxied, shutdown. All worked perfectly
Shutdown MSFS. Renamed the new empty community folder to GOOD_COMMUNITY and renamed BAD_COMMUNITY back to community.
Fired up MSFS and much to my surprise everything was working perfectly as before. Not sure what happened , but it fixed it.
Hello tthere (i see you !! not invisible)
Thank you for your answer, i’ll give that a shot and tell you
In the meantime i achived to set mouse as “legacy” and it works as old times, but still don’t know why the mouse doesn’t work with the new control system (with the blue controls etc)
From what I can gather, MSFS expects a game controller input. In VR it is also looking for an input from the VR controllers. Steam also provides a game controller input to MSFS through its own channel.
My first issue was a SteamVR update which stated that game controller optimisation had improved. I changed the settings and had no issues.
Then MSFS updated. There is something about how MSFS reads USB allocation, and with an update it resets to game controller mode as if the mouse isn’t there or the USB allocation defaults. MSFS had the mouse as unusable when flying.
When the mouse is pulled and put back in, Windows does something that MSFS then recognises that there is a mouse, and it is the primary controller when flying. I also suspect that there are different mouse types and software that make it more difficult.
I still get the white dot appearing randomly, but a move of the mouse makes it disappear. I have had to pull the mouse a few times. One of these was after I forgot to turn off the VR controllers in Virtual Desktop.