Missing scripts/broken references on prefabs in Oculus Interaction 46
Inside the following prefabs: Assets/Oculus/SampleFramework/Usage/Prefabs/UIOverlay.prefab Assets/Oculus/SampleFramework/Usage/DistanceGrab/Prefabs/DistanceGrabSquirtGunPf.prefab Assets/Oculus/SampleFramework/Usage/SceneManager/Prefabs/Couch.prefab Assets/Oculus/SampleFramework/Usage/SceneManager/Prefabs/Desk.prefab Assets/Oculus/Spatializer/scenes/Standard Assets/Character Controllers/3rd Person Controller.prefab Assets/Oculus/Spatializer/scenes/Standard Assets/Character Controllers/First Person Controller.prefab1.5KViews3likes1CommentUnity Alert: Integration 1.32 compile issue (01/07/19)
We have been receiving reports of an issue when attempting to compile with the current integration (v1.32) offered on the Unity Asset Store: Assets\Oculus\Avatar\Scripts\OvrAvatarSkinnedMeshRenderPBSV2Component.cs(4,23): error CS0234: The type or namespace name 'Policy' does not exist in the namespace 'System.Security' (are you missing an assembly reference?) Our team is aware of the issue and working to rectify it. For the time being, this can be fixed by opening the Assets\Oculus\Avatar\Scripts\OvrAvatarSkinnedMeshRenderPBSV2Component.cs file and commenting out/removing the following line (line 4) highlighted in bold: using UnityEngine; using System.Collections; using System; using System.Security.Policy; using Oculus.Avatar;767Views3likes1CommentOculus Integration for Unity - v1.34 (01/31/19)
Version 1.34 of our integration for Unity has been released. We highly encourage developers who are using v1.32 of our integration to upgrade to v1.34. Developers using previous Unity 2018.3 versions, we also encourage you to upgrade to Unity 2018.3.3f1 immediately due to compatibility issues. 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 about this release can be found here. 1.34 Update Notes Unity has released 2018.3.3f1 that resolves the issues encountered in versions 2018.3.1 and 2018.3.2. If you’re using any previous 2018.3 versions, we recommend upgrading to 2018.3.3f1 immediately. If you use 2018.3.3f1 for Oculus development you’ll need to verify that Oculus (Standalone) is installed in the Package Manager. New Features Updates to OVROverlay that include a GUI redesign and new features. Details about the updates and new features are detailed in VR Compositor Layers & OVROverlay. Added the ability to ‘Override Color Scale’ on an OVROverlay layer, allowing you to change the color offset and scale on layers independent of the global color settings. For any given overlay, global settings will apply unless ‘Override Color Scale’ is selected, in which case the specified overridden color scale will be used. Added the ability to opt out of “Use Default Rects” and define a texture input that contains stereo images in a single texture. Added support for uploading language packs, asset files, and obbs to the CLI. For more information, please see the Custom Items page in the Platform SDK guide. Added UI in OVRManager to setup the target Oculus devices (Android development only). Integration Changes The Unity Integration 1.34 contains the following changes to the Oculus Integration for Unity package: Update the Oculus Utilities to 1.34 Update the Platform SDK to 1.34 Update the Audio Spatializer to 1.34 Sample Changes No changes to the SampleFramework included in this release. Bug Fixes General performance improvements/fixes.3.5KViews3likes8CommentsCan't use the Platform in Standalone Mode, and Users.GetLoggedInUser() does not work.
I want to get Data of logged in Oculus user, so I went to this page documentation/unity/ps-setup/ and tried to activate "Use Standalone Platform", but that checkbox was disabled. Also the following script does not work on the first line. Users.GetLoggedInUser() seems to be NULL. How do I get it to work in Standalone mode? void Start() { Users.GetLoggedInUser().OnComplete((Message<User> uMsg) => { if (uMsg.IsError) { Debug.Log("Platform: GetLoggedInUser() failed. Reason: " + uMsg.GetError().Message ); return; } else { User _localUser; _localUser = uMsg.Data; Debug.Log(_localUser.DisplayName); } }); } [Using game engine and Oculus SDK] Unity 2019.4.18f1 (LTS), Oculus SDK 1.55.12.6KViews1like4CommentsOculus Unity Integration - v1.39 (07/26/19)
Version 1.39 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 Updates Mixed Reality Capture support: Updates to the Oculus Quest Mixed Reality Tools package. Added support to change the backdrop color of your Mixed Reality Capture foreground. The Unity Profiler now supports GPU profiling on Oculus Quest and Oculus Go, see the Testing and Performance Analysis page for additional information. Integration Changes Updated the Oculus Unity Integration to 1.39, including: Updated the Audio Spatializer to 1.39 Updated the Lipsync integration to 1.39 Updated the Platform integration to 1.39 Updated the Avatar integration to 1.39 Known Issues Please read the release notes in their entirety here: https://developer.oculus.com/downloads/package/unity-integration/ Previous versions of the Unity Integration can be found here: https://developer.oculus.com/downloads/package/unity-integration-archive/ The thread for the previous version (v1.38) can be found here: https://forums.oculusvr.com/developer/discussion/77572/oculus-unity-integration-v1-38-06-21-197.5KViews1like25CommentsOculus Unity Integration - v1.42 (10/23/19)
Version 1.42 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 1.42 is a maintenance release. There are no new features in this release. Integration Changes Updated the Oculus Unity Integration to 1.42, including: Updated the Audio Spatializer to 1.42 Updated the LipSync integration to 1.42 Updated the Platform integration to 1.42 Updated the Avatar integration to 1.42 Importing the latest Oculus Integration When importing a new version of the Oculus Integration into an existing project, follow the steps on Importing the Oculus Utilities Package to ensure a smooth upgrade experience. Known Issues Please read the release notes in their entirety here: https://developer.oculus.com/downloads/package/unity-integration/ Legacy Unity Release Archive Legacy versions of the Unity Integration can be found in the Unity Integration Archive. The thread for the previous version (v1.41) can be found here: https://forums.oculusvr.com/developer/discussion/81420/oculus-unity-integration-v1-41-10-03-193.3KViews1like6CommentsOculus Unity Integration - v1.40 (08/29/19)
Version 1.40 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 Updates to the Oculus Quest Mixed Reality Tools package. Added Late Controller Update to OVRManager. pdates the pose of the controllers immediately before rendering, for lower latency between real-world and virtual controller movement. Updated the behavior of Use Recommended MSAA Level in OVRManager. This setting is now enabled by default. OVRDisplay.RecenteredPose: Is now supported on Quest. The event is sent anytime a user recenters. Removed the requirement to manually generate an AndroidManifest.xml file with the headtracking manifest flag for Oculus Quest support. Simply adding "Oculus Quest" to the list of target devices in OVRManager will update the manifest file. Integration Changes Updated the Oculus Unity Integration to 1.40, including: Updated the Audio Spatializer to 1.40 Updated the Lipsync integration to 1.40 Updated the Platform integration to 1.40 Importing the latest Oculus Integration When importing a new version of the Oculus Integration into an existing project, follow the steps on Importing the Oculus Utilities Package to ensure a smooth upgrade experience. Known Issues Please read the release notes in their entirety here: https://developer.oculus.com/downloads/package/unity-integration/ Legacy Unity Release Archive Legacy versions of the Unity Integration can be found in the Unity Integration Archive. The thread for the previous version (v1.39) can be found here: https://forums.oculusvr.com/developer/discussion/79116/oculus-unity-integration-v1-39-07-26-197.2KViews1like23CommentsOculus 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-199.3KViews1like28CommentsUsing the Oculus Integration with Unity 2018.3.x.
The Oculus Integration is incompatible with the latest versions of the Unity Editor (2018.3.x). We do not recommend using any 2018.3.x versions for Oculus development. If you choose to use 2018.3.x and/or need to fix your project already in 2018.3.x, here are the workaround steps: - Follow the steps on Importing the Oculus Utilities Package (https://developer.oculus.com/documentation/unity/latest/concepts/unity-import/) to remove the existing Oculus Integration package. - Open your project and navigate to the Package Manager (Windows / Package Manager). Then install the Oculus (Standalone) package (it will be an older version #, probably 1.29.0). Do NOT install the Oculus (Android) package. - Open the Asset Store tab and import the Oculus Integration, now 1.32.1.6.5KViews1like9CommentsOculus Unity Integration - v1.37 (05/21/19)
Version 1.37 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 The 1.37 Oculus Integration for Unity adds development support for the Rift S headset. Integration Changes Updated the Oculus Unity Integration to 1.37, including: Updated the LipSync integration to 1.37 Integration Changes 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. General Unity Known Issues For more information on the known issues with this version of the integration, please read the full release notes here. The thread for the previous version (v1.36) can be found here: https://forums.oculusvr.com/developer/discussion/74996/oculus-unity-integration-v1-36-04-23-196.5KViews1like18Comments