Ways to identify the "active" controller and set it.
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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?
- 主要语言
- C++
- 星标
- 6.7k
- 派生
- 1.3k
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ValveSoftware/openvr 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 85/100
ValveSoftware/openvr#1289 · 1 个 reaction ·
-
难度 1/5 1 小时以内 新手友好度 72/100
ValveSoftware/openvr#227 ·
-
难度 4/5 3-5 天 新手友好度 45/100
ValveSoftware/openvr#1922 ·
-
难度 5/5 一周以上 新手友好度 42/100
ValveSoftware/openvr#1921 ·
-
难度 3/5 1-2 天 新手友好度 48/100
ValveSoftware/openvr#1919 ·
查看 ValveSoftware/openvr 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 92/100
autowarefoundation/autoware_universe#13413 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
-
automated-analysis bug memory-safety
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
gazebosim/gz-sensors#662 · 1 条评论 ·