Important Unity 6 information

[GoodGameGomez]

UPDATE (10/23): 

Please update to version 69.0.1 of the Meta XR Core SDK. This update resolves the known issue associated with input registration and headlocking.

With the release of Unity 6*, we’ve identified the following regressions:

1) Quest developers may experience a lack of input registration and headlocking when playing in editor, if their projects are using Unity OculusXR Plugin (com.unity.xr.oculus) along with the current Meta XR Core SDK package releases. We are going to resolve this issue promptly in the next patch release of the Meta XR Core SDK package (v69.1). Please update this through the Unity Package Manager when it becomes available.

In the meantime, Unity is providing the following workaround that resolves this issue. 

1. Open a new or existing project with the Meta XR Core SDK package installed. 
2. Navigate to the project Asset folder and locate the folder containing OVRPlugin.dll, along with the OVRPlugin.dll.meta file. 
3. Replace OVRPlugin.dll.meta with the attached file from Unity's forum post.
4. Restart the project and the observed issues will be resolved.

2) Significant screen distortion when Dynamic Resolution is enabled, and when changing the viewport scale with “XRSettings.renderViewportScale”. We are working with Unity to resolve this in the next Unity 6 update. There is currently no manual workaround available for this issue.

Let us know if you have any further questions in this thread. 

*Known affected versions of Unity 6:

• 6000.0.22f1

• 6000.0.23f1

[OdontMast]

There is also an issue with the Voice SDK where I'm getting "java.lang.NullPointerException: Attempt to read from field 'android.os.MessageQueue android.os.Looper.mQueue' on a null object reference" when AppDictationExperience initializes. This topic on Unity Discussions seems relevant: https://discussions.unity.com/t/voice-sdk-crash-on-activate-meta-quest-3/935246

[ratmat2000]

I was able to fix this after updating AWS to the latest AWS SDK for .NET and deleting the previous Microsoft.Bcl.AsyncInterfaces.dll

I'm experiencing an assembly reference problem when installing both the 69.0.1 Meta XR Core SDK package and the latest AWSSDK.CognitoSync.3.3.100.222 package:

Library/PackageCache/com.meta.xr.sdk.core/Scripts/Util/Async/OVRTask.cs(869,17): error CS0433: The type 'ManualResetValueTaskSourceCore<TResult>' exists in both 'Microsoft.Bcl.AsyncInterfaces, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' and 'netstandard, Version=2.1.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'

The AWS package includes the Microsoft.Bcl.AsyncInterfaces DLL causing this conflict and I'm not sure if there is any way to resolve this.

[ImmersiveMatthew]

I followed the above instructions and now I get the following errors when playing in the editor and my head is still locked. I am not sure why this is not mentioned, but the headlock is not only in the Editor, but it is in the Quest via a build as well both before and after updating the OVRPlugin.dll.meta file.  I have 3 copies of the OVRPlugin.dll file in my project (see attached), so unsure why it cannot find them.

Couldn't locate OVRPlugin.dll

UnityEngine.Debug:LogError (object)

Unity.XR.Oculus.OculusLoader:EditorLoadOVRPlugin () (at ./Library/PackageCache/com.unity.xr.oculus/Runtime/OculusLoader.cs:288)

UnityEditor.EditorAssemblies:ProcessInitializeOnLoadMethodAttributes ()

DllNotFoundException: OVRPlugin assembly:<unknown assembly> type:<unknown type> member:(null)

OVRPlugin.get_initialized () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/OVRPlugin.cs:3355)

OVRManager.Awake () (at ./Library/PackageCache/com.meta.xr.sdk.core/Scripts/OVRManager.cs:2381)

Can Meta please let us know when the fix is coming becuase of as now, the last 4 versions of Unity 6, 22f1, 23f1 and 24f1 and now 25f1 are all broken with the Oculus XR Plug in.  Further the Meta Avatars do not appear in the Quest with the Open XR Plugin with the Meta Quest support enabled yet they do in the Editor.  Open XR is at least not headlocked at least.  Have to ask...what is going on with QA at Meta and Unity?  These bugs are rather obvious showstoppers and I would have thought they would have been caught before publishing. 

[tech_alchemy]

Hi Meta Support Team,

We are encountering a critical issue with our VR app during our upgrade process. Previously, we were using Unity 2022.3.16f1 with the legacy Oculus Package, and everything was functioning correctly. However, after updating to Unity 6000.0.23f1 and Meta SDK version 69.0.1, we are experiencing a black screen and an immediate crash on app start.

This issue persists even in a clean project with an empty scene and only the basic Meta packages imported.

Could you please provide any updates on known fixes for these issues or suggest workarounds? Your assistance would be greatly appreciated as this is blocking our project progress.

[tanmay.ronin]

Hi Meta Support Team,
We are facing the same issue as @tech_alchemy.
After updating to Unity 6(27f) and Meta SDK 69.0.1, our app crashes as soon as we launch it on the device. This is with the latest Occulus XR plugin v 4.4.0.
Tested on Quest 2, 3 and Pro.

Could you please provide a fix for this issue.

[tech_alchemy]

Hi Tanmay,

We were able to find a solution to this problem and got our build working correctly.

Make sure following is set in your project:
1. Project Settings : 
AndroidMinSdkVersion: 26
AndroidTargetSdkVersion: 31
useCustomProguardFile: 1
apiCompatibilityLevel: 3

2. We are using ProGuard you may not need this but we required it in our build process:
"-keep class com.unity3d.player.UnityPlayerActivity.** { *; }
-keep class com.unity3d.player.** { *; }"

3. Custom launcherTemplate.gradle

Make sure same is set for mainTemplate.gradle if you use it.

4. Android Manifest
Make sure to set correct activity name if you are using legacy manifest file in your project.
<activity android:label="@string/app_name" android:name="com.unity3d.player.UnityPlayerGameActivity">
In unity project settings also make sure to set Application Entry Point:

And finally, make sure to update the manifest using meta's tool as this includes new configs that it requires :

This fixed our issues as app was instant crashing on start mainly due to gradle SDK versions mismatch and manifest files being outdated.

[tanmay.ronin]

Thank you @tech_alchemy 
It worked just by doing pt 1 & 2. 
My guess is just the Manifest change would also be enough.

But thanks for the prompt solution!

[tech_alchemy]

You're welcome @tanmay.ronin 
Yeah, 1&2 should do it for most projects we had an outdated manifest that was referring to old value types so was needed in our case.

Happy building for Unity 6 😀

[yutoVR]

I started a new thread for this topic.

https://communityforums.atmeta.com/t5/Unity-Development/Voice-SDK-Dictation-Not-Working-in-Unity-202...