Skip to content

@rpavlik rpavlik released this Dec 1, 2016

This is a minor update over 1.2.7 - the following are the main updates:

Addition of new device IDs to monitor INF

Additional HDK-derived devices will have a name associated with their entry in "Device Manager" under "Monitors". Since this INF is currently cosmetic (naming) only, this is purely a cosmetic change, though it may help in troubleshooting to be able to identify if an HDK display interface is visible to Windows.

Addition of a metadata package for the HDK 2 beltbox, revision of other metadata packages.

Belt boxes shipped with the HDK 2 vary slightly in their hardware identifiers and so may not have been assigned a friendly name and photo icon in the "Devices and Printers" Control Panel. A new metadata package has been added to identify these belt boxes.

Other metadata packages have been slightly modified, primarily removing references to HDK 1.x when the associated component may also be found with HDK 2.

Cleanups and compatibility improvements for INF files
While they shouldn't have prevented anyone's usage of the devices, the INF files had some warnings or errors in Microsoft verification tools that were not false-positives and that could be resolved. This release includes those cleanups, which may in a few cases cause the cosmetic INF files to apply on systems where they had not installed before (primarily 32-bit systems).

The attached executable installer includes:

  • The USB-CDC (USB serial) driver (for that "OSVR unknown device") used by the OSVR Control app (for updating firmware, etc). (Required on Windows 8.1 and below, will show up on Windows 10 as well) - shows up as OSVR HMD Communications Device under Ports in Device Manager
  • Windows 7 and up: "Device Metadata Packages" - aka, the data that makes nice icons appear in Devices and Printers - for:
    • OSVR HDK
    • OSVR HDK display panel (see #2 for why this is separate)
    • OSVR HDK 1.2/1.3/1.4 Belt Box/Audio (primarily for control of the USB Audio codec on the belt box that lets you plug analog headsets in - handles the "OSVR Audio" or the mystery "RAZER USB AUDIO" you might have seen there before, but also changes name to help indicate the HDK hardware model you likely have)
    • OSVR HDK 2 Belt Box/Audio (same purpose as above but for a minor variation in the belt box shipped with some HDK 2 units)
    • OSVR HDK IR Tracking Camera (will change name and icon indicate if an outdated firmware version is detected)
  • "Atmel USB DFU" driver needed for when the HDK is in firmware-upgrade mode.
  • Extra .inf drivers (primarily for naming purposes in the Device Manager - they do not need to override the behavior of the system-bundled driver yet), for:
    • OSVR HDK Head-Mounted Display - under Monitors (normal for this to be missing/hidden when in direct mode)
    • OSVR HDK Orientation Tracker (and its parent device, OSVR HDK USB HID Interface) - under Human Interface Devices
    • OSVR High-Speed Infrared Tracking Camera - under Imaging devices

Note that the device metadata installer that is a part of the executable bundle requires the .NET framework v4 client profile. You probably already have it, but if not, you can get it through Windows Update or at

As with previous installer executables, it can be run in silent mode by passing /S (case-sensitive!) on the command line to the installer.

The zip file contains only the .inf drivers for the USB-CDC (USB serial) device and the naming in Device Manager - it does not contain the "Devices and Printers" device metadata. It is provided as an option for those on non-x86/x64 platforms or as a convenience for advanced bundling purposes: its contents are a strict subset of the executable installer.

All drivers, as well as the installer, have been digitally signed by Sensics, Inc.

Assets 4
You can’t perform that action at this time.