VIVE Wave™ SDK provides a suite of Virtual Reality APIs to introduce VR content applications on mobile device to independently work with VR accessories. VR content developers have no need to pick up the specific VR hardware knowledge and can concentrate on the content core design.
VIVE Wave™ SDK adopts the client-server architecture. The content application in client side works with server via IPC connection and the IPC interface is backward compatible. The client content application does not need to re-compile for the further server upgrade. They are totally transparent for the maintenance of version forward in the future.
Init and Quit¶
Consider that content applications access VR stack flexibly in the suitable time of content lifecycle. VIVE Wave™ does not automatically initiate or destroy VR instance for content app. The content app must invoke WVR_Init function prior to any VR operations and invoke WVR_Quit to release the VR resource finally.
VIVE Wave™ API includes the following interfaces:
- WVR Device : Main interface for the device state, tracking pose, and user input of tracked device.
- WVR Event : Common Event Access
- WVR Arena : Interfaces to access the settings of Arena.
- WVR Display : Interfaces about the model view transform and projection.
- WVR Render : Interfaces about controlling render thread and updating render target to display.
- WVR System : Interfaces to get the system status of VR runtime.
- WVR Overlay : Interface to draw 2D images over 3D scenes.
- WVR Vulkan : Interface to integrate with Vulkan application.
- WVR Controller Model : Interface to get controller model or emitter information of current connected controller.
- WVR Hand : Interface to get hand tracking data of VR runtime.
- WVR Hand Model : Interface to get hand model data of VR runtime.
- WVR Tracker : Interface to get tracker data of VR runtime.
- WVR Eye : Interfaces to get eye tracking pose data.
- WVR Lip : Interfaces to get lip expression data.
- WVR Notify DeviceInfo : Interfaces Let AP notify DS information.