CloudXR 3.0 AWS ami - client not connecting

Hi,

I have created an EC2 using the 3.0 ami, followed the instructions, installing Steam, then SteamVR, then the SDK and running the firewall .bat, then installed the Client on my Oculus Quest 2 using adb per documentation and pushed an -s [ip address] to /sdcard/CloudXRLaunchOptions.txt (also using adb).

When I launch SteamVR and try to connect using the client app, the HMD cannot get past the rotating loading icon and the CXR icon does not appear in the SteamVR server app. CloudXRRemoteHMD is listed as a SteamVR addon and turned on.

Port configs are per default settings, running via a static elastic ip.

No logs can be found on the OQ2 as the /sdcard/CloudXR folder does not exist after running the client. Developer mode is enabled on the headset.

Below is the log from the server:
NVIDIA CloudXR v3.0 (CL# 30264573), built on Aug 4 2021 20:46:27.

[##] Cleaning up older files.
[##] VisionServerDriver::Init()
[##] CloudXR single instance mutex created, first one.
[##] VisionServerDriver::RunFrame() – creating VisionHmdDriver
[##] VisionHmdDriver()
[##] VSync to photons: 0.0200.
[##] Adapter 0: Description=‘NVIDIA Tesla T4’
[##] Direct3D setup done.
[##] Send audio: Enabled, Receive audio: Disabled, Foveation: Two pass
[##] Starting FrameServerDX11.
[##] Retry loading stream server dll from cxr directory
[##] Stream Server: Net Stream Server Instance Created
[##] Using an app provided render device for video processing.
[##] Stream Server: CloudXR video streams created
[##] Stream Server: Input stream created
[##] Stream Server: Audio send stream created
[##] Stream Server: streaming instance started - waiting for a client…
[##] VisionHmdDriver::VisionHmdDriver succeeded.

1 Like

i have the same issue i think :(

Whenever a CXR Client connects to the server, there will be several logs of connection attempts for each type of service (video/audio/etc). The line item: [##] Stream Server: streaming instance started - waiting for a client suggest that the CXR client isn’t even making it to the server. There’s likely something upstream that is blocked on the network that is preventing CXR connections to begin with. Have you double-checked your AWS Security Group settings within the VPC the EC2 instance is deployed in? Also, have you verified your outbound network supports ephemeral ports if outbound firewalls on your network are enabled?