Version 1.38 of our integration for Unity has been released!The Oculus Integration for Unity package adds scripts, prefabs, samples, and other resources to supplement Unity’s built-in support. The package includes an interface for controlling VR camera behavior, a first-person control prefab, a unified input API for controllers, advanced rendering features, object-grabbing and haptics scripts for Touch, debugging tools, and more. For more information, see our Unity Getting Started Guide.You can grab the latest version of our Unity Integration here (through the Unity Asset Store): https://assetstore.unity.com/packages/tools/integration/oculus-integration-82022More information, as well as general known issues with Unity, about this release can be found here.New FeaturesAdded Mixed Reality Capture support for Oculus Quest.Integration GuideSetup and User GuideThe Oculus Unity Integration supports Unity’s XR SDK preview. More information about the XR SDK can be found on Unity's forum post.Integration ChangesUpdated the Oculus Unity Integration to 1.38, including:Updated the LipSync integration to 1.38Updated the Audio Spatializer to 1.38API UpdatesBreaking change: the OVROverlay prefab now requires an instance of the OVRManager prefab to be present. Apps that wish to update to 1.38 or later may be required to add OVRManager.Renamed the TiledMultiRes setting to FixedFoveatedRendering.Known IssuesAll Unity 2018.2 versions(Mobile) You'll need to either switch the AndroidBuildSystem to internal or export a Gradle project and modify the SigningConfig in the build.gradle file to include v1SigningEnabled=true, v2SigningEnabled=false.2018.2.20f1(Mobile) Some game objects may appear darker when loaded in 2018.2.20f1. To work around this issue, load the project in another version of Unity, like 2018.2.19.Other Known IssuesPlease read the release notes in their entirety here: https://developer.oculus.com/downloads/package/unity-integration/The thread for the previous version (v1.37) can be found here: https://forums.oculusvr.com/developer/discussion/75863/oculus-unity-integration-v1-37-05-21-19

Does Oculus staff even read these posts? I've not seen a single issue brought up here ever get a response.I'll throw mine in here anyway. The LocomotionTeleport setup doesn't work with the Character Controller Constraint as it should. When teleporting to a point lower in elevation than your current position, the player is moved to the correct XZ coordinate, but the Y coordinate remains that of their previous position. Then the player either drops or floats, depending on gravity settings.Disabling the Constraint component resolves the Y axis issue, but then you don't get roomscale adjustments, wall clipping protection, and snap rotations rotates you around a point outside the character. I've seen Oculus staff mention before that if you're doing roomscale, you shouldn't be using the OVRPlayerController component, but both the LocomotionTeleport and camera constraint component require it to be used...Honestly, it really feels like there needs to just be an Oculus Integration 2.0 that starts things from scratch, because this package seems to become more of a mess each update. Just my frustrated two cents, though.

What is the purpose of creating this form if devs do not read it?

rocketchicken said: 1.38 seems to break OVRHeadsetEmulator. This conditional is never set in OVRManager.cs: if (OVRPlugin.initialized || (Settings.enabled && Settings.loadedDeviceName == OPENVR_UNITY_NAME_STR)) { InitOVRManager(); }Is there something else we should be doing in the setup that's not described in the documentation?Same issue here. Never returns true so InitOVRManager is never called. Breaks the headset emulator but there'd be numerous other issues, since the static 'instance' is never set, so OVRManager can't be called. Will roll this update back.

This is going to sound really nit picky, but I noticed that some of the files in the SDK are indented with spaces, some are indented with tabs, some have brackets on the same line, some have brackets on a newline. OculusPlatformSettingsEditor.cs is even indented with 2 spaces!Can you guys just have a coding style battle royale and unify on something, please?(You probably didn't even know you were eating lunch next to someone who indents using spaces.)

1.38 seems to break OVRHeadsetEmulator. This conditional is never set in OVRManager.cs: if (OVRPlugin.initialized || (Settings.enabled && Settings.loadedDeviceName == OPENVR_UNITY_NAME_STR)) { InitOVRManager(); }Is there something else we should be doing in the setup that's not described in the documentation?

mouse_bear

Retired Support

7 years ago

Oculus Unity Integration - v1.38 (06/21/19)

Version 1.38 of our integration for Unity has been released!

The Oculus Integration for Unity package adds scripts, prefabs, samples, and other resources to supplement Unity’s built-in support. The package includes an interface for controlling VR camera behavior, a first-person control prefab, a unified input API for controllers, advanced rendering features, object-grabbing and haptics scripts for Touch, debugging tools, and more. For more information, see our Unity Getting Started Guide.

You can grab the latest version of our Unity Integration here (through the Unity Asset Store): https://assetstore.unity.com/packages/tools/integration/oculus-integration-82022

More information, as well as general known issues with Unity, about this release can be found here.

New Features

Added Mixed Reality Capture support for Oculus Quest.
- Integration Guide
- Setup and User Guide
The Oculus Unity Integration supports Unity’s XR SDK preview. More information about the XR SDK can be found on Unity's forum post.

Integration Changes

Updated the Oculus Unity Integration to 1.38, including:
- Updated the LipSync integration to 1.38
- Updated the Audio Spatializer to 1.38

API Updates

Breaking change: the OVROverlay prefab now requires an instance of the OVRManager prefab to be present. Apps that wish to update to 1.38 or later may be required to add OVRManager.
Renamed the TiledMultiRes setting to FixedFoveatedRendering.

Known Issues

All Unity 2018.2 versions

(Mobile) You'll need to either switch the AndroidBuildSystem to internal or export a Gradle project and modify the SigningConfig in the build.gradle file to include v1SigningEnabled=true, v2SigningEnabled=false.

2018.2.20f1

(Mobile) Some game objects may appear darker when loaded in 2018.2.20f1. To work around this issue, load the project in another version of Unity, like 2018.2.19.

Other Known Issues

Please read the release notes in their entirety here: https://developer.oculus.com/downloads/package/unity-integration/

The thread for the previous version (v1.37) can be found here: https://forums.oculusvr.com/developer/discussion/75863/oculus-unity-integration-v1-37-05-21-19

28 Replies

Replies have been turned off for this discussion

Anonymous
7 years ago
Fixed Foveated Rendering (FFR) is broken in the lightweight render pipeline (LWRP) for Oculus Quest. Is this a known issue?
Anonymous
7 years ago
Also, there's a bug in GetOculusProjectConfigAssetPath() if you have spaces in your path.

Line 55 should be:
// Because spaces become %20 in Uris
return Uri.UnescapeDataString(relativeUri.ToString());
FretBuzzBoogie
Honored Guest
7 years ago
GearVR Unity 2018.2.20f1

On upgrading from v1.37 to v1.38, while trying standalone on editor I have lost the emulator support, then I checked in OVRManager.cs Line 1297
if (OVRPlugin.initialized || (Settings.enabled && Settings.loadedDeviceName == OPENVR_UNITY_NAME_STR))

I get OVRPlugin.initialized = false and Settings.loadedDeviceName = "", so OVRManager is never initialized.

Also, the IAP bug is not yet fixed.
You cannot purchase two items. On second purchase when IAP item is selected and the window goes to oculus home to purchase the item, the window transitions back to the game without the callback being called.
tyounanmoti
Honored Guest
7 years ago
Not worked on Unity 2019.1.4f1 and 2018.3.13f1 with following warning log.

Virtual Reality SDK Oculus failed to initialize.
Will attempt to enable None instead
Anonymous
7 years ago
This is going to sound really nit picky, but I noticed that some of the files in the SDK are indented with spaces, some are indented with tabs, some have brackets on the same line, some have brackets on a newline. OculusPlatformSettingsEditor.cs is even indented with 2 spaces!

Can you guys just have a coding style battle royale and unify on something, please?

(You probably didn't even know you were eating lunch next to someone who indents using spaces.)
huangjun
Protege
7 years ago
Is there any infomations about body tracking & share space？
Abnormalia
Protege
7 years ago
Are you guys going to fix editor "Virtual Reality SDK Oculus failed to initialize" BUG or is there some workaround for now ?
preston_mccaule
Protege
7 years ago
I'm using the new build, when I deploy to my device it looks like my developer build is running (using the same distance grab scene) I get the loading dots, then it just crashes back to home... - anyone get this working yet?
Abnormalia
Protege
7 years ago
Unity (2019.1.8f) Create New 3D project, Integrate 1.38 - Runs fine
Switch Platform to Android, Run not working, no tracking, no Unity in headset (Oculus CV1)
Switch Platform back to windows - Not working, same as above

Which is most stable version for quest development until its fixed ?
Anonymous
7 years ago

tyounanmoti said:

Not worked on Unity 2019.1.4f1 and 2018.3.13f1 with following warning log.

Virtual Reality SDK Oculus failed to initialize.
Will attempt to enable None instead

I've been having the same issue on Unity 2019.1.8f1. However, it was running just fine for a while on Tuesday... I think it was Tuesday. I didn't change a thing but the SDK v1.38.0 was showing up in console as it should. Now I am seeing what is in the attached screenshot.

In any case, I have included OpenVR and Unity will fallback to that for running in the Editor. This will allow you to continue development at least. If using a LocalAvatar, the finger animations will not match the controller.

This particular project is setup for Quest and I have been using my Rift S for checking progress. This has not caused any issues with building and pushing an APK to the device.

@NinjaGaijin
Any ideas on why the SDK is intermittently initializing? I've noticed others having this issue too.