WaveVR API Level

Introduction

WaveVR SDK provides APIs, scripts and prefabs for feature development, but these components need corresponding API levels to take effect.

Please refer to Wave VR Version List for a mapping table of WaveVR SDK version vs. API level.

We list the feasible and effective API levels of components here.

  • Feasible: usable, but limited.
  • Effective: fully supported.

Prefab

WaveVRButtons : please refer to Buttons

  • Feasible: level 3
  • Effective: level 3

InputModuleManager : please refer to Input Module Manager

  • Feasible: level 2
  • Effective: level 2

ControllerLoader : please refer to WaveVR_ControllerLoader

  • Feasible: level 1
  • Effective: level 2

Script

WaveVR_ControllerInstanceManager : please refer to WaveVR_ControllerInstanceManager (new in SDK 3.0)

  • Feasible: level 2
  • Effective: level 2

WaveVR_ControllerInputModule : please refer to WaveVR_ControllerInputModule

  • Feasible: level 1, 2 controllers take effects concurrently.
  • Effective: level 2, only 1 controller takes effect.

API

WaveVR_Controller.Input().TriggerHapticPulse: please refer to WaveVR_Controller

  • Feasible: level 1, vibrates less than 0.1s in each time usage.
  • Effective: level 4

Other feature

Adaptive Quality: please refer to AdaptiveQuality

  • Feasible: level 4,
  • Effective: level 4