Skip to content
This repository has been archived by the owner on Aug 11, 2024. It is now read-only.

Controller mapping unification across platforms #240

Closed
SimonDarksideJ opened this issue Jul 17, 2019 · 1 comment · Fixed by #508
Closed

Controller mapping unification across platforms #240

SimonDarksideJ opened this issue Jul 17, 2019 · 1 comment · Fixed by #508
Assignees
Labels
Feature Request FR Accepted Feature Request accepted, ready for development
Milestone

Comments

@SimonDarksideJ
Copy link
Contributor

XRTK - Mixed Reality Toolkit Feature Request

Is your feature request related to a problem? Please describe

Currently, multiple mappings are required for the same controller across platforms
(With the exception of WMR). E.G. Separate mapping profiles required for Oculus Touch on OpenVR and Native Oculus (due to differences in how mapping works)

Ideally, this should be unified so a controller type only needs mapping once for all supported platforms

How would you classify your suggestion

  • Usability / Configuration
  • Architecture / Services

Describe the solution you'd like

One mapping per controller type (same as WMR is currently implemented)

@StephenHodgson
Copy link
Contributor

Good luck with that, each is technically a different Type under the hood. While yes the mappings usually match up across OpenVR vs the native platform it's not always the case.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Feature Request FR Accepted Feature Request accepted, ready for development
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants