On this Page
This section details migrating from earlier versions of the Mobile SDK for native development.
Note: For information on releases older than listed, see Mobile Native Migration Guide - Archive.
This section is intended to help you upgrade from the Oculus Mobile SDK version 1.24.0 to 1.25.0.
There are no developer-facing changes in this release.
VRAPI_EXTRA_LATENCY_MODE_OFFhas been resolved.
This section is intended to help you upgrade from the Oculus Mobile SDK version 1.23.0 to 1.24.0.
This release adds support for several new Vulkan features, all of which are demonstrated in the VrCubeWorld_Vulkan sample included with the SDK. These features are as follows:
Additionally, protected content rendering is now supported on both Oculus Quest and Oculus Go.
vrapi_CreateAndroidSurfaceSwapChain2function has been added to create an Android Surface SwapChain as a protected resource.
vrapi_GetTextureSwapChainBufferFoveationVulkanfunction has been added to acquire the foveation Vulkan image associated with the SwapChain.
VRAPI_SYS_STATUS_USER_RECENTER_COUNT, has been added for retrieving the number of user-initiated recenter operations.
VRAPI_FRAME_LAYER_FLAG_FILTER_EXPENSIVE, has been added to enable expensive filtering for a layer. This option is only useful for 2D layers that are high resolution (such as a remote desktop layer), typically double or more the target resolution.
vrapi_GetEyeViewMatrixhas been removed from
GetEyeViewMatrixfor a valid replacement.
LibOVRKernel has been removed from the SDK. Most
LibOVRKernel usage was replaced by the C++11 Standard Library equivalent. Any functionality that was not replaced was moved into header files at 1stParty/OVR/Include.
This section is intended to help you upgrade from the Oculus Mobile SDK version 1.22.0 to 1.23.0.
This release provides support for Samsung Galaxy S10 smartphone.
ovrTrackingStatusflags were added:
VRAPI_TRACKING_STATUS_ORIENTATION_VALID. Prior to these status bits, it was unclear how to treat orientation and position data when the
TRACKEDstatus bits were unset. The new
VALIDbits indicate whether the value delivered is usable for rendering or other computation. When the
TRACKEDbit is unset, but the
VALIDbit is set, the provided pose is usable, but is the result of some model or estimation heuristic.