Well then, thanks for figuring this out with me. To bad it ended in a feature breaking bug. The Legacy Asobo leave behind with VR in Flight Simulator is good but not great. Here’s for a better try with 2024.
My assumption is that the mouse recentering when you turn your head is not a bug per se in the game, but a limitation of rendering where you are looking. The headset is only rendering the image where you are looking. It is not rendering anything past he screens in any direction. Thus, the mouse has no where to actually be, so it centers on your view.
I bought and use these exact 2 pieces of hardware:
11:40 in this video.
Destination Departure kneeboard
Kensington K72359WW trackball (that exact trackball)
this video has 2 main points:
1 Quest 3 has really good passthrough (their new software this week improved the passthrough images).
2 But Quest 3 will not give the fps and performance that a Pimax Light can.
You are right that it’s not a bug. But has nothing to do with limitations. This is probably done this way so when the mouse pointer is off view it moves into view so you won’t loose it and have to look around to find it. With a mouse pointer that can move around in 3D space it can easily be lost anywhere.
I just wish this was toggable with a hotkey to bring it into view when you need to. Then I could rest the mouse pointer on a controller and use it even when it’s off view. It’s obvious Asobo rarely use VR themself when playing this game or stuff like this would be fixed.
I’m hoping for better support in 2024 but I don’t think that will happen. Most likely it will be worse.
They seem to be able to make it work for when you hold the primary action button down, so I’m not sure why the ‘primary action (locked)’ equivalent doesn’t work?
Maybe I’m assuming too much about their naming convention, but the same approach has been employed elsewhere in the control mapping settings. It could also be that there is some other setting that also needs to be changed, to allow the “(locked)” versions to work, but if that is the case, then the very least that the devs should do is to provide that information in the description of the command.
I did try some settings I found that was “Enable lock”, “Disable lock” and “Toggle lock”. Not sure if this was the exact naming but something very similar. However, I didn’t get that to work either. But then, who knows what the real intention of these settings are. It’s not like there is a manual for this
That’s what I do and fly always in VR. Map all important buttons to the HOTAS. Don’t use VR controllers at all. I use a track-ball mouse mounted beside the throttle quadrant. Can switch stick and yoke. Fighter throttle on left, levers on the right.