The way the cursor works when it’s placed between overhead panel switches is really weird and makes playing in VR more difficult. It’s very inconsistent as well between different planes.
For example, on the A330 the cursor floats maybe about 15 cm / 6 inches below the overhead panel whenever there’s no switch underneath. Once I move the cursor over a switch, it snaps right to it. This makes the cursor jump up and down frantically like Super Mario on steroids when moving from one switch to another. It takes a little bit of guesswork to hit the switches sometimes. I suspect this to be an odd design choice and not a bug, but I’m not sure. FBW’s A32NX for MSFS 2020 has a less severe but similar problem, and it’s one the main reasons why I rarely fly it. I think that ideally the cursor should just follow the surface of the panel instead of jumping all over the place.
On the A320 the problem is kind of the opposite. When the cursor is between switches, it fools the depth perception and makes it look as if the cursor is behind the panel, not in front of it. This is a weird effect as it basically lets you see through an opaque surface, which is not in line with reality.
The TBM and the 747 are even weirder. I can often see two cursors and I have to cross my eyes to make it look like one. The cursors also turn weirdly small when placed over the panel. These and the A320 seem more like actual bugs to me and I’m thinking of reporting them.
I’m using a Reverb G2 with 4070 Ti. I’m interested if anyone else is having these issues, as I’ve never heard anyone talk about them. 2020 had (still has?) similar and known problems with a misaligned cursor, but I think they mostly applied to custom camera angles. Here it’s not limited to those.
)