Oculus Developer Release Notes: v32

Oculus Integration for Unity - v32

• This release focuses on bug fixes and improvements. No new features are released in this version.

• Improved stability to controller haptics in the OpenXR backend
• Screen flickering issues that appeared on Vulkan
• Random black sreen that appeared after multiple power cycles or when a user enters or leaves the guardian boundary in the OpenXR backend
• PC MRC having a wider background than foreground when using external composition with URP
• A swimming effect with some objects in the scene, which could have otherwise caused discomfort
• PC Compositor layers being upside down in the OpenXR backend
• PC Compositor layers throwing an error in the OpenXR backend

• OVRLint tool now clearly exposes the categories of issues it checks, which aids developers with better discoverability of issues
• Added a dialog box that confirms the selection whether you want to use the OpenXR backend when upgrading the OVRPlugin

• GetAdaptiveGPUPerformanceScale is deprecated

• If you're using the Spectator Camera feature and you switch the view, the casting video is flipped upside down. Workaround: Set SetMrcFrameImageFlipped to false. For more information, see the Known Issues section in the Spectator Camera user guide.
• Vulkan Quest apps may crash when you select Use Recommended MSAA Level setting in OVRManager. Workaround: Clear Use Recommended MSAA Level check box in OVRManager and manually set the appropriate MSAA level (recommended 4x) in Project Settings > Quality
• Vulkan Quest apps crash when you request audio permissions after the splash screen is loaded.
• Changing modes in Lipsync_Demo on Oculus Quest is currently not supported.
• Unity has a known issue such that parenting one VR camera to another will compound tracking twice. As a workaround, make them siblings in the GameObject hierarchy
• Using Unity Universal Render Pipeline will not set the MSAA level automatically.

• Support for hand-tracking is currently restricted to the baseline OpenXR spec. Therefore, additional hand-tracking features such as collision capsules, hand input metadata, and runtime hand meshes are not yet supported. In addition, there is a known compatibility issue with the thumb trapezium bone (Thumb0) in the OpenXR-based OVRPlugin. Due to the known compatibility issues with hand-tracking and haptics, Oculus Store and App Lab will not accept apps built with v31.x SDK and OpenXR backend. Workaround: Hand tracking features are fully functional with the legacy VRAPI backend. If you want to submit apps to Oculus Store or App Lab, you must switch to the legacy backend. In the Unity editor, go to the Oculus > Tools > OpenXR > Switch to Legacy OVRPlugin menu to switch to the VRAPI backend to continue using hand tracking features. Find detailed information in the Switch between OpenXR and Legacy VRAPI documentation.
• Mixed Reality Capture on Rift is not supported in OpenXR. Workaround: In the Unity editor, go to the Oculus > Tools > OpenXR > Switch to Legacy OVRPlugin menu to switch to the VRAPI backend to continue using Rift MRC. Find detailed information in the Switch between OpenXR and Legacy VRAPI documentation.
• GetAppPerfStats and ResetAppPerfStats are currently not supported with the OpenXR backend. Workaround: In the Unity editor, go to the Oculus > Tools > OpenXR > Switch to Legacy OVRPlugin menu to switch to the VRAPI backend to continue using Rift MRC. Find detailed information in the Switch between OpenXR and Legacy VRAPI documentation.

• You may experience long UI stalls or poor performance with the Unity editor when targeting Oculus Rift on Windows 10. Workaround: Run Windows update to ensure that you have the latest version of Windows 10.
• The combination of all Unity versions with Oculus runtime 1.17 and higher and Windows 10 + Creators Update results in spurious WM_DEVICECHANGE reports in the editor, even in non-VR projects. You may not notice any impact, but if you're connected to certain USB devices, you may find the Unity editor becomes non-responsive and you needs to terminate it from Task Manager. Workaround: Update to the Beta runtime available on our Public Test channel. We are currently working with Unity and Microsoft on a permanent solution.

• Currently, in the Guardian System API, ovr_SetBoundaryLookAndFeel does not take effect if the headset is not worn when the call is made (e.g., on start).
• Transparent VR Compositor Layers do not currently support multiple layers of occlusion.

Unreal Engine 4 Integration

• Unreal 4.27 (Latest) ⁠
  Note: If you are not logged on to GitHub with an account subscribed to the private repository, you will get a 404 error when accessing the link.

• OVRPlugin updated to 1.64.0
• Symmetrical rendering is now available as a Quest2 specific GPU optimization activated with the CVAR r.Mobile.Oculus.ForceSymmetric. Performance gains come from reusing vertex shader and cache that is possible due to the shared geometry between left and right eyes when using multiview. Gains are scene dependent and increase if using FFR and the wearer has low to mid range IPD.
• (Experimental) You can debug UE4.27 C++ projects on Oculus devices using Visual Studio with the AGDE plugin by attaching to a process.
• For C++ projects only
• The heapprofd option must be off in the Android > Advanced Build options
• You must generate a .sln file with AGDE settings turned on, for example:
  C:\project\GenerateProjectFiles.bat
  C:\project\MyVRProject.uproject -vsdebugandroid -Game -Engine

• Foveation now works on Vulkan when using the OVRPlugin OpenXR backend.
• Fixed stability and life cycle issues in the OVRPlugin OpenXR backend.
• Fixed default tracking space origin when using the OVRPlugin OpenXR backend.

• Oculus_Quest and Oculus_Quest2 have been added as Android Device Profiles. To future proof apps, we recommend using Device Profiles to enable device-specific settings instead of using code like if(Quest1).
• The default color space for new projects has been changed to Rift CV1 to simplify color space selection.
• Additional GPU optimization lowers timewarp cost by up to 0.3ms.
• We no longer package Android NDK Vulkan Validation Layers. Use the Vulkan Validation Layers built into the Oculus VR OS instead.
• VSCode debugger files are now generated automatically at APK launch time, you no longer need to launch GenerateProjectFiles.bat -VSCode.

• Oculus Store and App Lab will not accept apps built with v31 or v32 SDKs and the OVRPlugin OpenXR backend due to a known compatibility issue with hand tracking and haptics. To submit apps to Oculus Store or App Lab, you must change Project Settings > Plugins- OculusVR > XR API to Legacy OVRPlugin.
• Hand tracking in the OVRPlugin OpenXR backend is currently restricted to the hand tracking features defined in the OpenXR specification, and Oculus hand tracking features such as collision capsules, hand input metadata, and runtime hand meshes are not available. In addition, there is an issue with the Thumb0 thumb trapezium in the OVRPlugin OpenXR backend. Oculus hand tracking features are fully functional in the Legacy OVRPlugin backend, which you can enable in Project Settings > Plugins- OculusVR > XR API.
• Mixed Reality Capture (MRC) on Oculus Rift is not supported in the OpenXR backend. If you need to use MRC, change Project Settings > Plugins- OculusVR > XR API to Legacy OVRPlugin.

Platform SDK

• New ovrChallengeEntryGetID function to make it easier to delete Challenges. See more in the Challenge Entry reference.
• New ovrLeaderboardEntryGetID function to make it easier to delete Leaderboards. See more in the Leaderboard Entry reference.

Mobile SDK

• This is a maintenance release. There are no developer-facing changes in this release.

• There are no developer-facing improvements in this release.

• There are no major bug fixes in this release.

Other Developer Updates

• A marketing attribution dashboard was recently added to help you track how effective your marketing efforts are. For more information, see Marketing Attribution Analytics.