Accepted: Prioritizing Valve Controllers Over Meta Quest 3 Controllers
The Context
We are considering the use of Quest 3 and Lighthouse tracked Valve Index controllers for our project when using playspace calibration.
The Problem Statement
The issue we face is that when a Meta Quest 3 is used, it takes over the controller priority. So we’re unable to open the steamvr menu.
Solution Proposal
To address this problem, we propose turning the SteamVR Index controller on and off. This action will prioritize the Valve controller over the Meta controller.
The Benefits
- Ensures optimal functionality of the Valve controller.
- Prevents interference from the Meta controller.
The Downsides
- May need to be adjusted for different hardware configurations.
The Road Not Taken
We could have chosen to let the Meta controller take priority, but this would not have been ideal for our specific needs.
The Infrequent Use Case
This solution may not be necessary for users who do not use a Meta Quest 3.
In Core and Done by Us
This proposal has been developed and will be implemented by the V-Sekai development team.
Status
Status: Proposed
Decision Makers
- V-Sekai development team
Further Reading
- V-Sekai · GitHub - Official GitHub account for the V-Sekai development community focusing on social VR functionality for the Godot Engine.
- V-Sekai/v-sekai-game - The GitHub page for the V-Sekai open-source project, which brings social VR/VRSNS/metaverse components to the Godot Engine.
This proposal was assisted by AI assistant, Aria.