Ways to identify the "active" controller and set it.

Open
#1,663 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
api

Research direction

No file or test is named. Start by reviewing the OpenVR API documentation and interfaces related to tracked devices, controller roles, and input selection, then reproduce the behavior with Index and Quest 2 controllers. Done would require a clearly defined API for identifying or selecting active controllers, along with corresponding documentation or tests.

Written by the indexing model from the issue text.

Description

I've been experimenting with using index controllers with a Q2 headset, and something I've noticed is if steamvr is started with the index controllers if I proceed to start/connect a quest 2 controller(required for calibration and initial menu interaction) sometimes it will become the active controller (able to interact with menus/recognised as the controller to be used in a game), and sometimes the previously connected index controllers will remain active.

So my question is is there anything in the API that allows me to see which devices specifically are the "active" ones, and possibly allow me to set which ones are active?

Dominant language
C++
Stars
6.7k
Forks
1.3k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ValveSoftware/openvr

All issues in ValveSoftware/openvr

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.