Some suggested clarifications to get this running

[svrc]

I got this running, I have some suggestions:

1. The WindowsApp passes version "6.0.0" to the NVIDIA Streaming Manager and has no version selection logic. The Streaming Manager will thankfully not respect this and will dynamically pick the CloudXR runtime version, but it picks it differently than how the README in this project describes it.

First, it doesn't use the XR_RUNTIME_JSON (that is for the OpenXR app itself) or pick the first thing it finds in the server/releases directory. It expects the CloudXR runtime release to be in a subdirectory corresponding to the version number. e.g. releases/6.0.4. If you don't do this, the Stream Manager won't know what version to pick. For example, I had runtime 6.0.2 directly unzipped in the releases folder, and was getting an error when trying to connect the AVP that the 6.0.0 server version couldn't be started. When I placed it in a 6.0.2 subdirectory, it started to work. I added 6.0.4 later, and it it would choose 6.0.4 as expected.

2. There's a CloudXRService.exe that comes with the NVIDIA Stream Manager, this is the process host for the OpenXR Runtime, it probably should be mentioned. NVIDIA doesn't even mention it in their docs, I posted on their forum to suggest they should!

3. The Stream Manager API header & DLL comes with NVIDIA's sample app in the Stream Manager download, this is a bit unintuitive but not too bad to figure out.

4. The OpenXR test app itself needs to have XR_RUNTIME_JSON set to the CloudXR version you expect Stream Manager will launch... or else it will try to open up SteamVR or whatever system default OpenXR runtime you've set.

I've made a commit in my fork for these suggested clarifications. svrc@ed20d3d

Wish there was a clear way to tweak the emulated & encoding resolution, NVENC settings, etc. the encoding resolution that is negotiated with AVP is really low: I get warped: 1200x960 unwarped: 3800x3040 which means the NVENC is encoding at 1200x960 for a 3800x3040 unfoveated resolution. The ratio seems weird (I'd expect 1.14375 as the AVP lenses have). But I guess this is for the NVIDIA side to figure out unless it's a problem with the FoveatedStreaming framework.