Getting lower resolution than requested from local PC

I’m testing with the Zapbox iOS client app as described in this post.

When testing with an EC2 instance launched with the NVIDIA AMI I get the full requested resolution - 1664x1568 per eye when using an iPhone 12. However when connecting the exact same client app build to the local PC which has an RTX3070 the stream is received at 808x768 (just slightly less than half the width and height).

There’s plenty of bandwidth - the PC has a dedicated WiFi 6 router connected via ethernet that’s in the same room as the client device and the client network stats all look perfect (no packet loss, RTT of 3ms, quality 5).

I’ve tried uninstalling and reinstalling CloudXR (and SteamVR) and still see the issue, I was wondering if there are some settings files somewhere that might have cached something from some of my earlier client experiments?

That is strange.

One thing to try: see whether you have a command-line arguments file for SteamVR. This docs section shows how to find the right directory:
https://docs.nvidia.com/cloudxr-sdk/usr_guide/cmd_line_options.html#windows-options

Also, can you share the server and client logs?
https://docs.nvidia.com/cloudxr-sdk/support/support.html#log-files

Thanks. I don’t have any CloudXRServerOptions.txt file in that folder on the server.

Client Log:
Streamer Client Log 2024-09-12 18.08.34.txt (5.5 KB)

Server Logs:
CloudXR Server - SteamVR Log 2024-09-12 18.02.33.txt (16.4 KB)
Streamer Server Log 2024-09-12 18.02.36.txt (269.9 KB)

The compositor resized parts in the CloudXR Server look potentially relevant

Found the culprit, though not the root cause…

In C:\Program Files (x86)\Steam\config\steamvr.vrsettings there was a line in the steamvr block saying "maxRecommendedResolution": 810.

Removing that line when SteamVR was closed looks to have fixed things.

Not sure quite how that setting got in there - I was playing with maxResFactor in cxrDeviceDesc at some point but then also played with the Video settings UI in StreamVR trying to fix it. I’m happy for that to remain a mystery now I can get full res from my local setup :)

So glad you figured it out, and thanks for sharing!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.