Hi NVIDIA team,
We are seeing an Enscape-specific issue after moving to CloudXR 6.x.
When streaming Enscape VR to a Meta Quest WebXR client, the scene appears to rubber-band / swim in the opposite direction during head rotation. The faster the head turn, the stronger the artifact. Translation / joystick movement looks smooth, and the stream itself stays stable.
This only happens with Enscape. The same CloudXR 6 pipeline works correctly with other OpenXR apps, including Omniverse USD Explorer, Unity, our own OpenXR lobby app, and Khronos hello_xr. We also tested hello_xr with Vulkan and D3D11, both without the issue, so this does not look like a general Vulkan problem.
We reproduced it with CloudXR Runtime 6.0.5 and 6.2.0, and on two different machines/GPUs. Changing max-fps, disabling immediate compositor, lowering Enscape quality, and disabling our OpenXR layer (responsible for hand-to-controller input synthesis) did not fix it.
Our OpenXR diagnostics show that the pose Enscape submits at xrEndFrame closely matches the pose returned by xrLocateViews, so from the app/layer side the submitted pose appears consistent.
The symptom looks like a pose timing / reprojection / timewarp issue specific to Enscape under CloudXR 6.x. Enscape worked correctly for us in the older CloudXR 4 workflow.
Has NVIDIA seen this before with Enscape and CloudXR 6? Are there known runtime settings or diagnostics we should collect for rotation-only wobble in OpenXR apps?
We can provide CloudXR server logs, OpenXR timing/pose logs, and a video capture.