Bug Report - Hand Tracking is being Shaky/Laggy (Reproduced on 2 devices)
Hi, after going through the forums, back and forth between Meta Support, they couldn't help me, so I am going to put all the information together here. Hand Tracking seems to work but it's incredibly shaky when staying still. I managed to reproduce this on a Quest Pro and Quest 2 on Link and Standalone. This seems to be exclusive to OpenXR apps, it doesn't happen in the Home environment nor Apps such as First Hand Experience app or at least it's not as noticeable. I managed to reproduce this in the new Aura sample app that got released on App Lab on Standalone. As well as other two barebones OpenXR apps via Link. Here's two videos showing the issue: (I made sure to be in lit environment, so it's not bad lighting) Video #1: https://youtu.be/wBfFyP7Tl10 Video #2: https://youtu.be/08E-BWR4CD0 Version v49 (49.0.0.206.357) on Standalone (Quest Pro) I also tried both the latest PTC version (50.0.0.165.257) and the stable version (49.0.0.170.358) of Oculus PC software on Link, if that matters. My first forums post about this issue: PTC v50 Oculus Link issue - Hand Tracking is shaki... - Meta Community Forums - 1030901 (atmeta.com)5.1KViews4likes8CommentsGet Device Physical Screen Resolution
I am trying to get the physical width and height of the device to create the swapchains. With the old Native VrApi that is currently deprecated, I could use VRAPI_SYS_PROP_DISPLAY_PIXELS_WIDE and VRAPI_SYS_PROP_DISPLAY_PIXELS_HIGH to retreive the correct physical screen resolution. When tested on the Meta Quest 2, the results were 1,832 and 1920. I am moving my code to use Native OpenXR. Using the OpenXR Runtime when I query for typedef struct XrViewConfigurationView { XrStructureType type; void* XR_MAY_ALIAS next; uint32_t recommendedImageRectWidth; uint32_t maxImageRectWidth; uint32_t recommendedImageRectHeight; uint32_t maxImageRectHeight; uint32_t recommendedSwapchainSampleCount; uint32_t maxSwapchainSampleCount; } XrViewConfigurationView; and for typedef struct XrSystemGraphicsProperties { uint32_t maxSwapchainImageHeight; uint32_t maxSwapchainImageWidth; uint32_t maxLayerCount; } XrSystemGraphicsProperties; The recommended width and height I receive are 1440 and 1584, while for the maxSwapchainImageWidth, maxSwapchainImageHeight, maxImageRectWidth and maxImageRectHeight, I am receiving 8192. I believe the maximum swapchain size should be the physical size of the screen. Or maybe there is another way to retreive the physical screen resolution like it was implemented in the deprecated VrAPI. System Information: Device: Meta Quest 2 Build: Meta Quest build 50.0 OpenXR Loader Version: 1.0.24 Development: OpenXR Native API1.5KViews1like0Comments