[Pico] Workaround input profile selection in Pico4 Ultra #1739
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The OpenXR runtime in the Pico4 Ultra incorrectly selects the Khronos simple profile instead of the more specific Pico4 one provided by the XR_BD_controller_interaction extension. This results in Wolvic rendering a generic trigger controller instead of the actual 3D model for Pico4 Ultra controllers.
|
Before |
javifernandez
approved these changes
Feb 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The OpenXR runtime in the Pico4 Ultra incorrectly selects the Khronos simple profile instead of the more specific Pico4 one provided by the XR_BD_controller_interaction extension.
This results in Wolvic rendering a generic trigger controller instead of the actual 3D model for Pico4 Ultra controllers.