Detailed XR InputDevice names?

In Unity 2019.x, if I only have the OpenVR and Oculus packages via Package Manager (no SteamVR or Oculus integrations from Asset Store), is there a way to differentiate what input device (Vive Wand, Oculus Touch, whatever Knuckles are called now) the player is using with just UnityEngine.XR methods? XR.InputDevices seems to only return generic names.

 

I guess the answer is Input.GetJoystickNames() does provide detailed names, but for some reason my calls to it were returning empty strings till a second in.

 

Aha! I tried XRDevices.getDevices() but it was returning a single empty item. When I added it to the XRInputTests GetJoystickNames test scene which calls the display method, ShowJoystickNames(), every 3 seconds, I found that it was working, but just not on the first call from Start(). Sounds like when I tested the very first time (which caused me to start this post) I was running into a race condition between the headset/controllers loading and the data becoming readable.

On further testing, I also found:
XRDevice.deviceLoaded never got called, which I set in Start(), maybe I should try it in OnEnable() instead.
I added a test of XRDevice.isPresent to the beginning of ShowJoystickNames(), and it always returned true, even the first time when getDevices() returned empty objects.
In Start(), if I check XRSettings.loadedDeviceName before calling ShowJoystickNames(), getDevices() returned the devices correctly on the first call.

Sounds like some user error on my part, but maybe also a bug in the software. Also, this was only tested in editor, not on a built application.

 

Could we possibly get a list of the current names of the devices? We are doing some custom controllers and variable setting and this seems like the best way to determine whats going on.

 

@StayTalm_Unity with Unity 2019.3.3 and latest Oculus (v14), I'm currently getting:

Oculus Quest / Link:
InputDevice.name = "Oculus Rift S" (!)
InputDevice.manufacturer = (NULL)
InputDevice.serialNumber = "__SerialNumber__"

 

@StayTalm_Unity At least on the Oculus platform, I'm getting incorrect results using InputDevice.name versus the old XRDevice.model and GetJoysticks techniques. So for a Rift-S, for example, the new APIs for InputDevice report it as being named "Oculus Rift". And for the controllers, they're reported as "Oculus Touch Controller - Left/Right". The joystick name was reporting Rift S (forgot the exact name). So using the new system, I'm unable to distinguish between an actual Rift and a Rift-S, which I need to be able to do. Especially the controllers, since they have different orientations.

 

@Brady I've been developing VR games in Unity for some time now and making a proper distinction between devices of different brands and manufacturers is a real struggle every freakin time.
I've recently discovered that the same controllers names differs depending on used SDK with InputDevice.name call.
For instance controllers for Oculus Rift S - when using Oculus SDK - left controller is seen as "Oculus Touch Controller - Left", but switching to OpenVR causes the same controller to be seen as "OpenVR Controller(Oculus Rift S (Left Controller)) - Left".

Moreover when using Oculus SDK there is no distinguish between Oculus Rift and Oculus Rift S controllers - they're both named "Oculus Touch Controller - Left" (OpenVR seems to distinguish them pretty well, but still the name differs between SDK's) and some dirty hacks are needed to find the proper one.
This makes really hard to develop to different devices if you don't have them physically in your studio.
You can just guess the names developers setup as a hardware description.
Another really misleading example is Vive Focus Plus mobile device - headset is detected as "HMD Test Mock". Try to guess that one without checking!

It would be incredibly helpful to have a table of all supported devices and all hardware names for all SDK's as seen when calling InputDevice.name. And iclude controllers orientations and offsets.

 

+1 I'd really love to see a table of the different names too. It's already awkward to have to explicitly try out multiple different headsets to find these names - but I don't own all the different headsets to be able to do this for everything.

Really I wish there was a better designed API that assigned controllers, manufacturers and platform vendors numeric IDs somehow. I find it hard to trust that a string like "OpenVR Controller(Oculus Rift S (Left Controller)) - Left" isn't going to randomly change one day and break a ton of applications that are forced to relying on string comparisons to figure out what controllers are in use.

Extra metadata about orientations would be really helpful as @czeberesco mentioned. In my application I'm having to calculate a rotation for each different controller for showing the controller placed on the floor, as an icon for asking users to put the controllers down. It would be great if I could query a suitable orientation for displaying a controller as if it were placed on a hard surface.

 

Agreed. I'm trying to handle Vive input with having limited buttons, but I don't know the controller name to check for. You should have enum supported entries for common headsets, and fallback to the name option for other headsets.

 

+1 for table of device names (per-device AND per-platform, such as OpenVR vs. Oculus SDK, etc).

ALSO +1 for orientation information. It's a pain-in-the-ass to manually set orientations on a per-device basis, and that's only possible if you HAVE one of those devices. For devs who don't have a sample of every kind of hardware, it's impossible to correctly orient a hand, for example, to the controller.

 

Searching for that wished for table of device names brought me here...

 

Yeah, I'm _again_ looking and wishing for a table of device names as I add support for yet another set of controllers

 

I feel like a lot of people have been ending up like I did at the end of this thread dissapointed that there is no official list. While we wait to see if there is an official one I made a Spreadsheet of devices with names which has a form where people can add to it if they don't see their headset listed.
https://docs.google.com/spreadsheets/d/1N3yxn_ieW8Cab3QoPiZAaHDS7ppwyQvmSNRVB7gniKg/edit?usp=sharing
It'd be greatly appriciated if everyone could add their devices, before long I am sure we'll be able to have all values for common headsets!

 

I suggest you add a drop down option (if it's possible??) asking which sdk is in use. As that may affect the value returned by the API, especially in the case of OpenXR which by the way device names can be pulled from the package code.

Legacy / XRPlugin
SteamVR
OpenXR

 

Any news on that? The provided google docs file is outdated and has only one entry.

@StayTalm_Unity
Maybe unity can provide a list, that would be really useful!

 

Welp, this thread isn't very useful. It seems like we lost a working solution with no good replacement. I'd love to hear if there's a better solution since this thread was last active.

 

In Unity 2019.x, if you only have the OpenVR and Oculus packages via Package Manager, without SteamVR or Oculus integrations from the Asset Store, it may be challenging to differentiate specific input devices using just UnityEngine.XR methods. The XR.InputDevices may only return generic names in this context. You may need to implement additional platform-specific code to differentiate between input devices accurately.

iq test​