Forum Discussion

nexusmtz's avatar
nexusmtz
Protege
8 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.