Changes For Release 1.11.x

This section describes changes to the Oculus SDK, the Oculus App, Oculus Home, and the runtime.

Overview of Release 1.11.x

This release enables you to specify a tracking origin, provides raw button values, and adds Asynchronous SpaceWarp (ASW) statistics.

New Features for 1.11.x

  • Added ovr_SpecifyTrackingOrigin(), which enables you to specify the tracking origin instead of setting the tracking origin based on the user's current location. For more information, see Position Tracking.
  • Added IndexTriggerRaw, HandTriggerRaw, and ThumbstickRaw, which provide raw button values without a deadzone or filter. For more information, see Button State.
  • Added the following ASW Performance HUD statistics:

    • ASW Status
    • ASW Active-Toggle Count
    • ASW Presented-Frame Count
    • ASW Failed-Frame Count
  • Added the following ASW SDK statistics:

    • AswIsActive
    • AswActivatedToggleCount
    • AswPresentedFrameCount
    • AswFailedFrameCount

API Changes for 1.11.x

There are no breaking changes to version 1.11.x.

Known Issues

The following are known issues:

  • Some older AMD CPUs are not currently compatible with Asynchronous SpaceWarp (ASW), which might cause your system to repeatedly crash. The workaround is to disable ASW by setting its registry key to 0. For more information, see Asynchronous SpaceWarp.
  • If you encounter intermittent tracking issues, remove the batteries from any Engineering Sample Oculus Remotes that you paired with your headset and contact Developer Relations for replacement remotes.
  • If you bypass the shim and communicate with the DLL directly, without specifying a version to ovr_Initialize, the DLL has no way of knowing the SDK version with which the application was built. This can result in unpredictable or erratic behavior which might cause the application to crash.
  • There are some USB chipsets that do not meet the USB 3.0 specification and are incompatible with the Oculus Rift sensor. If you receive a notification in Oculus Home or the Oculus App, plug the sensor into a different USB 3.0 port (blue). If none of the USB 3.0 ports work, plug the sensor into a USB 2.0 port (black).
  • Antivirus software, such a McAfee, can cause installation issues. To work around the issue, make sure you have the latest updates and disable real-time scanning.
  • If you encounter installation issues, delete the Oculus folder and install the software again.
  • If the Rift displays a message that instructs you to take off the headset, remove it and place it on a flat surface for 10-15 seconds.
  • The keyboard and mouse do not work in Oculus Home. To select an item, gaze at it and select it using the Oculus Remote or Xbox controller.
  • Bandwidth-intensive USB devices, such as web cams and high-end audio interfaces, might not work when using the Rift. To work around this issue, install the device on another USB host controller or a separate computer.
  • For dual-boot systems using DK2 or CB1 HMDs, the OS selection screen might appear on the HMD instead of the monitor. To work around this, try plugging the HMD into a different port or unplug the HMD while booting.
  • If you are running your application from the Unity Editor and you press the controller's home button to return to Oculus Home, you will be prompted to close the application. If you select OK, Unity might remain in a state where it is running, but will never get focus. To work around this, restart Unity.