Forum Discussion

vrlab-ecg's avatar
vrlab-ecg
Honored Guest
7 months ago

No option to disconnect VR-headset via PC (Air Link)

Situation/Context:

I am in a position where I work with multiple Meta Quest 3 VR-headsets (one at a time, but multiple lying around). Since I do not work alone these multiple Meta Quest 3's belong to a pool of VR-headsets, freely usable by anyone around.

Problem:

When having a Meta Quest 3 linked to a computer via the Meta Quest Link app (Air Link), a new connection with another Meta Quest 3 cannot be established — neither is it possible to have multiple VR-headsets connected at the same time, nor does a new connection (attempt) disconnect the current one.

If a VR-headset is connected to some computer and not actively disconnected, it will try to connect to this very computer everytime both devices are turned on and connected to the same WiFi. If the paired VR-headset is now being used by someone else, who is not using the Air Link option, this very connection stays active. As a result the computer, which is still linked to the now-away-VR-headset, cannot be used with another VR-headset — neither via Air Link, nor via a cable connection. There simply is no option from the pc-side to cancel an active connection.

Restarting the Meta Quest Link app (through the beta-version feature) will result in the connection being instantly established again. This also happens after restarting the entire computer — as soon as the Meta Quest Link app has started and the WiFi connection is active, the paired VR-headset is connected again.

Further questions:

Are there any methods to disconnect a vr-headset-pc-connection without access to the vr-headset?

Any other tipps to avoid the above described situation (other than 'just disconnect the VR-headset before you stop using it')?

Possible solution:

Adding a button inside the Meta Quest Link app to actively disconnect a VR-headset would solve this issue in an instant. I would think that there are a couple of people out there who are developing with the Meta hardware and would appreciate such a feature (as to no longer hunt for the currently connected VR-headset and politely ask the current user to disonnect the Air Link connection..).

 

Thanks

Air Link
connection
feature idea
feature request
Headset
Meta Quest 3
Meta Quest Link App
PCVR

2 Replies

  • nexusmtz's avatar
    nexusmtz
    Protege
    7 months ago

    Make sure Settings, Advanced, Developer, Link Auto-Connect is off on the headsets.

    When you need to terminate an active rendering session, run 

    & "C:\Program Files\Oculus\Support\oculus-client\OculusClient.exe" --url oculus://STOP_REMOTE_RENDERING/

    Even if Link Auto-Connect is on, the headset won't reconnect a rendering session until its Link status changes, e.g. reboot, AirLink on/off.

    If that doesn't help, or the single connection that you're trying to terminate isn't an active link session, you could be creative and knock the connected headset off long enough for you to connect by setting up a firewall rule.

    One time: (admin PowerShell)

    New-NetFirewallRule -DisplayName OVRServer_Block_IP -Enabled False -Direction Inbound -Action Block -Program 'C:\Program Files\Oculus\Support\oculus-runtime\OVRServer_x64.exe'

    To use: (admin PowerShell)

    $ip=Get-Process -Name OVRServer_x64|
  %{Get-NetTCPConnection -State Established -OwningProcess $_.Id}|
    ?{$_.RemoteAddress -ne '127.0.0.1' -and $_.RemotePort -ne 443}|
      Select -First 1 -ExpandProperty RemoteAddress
Set-NetFirewallRule -DisplayName OVRServer_Block_IP -RemoteAddress $ip -Enabled True
Start-Sleep -Seconds 60
Set-NetFirewallRule -DisplayName OVRServer_Block_IP -Enabled False

    Or you could allow one IP instead of blocking the currently connected one, but you'd need to know the IP of each headset.

  • vrlab-ecg's avatar
    vrlab-ecg
    Honored Guest
    6 months ago

    Thank you for the reply. I guess that kind of works. With auto-connect on, this still remains a problem. Setting a firewall rule is a bit too much I think, but I guess works as a last resort..

    Would be nice, if this was handled by meta themselves and added as a feature <.<