VR Focus Gets Stuck

ISSUE DESCRIPTION

Description of the issue:

If you bind VR Focus to any button or key, it will become stuck in certain focused views and require mouse movement to be released. Sometimes I use it to get a quick glance at instruments and then it won’t release. I then have to grab the mouse and move it around.

FREQUENCY OF ISSUE

It will happen every time if you focus on certain instruments, such as the MFD display on a G1000.

REPRODUCTION STEPS

  1. Bind VR Focus to any key or button. I usually use the ~ key
  2. While in VR flight, hold focus binding to look out the windows
  3. Release focus binding - this returns the view to normal
  4. Hold focus binding to look at detailed areas of the instrument panel. It may or may not become stuck in the focused view.
  5. If the view becomes stuck, move the mouse to return to normal view.

What peripherals are currently plugged in, as well as your VR headset? Please name all of them as there could be a potential conflict.

VR Focus bindings on Keyboard and tm16000. Focus binding removed from right mouse button.

[END OF FIRST USER REPORT]


:loudspeaker: 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:

didn’t realize that moving the mouse could unstuck it, i had to go to external view and back to cockpit

Yes, it’s still kind of annoying but not as bad as going external!

If I had to guess it’s locking into a specific instrument camera view. But that is kind of not ideal.

It’s a half thought out idea from 2020 that has been ported to 2024.

Xplane has a good VR implementation where you push the button with the binding and you get a 2x(3x?) zoom wherever you are looking. Nice for reading gauges or looking at POI out the window. Would love to see something like that.

3 Likes

It appears this was fixed! I think it happened during SU2.

Although I wonder if it was fixed on purpose or it was just an accidental fix? The report never got acknowledged or showed in the release notes.

It could also be a developer was in the code and just noticed something funky?