You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using VR, when I open a keyboard in the EFB (e.g. to enter a target altitude), the keyboard disappears when I move my head left or right.
Expected behavior
I suspect that this was introduced by #8447.
While the intention of this change is correct, the implementation needs a bit more tweaking for VR users like me,
I see two possible approaches here:
ideally, only invoke the unfocus event when the head is moved by a far greater amount as it is currently the case. Maybe by 45 degrees or so?
the unfocus event could be time delayed, with the timer starting after I enter the first number/character. Then do not invoke it for lets say 10 seconds or so.
Both might need some 'playing' around to find the best compromise.
Steps to reproduce
STEPS TO REPRODUCE
Can happen at any stage of a flight, just make sure that you are using VR while flying (I am using HP Reverb)
Look at the EFB and access the TOD calculator
Click on the Target Field -> the EFB will display the keyboard
Optional: Click on a number on the keyboard to enter a target altitude
Turn your head left or right - a small movement should do
CURRENT OUTCOME
the keyboard disappears
I have to click into the target altitude field again to make the keyboard show up again
We do not yet officially support VR as we do not develop and test for it.
Once the aircraft is more complete and more of the dev team has access to VR headsets we can look into this.
Aircraft Version
Development
Build info
Describe the bug
While using VR, when I open a keyboard in the EFB (e.g. to enter a target altitude), the keyboard disappears when I move my head left or right.
Expected behavior
I suspect that this was introduced by #8447.
While the intention of this change is correct, the implementation needs a bit more tweaking for VR users like me,
I see two possible approaches here:
Steps to reproduce
STEPS TO REPRODUCE
CURRENT OUTCOME
COMMENT
Most likely introduced by #8447
References (optional)
No response
Additional info (optional)
As mentioned above, my guess is that this was introduced by #8447
Discord Username (optional)
StephN-B
The text was updated successfully, but these errors were encountered: