-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EFB: when using VR, the keyboard for user input disappears when I turn my head #8545
Labels
Request
New feature or request
Comments
Hey, I want to try and reproduce this, which headset are you using? |
Hi there.
I am using the HP Reverb headset.
Cheers
Stephan
…On Sat, 2 Mar 2024 at 13:55, Aurora Takemi ***@***.***> wrote:
Hey, I want to try and reproduce this, which headset are you using?
—
Reply to this email directly, view it on GitHub
<#8545 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUZ6DWKMBNVBEMWWWGDCAZDYWFSUZAVCNFSM6AAAAABEC2SCF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZUGMZTANZQGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thanks, using the Quest 3 I can replicate the behavior. Video attached com.oculus.shellenv-20240302-090941.mp4 |
We do not yet officially support VR as we do not develop and test for it. |
frankkopp
added
Request
New feature or request
and removed
Bug
Something isn't working
labels
Mar 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: