From 4a77a5782199d26319243998927428bddfdbb1ad Mon Sep 17 00:00:00 2001 From: Sergio Villar Senin Date: Tue, 4 Feb 2025 16:43:47 +0100 Subject: [PATCH] [PicoXR] Use a different input profile for Pico4U Pico has defined a input profile for the Pico4U which is different to the ones for the Pico4 or the Pico4E. It is not in any OpenXR doc so we were not aware of it. We got that info from the Pico customer service. The problem was that the runtime was selecting the generic Khronos profile instead of the Pico4 profile because we were not suggesting the specific profile for the 4U but for the 4 (or 4E). Actually the runtime should probably select the Pico4 profile over the generic one but that's their decision anyway. --- app/src/openxr/cpp/OpenXRInputMappings.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/src/openxr/cpp/OpenXRInputMappings.h b/app/src/openxr/cpp/OpenXRInputMappings.h index 537b953e3e..b43ef97359 100644 --- a/app/src/openxr/cpp/OpenXRInputMappings.h +++ b/app/src/openxr/cpp/OpenXRInputMappings.h @@ -289,7 +289,7 @@ namespace crow { }; const OpenXRInputMapping Pico4U { - "/interaction_profiles/bytedance/pico4_controller", + "/interaction_profiles/bytedance/pico4s_controller", "vr_controller_pico4u_left.obj", "vr_controller_pico4u_right.obj", device::Pico4U,