Unity 4 Integration Release (0.6.0.2) & Important Notice
As you may be aware, the new Oculus 0.7 Runtime package will release on August 20th. This release is a major improvement, and introduces Direct Driver Mode, which will improve stability, performance, and latency. However, these architectural changes mean it will no longer support applications built with Unity 4 using older integration packages. This is important for developers to understand, as any PC application built using Unity 4 will not function once end-users update to the 0.7 Runtime. If you are currently using Unity 4, you will have two options for ensuring your application continues to function with the 0.7 Runtime.
The preferred path would be to update to Unity 5 and use the built-in VR support. In this case, you would not use the integration package, but can use the Oculus Utilities for Unity to bring back certain functionality previously in the integration. Unity 5 is the better option as you will continue to receive the latest features for Oculus moving forward.
In the case that you’re not able to upgrade to Unity 5, it will be necessary to build your project against the new 0.6.0.2 Unity 4 Integration. This new package will work with the Oculus 0.7 Runtime. It’s vital that you update your project immediately to ensure that end-users are able to continue using your application once they install the 0.7 Runtime.
If you haven’t started your project yet, then the best path to take is to start working with Unity 5 and using the built-in VR support.
In either case, if you have an application on Oculus Share, you will be required to resubmit the updated files after rebuilding your project.
The new 0.6.0.2 integration package is available here: https://developer.oculus.com/downloads/
Please let me know if you have any questions or comments. Thanks.
The preferred path would be to update to Unity 5 and use the built-in VR support. In this case, you would not use the integration package, but can use the Oculus Utilities for Unity to bring back certain functionality previously in the integration. Unity 5 is the better option as you will continue to receive the latest features for Oculus moving forward.
In the case that you’re not able to upgrade to Unity 5, it will be necessary to build your project against the new 0.6.0.2 Unity 4 Integration. This new package will work with the Oculus 0.7 Runtime. It’s vital that you update your project immediately to ensure that end-users are able to continue using your application once they install the 0.7 Runtime.
If you haven’t started your project yet, then the best path to take is to start working with Unity 5 and using the built-in VR support.
In either case, if you have an application on Oculus Share, you will be required to resubmit the updated files after rebuilding your project.
The new 0.6.0.2 integration package is available here: https://developer.oculus.com/downloads/
Please let me know if you have any questions or comments. Thanks.