Skip to content

Commit

Permalink
[PicoXR] Use a different input profile for Pico4U
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
svillar committed Feb 6, 2025
1 parent 1adae94 commit 4a77a57
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion app/src/openxr/cpp/OpenXRInputMappings.h
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down

0 comments on commit 4a77a57

Please sign in to comment.