Skip to content
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

VR headset not detected when using Oculus Quest 2 via Airlink #470

Open
skalarproduktraum opened this issue Jan 24, 2022 · 2 comments
Open
Labels
has workaround A workaround for the issue is available and contained in the issue description or comments. upstream-library Issue originates in an upstream library

Comments

@skalarproduktraum
Copy link
Member

skalarproduktraum commented Jan 24, 2022

Description

When using the Oculus Quest 2 VR headset via Airlink (wireless connection), SteamVR might sometimes not recognise the headset as being present. This is a known issue with SteamVR and Airlink, and independent of scenery.

Workaround

With Airlink

In order to circumvent the problem, the different applications have to be launched in specific order:

  1. Connect the headset to the computer with a suitable USB 3.0 cable
  2. Set up Airlink
  3. Access the virtual desktop from the Quest 2 headset, and launch the scenery application from there.

Using Virtual Desktop

An alternative is using Virtual Desktop -- the issue does not occur there.

@skalarproduktraum skalarproduktraum added has workaround A workaround for the issue is available and contained in the issue description or comments. upstream-library Issue originates in an upstream library labels Jan 24, 2022
@skalarproduktraum skalarproduktraum pinned this issue Jan 24, 2022
@moreApi
Copy link
Member

moreApi commented Apr 4, 2022

Can not reproduce. For me it works like it should. Maybe its patched?

@kephale
Copy link
Member

kephale commented Jun 9, 2024

@skalarproduktraum closable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has workaround A workaround for the issue is available and contained in the issue description or comments. upstream-library Issue originates in an upstream library
Projects
None yet
Development

No branches or pull requests

3 participants