1411059 - ​Expose full OpenVR name string for Microsoft Mixed Reality headsets

Status: NEW

(Core :: WebVR, enhancement)

Description

[:kip (Kearwood Gilbert)]

We should verify that the strings returned by Firefox for Mixed Reality Headsets and their associated controllers match the strings returned by Microsoft Edge.

Currently, OpenVR headsets are all enumerated with a name of "OpenVR HMD" in Firefox.  Content makes the assumption that these headsets are all HTC Vive headsets, resulting in incorrect models being presented to represent the headset and its associated controllers.

A-Frame has already been updated to match the behavior of Microsoft Edge, which reports the full name as output from the OpenVR API.  The Microsoft Mixed Reality headsets will include an identifier in the string that ensures the displays can be differentiated.  This string will not include any serial number or other UUID that can be used for tracking.

Comment 1

[Daosheng Mu[:daoshengmu]]

Using mVRSystem->GetStringTrackedDeviceProperty() with ::vr::Prop_SerialNumber_String can get "WindowsHolographic" identifier for the HMD, and "MRSOURCE2000000010" for the controllers when using my Acer MR device.

In Edge, when running it on a WebVR page, it shows "Acer AH101" for the HMD, and "Spatial Controller (Spatial Interaction Source) 045E-065B" for the controllers.

Currently, Microsoft doesn't expose too much device info for OpenVR API. We can look forward their update for this part.

But, because all of Windows MR devices use the same looking of controllers, I think we can give them the same identifier. how about giving "OpenVR WS HMD" and "OpenVR WS Controller" for the identifier string. :kip?

Comment 2

[:kip (Kearwood Gilbert)]

(In reply to Daosheng Mu[:daoshengmu] from comment #1)
> Using mVRSystem->GetStringTrackedDeviceProperty() with
> ::vr::Prop_SerialNumber_String can get "WindowsHolographic" identifier for
> the HMD, and "MRSOURCE2000000010" for the controllers when using my Acer MR
> device.
> 
> In Edge, when running it on a WebVR page, it shows "Acer AH101" for the HMD,
> and "Spatial Controller (Spatial Interaction Source) 045E-065B" for the
> controllers.
> 
> Currently, Microsoft doesn't expose too much device info for OpenVR API. We
> can look forward their update for this part.
> 
> But, because all of Windows MR devices use the same looking of controllers,
> I think we can give them the same identifier. how about giving "OpenVR WS
> HMD" and "OpenVR WS Controller" for the identifier string. :kip?

I have talked with Nell at Microsoft about this earlier.  There are already two variants of controllers in the mixed reality platform.  Nell specifically asked if we could include the numeric codes in the name for identification purposes so the controllers and headsets can be differentiated.

If OpenVR isn't returning all the info required, we may be able to request some changes from Microsoft to make this possible.  I'll follow up with Nell with your findings.  I'll leave the NI? open as a reminder for the follow-up.

Comment 3

[:kip (Kearwood Gilbert)]

My MR set is due to arrive some time this week.  I'll be able to look directly soon and give feedback to Nell.

Comment 4

[:kip (Kearwood Gilbert)]

I've followed up with Microsoft for more details.  Hopefully we will be able to generate the exact same strings as Edge.

Comment 5

[:kip (Kearwood Gilbert)]

I'll take this one and update it once I get feedback from Microsoft

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.