Forum Discussion
Oculus Utilities for Unity 5 1.8.0 Released
Oculus Utilities for Unity 5
This document provides an overview of new features, improvements, and fixes included in the latest version of the Oculus Utilities for Unity 5. For information on first-party changes to Unity VR support for Oculus, see the Unity Release Notes for the appropriate version. You will find an updated scripting reference for the included C# scripts in our Unity Developer Reference.
If you have previously imported a Unity integration package, you must delete all Oculus Integration content before importing the new Unity package. For more information, seeImporting the Oculus Unity Package.
Note: Due to issues with earlier releases, we now recommend all developers update to 5.3.6p5 or version 5.4.1p1 or later.
New Features
- Added support for the Oculus Guardian System, which visualizes the bounds of a user-defined Play Area. Note that it is currently unsupported by public versions of the Oculus runtime. SeeOVRBoundary for more information.
- Added underlay support allowing VR compositor layers to be rendered behind the eye buffer.
- Added support for stereoscopic cubemap VR compositor layers (mobile only).
API Changes
- Added OVRBoundary API for interacting with the Oculus Guardian System.
- Removed OVRTrackerBounds.
Bug Fixes
- Fixed blackscreen issue related to unplugging the HDMI cable and re-plugging it back in.
- Fixed Touch judder issue.
Known Issues
- Due to issues with earlier releases, we now recommend all developers update to 5.3.6p5 or version 5.4.1p1 or later.
- Gear VR
- Mobile developers should not use Unity versions 5.3.6p1-2 and 5.4.0p1-2 due to incorrect positional movement of the head.
- Unity 5 automatically generates manifest files with Android builds that will cause them to be automatically rejected by the Oculus Store submission portal. If this is blocking your application submission, please let us know on our Developer Forum and we will work with you on a temporary workaround.
- Gear VR developers using Unity 5.3.4 or later, or using Unity 5.4.0b16 and later: Do not set DSP Buffer Size to Best in Audio Manager in the Inspector for now or you will encounter audio distortion. Set it to Good or Default instead.
13 Replies
Replies have been turned off for this discussion
Important Note: Due to issues with earlier releases, we now recommend all developers update to 5.3.6p5 or version 5.4.1p1 or later.
- Hi,
Do you have any idea when a fix for the issue below will be available?
"Gear VR
Mobile developers should not use Unity versions 5.3.6p1-2 and 5.4.0p1-2 due to incorrect positional movement of the head."
Also can you give more detailed information about it? We are using 5.4.1 and there doesn't appear to be any new issue with head movement.
Thanks - Hi,
Do you have any idea when a fix for the issue below will be available?
"Gear VR
Mobile developers should not use Unity versions 5.3.6p1-2 and 5.4.0p1-2 due to incorrect positional movement of the head."
Also can you give more detailed information about it? We are using 5.4.1 and there doesn't appear to be any new issue with head movement.
Thanks - Hey,
I am running into a blocker issue on some of our machines where the OVRPlugin.dll fails to load. The error I am seeing is as follows:
Failed to load 'C://build/standalonewindows/profile/Game_Data/Plugins/OVRPlugin.dll' with error 'The specified module could not be found.
This started happening after integrating Oculus Utilities 1.8, Platform SDK 1.8 and upgrading to Unity 5.4.1.p1. I still haven't had any luck trying to find the root cause. Anyone know what might be happening here? - And to clarify, in the editor the game runs fine, the issue exists only in builds.
- > Gear VR Mobile developers should not use Unity versions 5.3.6p1-2 and 5.4.0p1-2 due to incorrect positional movement of the head.
This was resolved in 5.3.6p3 and 5.4.0p3 and up. The problem was a flipped translation along the z axis, resulting in visibly incorrect head movement relative to close-up objects on Gear VR.
> Failed to load 'C://build/standalonewindows/profile/Game_Data/Plugins/OVRPlugin.dll' with error 'The specified module could not be found.
Please make sure you've enabled VR support and added Oculus to the list of supported devices in Player Settings. There is a bug in Unity 5.4 that sometimes causes the settings to be lost after upgrading from prior versions. - >Please make sure you've enabled VR support and added Oculus to the list of supported devices in Player Settings. There is a bug in Unity 5.4 that sometimes causes the settings to be lost after upgrading from prior versions.
They are correctly setup in the Player Settings and it is affecting only some of our machines. So I know for sure the build does work. - Can you confirm OVRPlugin.dll exists in the _Data folder of your built player? If not, try disabling VR support and then re-enabling it.
- Yes it exists. I can PM you the log file if that helps.
- Thanks, that would help. I assume you are using Rift Runtime 1.8.
