Skip to content

Microsoft Mixed reality headsets don't show up in input selection, and can't be managed by tool #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wirelessdreamer opened this issue Aug 20, 2018 · 6 comments
Closed

Microsoft Mixed reality headsets don't show up in input selection, and can't be managed by tool #51

wirelessdreamer opened this issue Aug 20, 2018 · 6 comments

Comments

@wirelessdreamer
Copy link

Any plans to add support for mixed reality controllers support through SteamVR?
@lawwong
Copy link
Contributor

lawwong commented Sep 4, 2018

You mean not shown in VIU Settings support device list?
We haven't try it but expecting that check the "VIVE (OpenVR compatible device)" should also work on the Microsoft MR headsets.

@wirelessdreamer
Copy link
Author

when running example scene 7, and a role can be assigned to the headset, or controllers, nothing shows up when using a mixed reality headset.

@lawwong
Copy link
Contributor

lawwong commented Sep 13, 2018 •
edited
Loading

0d37c13 should fix it.
Previously we inactivate the unrecognized devices' icon.

@wirelessdreamer
Copy link
Author

I just pulled the current code and tested in 2018.2.0f2 I'm not sure if this is related but as soon as I enter the project using a mixed reality headset in steam vr, my headset and controllers show up at the start, within i have the laser pointer and reticle showing up, i try to point and click and the + icon, but when I pull the trigger it tries to teleport, and does not click on the +. after trying a few times both controllers disappear. if I don't use the controllers, they soon disappear as well.

These are the errors that keep repeating

image

lawwong added a commit that referenced this issue Sep 19, 2018
@lawwong
Update to v1.9.0
3c56e13 
* New Features
  - Wave VR Plugin v2.1.0 support
  - Add Oculus Go support (requires Oculus VR plugin)

* Improvement
  - [WaveVRModule] Add 6 DoF Controller Simulator (Experimental)
    - [More...](https://github.com/ViveSoftware/ViveInputUtility-Unity/wiki/Wave-VR-6-DoF-Controller-Simulator)
  - [RenderModelHook] Now able to load Wave VR generic controller model
  - [Example2] Add drop area that using physics collider
  - [Example3] Make scroll delta tunable from the Editor
    - [issue#49](#49)
  - [VIUSettings] Add WVR virtual arms properties
  - [BindingUI] Make un-recognized device visible in the device view (shown in VIVE device icon)
    - [issue#51](#51)

* Bug Fix
  - [VRModule] Fix sometimes SteamVRModule activated but not polling any device pose/input
@lawwong
Copy link
Contributor

lawwong commented Sep 19, 2018

It works fine on our MMR device (ASUS MR headset),
Will keep looking but need more detail about this.

It's odd that you pulled trigger but VIU gets pad pressed (enable teleport), maybe the second line message has to do with this?
BTW, VIU didn't intent to prompt that message.

@wirelessdreamer
Copy link
Author

just updated to 1.9 and devices are showing up and working as expected, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wirelessdreamer @lawwong