Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PicoXR] Added a new interaction profile for the Pico 4 Ultra #1746

Merged
merged 3 commits into from
Feb 6, 2025

Conversation

svillar
Copy link
Member

@svillar svillar commented Feb 4, 2025

The 4 Ultra has its own interaction profile. It cannot be found in any online sources that we know but we were told about it by the Pico's customer service.

This allows us to remove the workaround that we landed to select the Pico4 profile over the generic Khronos one.

Apart from that, we take the chance to remove the unused Pico4xOld profile, that might potentially break controller support for devices with old PicoOS versions.

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.
That interaction profile was used long time ago when the Pico4 device
didn't have its own interaction profile. It's actually the profile
designed for the Neo3. Recenctly Pico released an extension that
provide a specific profile for the Pico4, so this should not be
needed. Actually the code was not using it at all, so any device
selecting it would be broken.
Copy link
Collaborator

@felipeerias felipeerias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving since the changes look reasonable, but I haven't tested them on the device.

@svillar svillar merged commit 9cc650e into main Feb 6, 2025
22 checks passed
@svillar svillar deleted the pico4u_profile branch February 6, 2025 09:18
@svillar svillar added the release_candidate PR that should be part of the next release label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_candidate PR that should be part of the next release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants