[System: Windows 11]
[Mobo: MEG X570 UNIFY]
[CPU: AMD Ryzen 5950X]
[GPU: RTX 4090]
[SSD: Samsung 990 PRO 2TB PCIe 4.0 (up to 7450 MB/s)]
[Ram: 32.0 GB 3600MHz]
[Unity: 2022.3.19f]
[Device: Meta Quest 3]
[Using: Meta Quest Link]
Fresh project (simple scene: “just falling cube with rigidbody”) when I press the button “Play” starts in 3 seconds and this is perfect, but when I turn on Oculus “XR Plug-in Management” it takes more than 20 seconds to start this super simple scene!!! How can I fix it???
This usually happens when no device is detected. It waits for oculus to start the hmd which does not exist.
I think OpenXR fixed it, not sure about Oculus. Feel free to submit a bug report
Hello,
We’re facing the same issue with quest link binding to Unity. But it only occurs since Tuesday when they updated the Oculus app (now Meta Quest Link) to v62. Before that it was fine.
Our headsets (quest 2 and 3) are all facing the issue, but didn’t get the v62 software update yet, hopefully it will be fixed when headset get the update, but who knows… Did your Quest 3 has the update?
Also, you can Go to Project Settings → Editor → check “Enter Play Mode Settings” (leave uncheck reload domain/scene)
This should make play mode launch faster, from 3 seconds to 0. Note that some features and plugins don’t support that option but for a simple scene it should work. But this won’t resolve Oculus Link taking ages to connect to Unity…
I figured it was caused by the latest Oculus app update. Before the update everything worked fine, play mode would start way before I put on my headset.
I submitted a bug through Unity Hub via the “Troubleshooting: Report a bug” section. I received an email from Unity, but it says “No Access (You don’t have permission to view this portal).” Therefore, I’m unable to track my bug report on Jira Service Management. Could you please help me resolve this issue so I can follow my bug report?
Unfortunately my Quest 3 is still on v60 so I just need to wait till it will be updated to v62 ;(
“Enter Play Mode Settings” is fantastic for normal play, starting the game instantly (0 seconds)! However, enabling XR Plug-in Management adds a significant delay, forcing me to wait around 20 seconds each time.
You’re right! Before the update, my simple scene started in just a few seconds. Now, unfortunately, it takes significantly longer, which is frustrating and inefficient.
Same for me. (Meta Link App Version 62.0.0.235.346) I have two dev Windows PC’s. I also tested this with a Quest 2 and Quest 3
I updated the Oculus App on Machine one as it requested I use new drivers to continue. Now takes 20 Seconds to Launch play button (Unity Editor Freezes)
I postponed the update on machine 2. No Problems. Runs as it should. I then updated Unity Hub to 3.7.0 Again no problems.
I then allowed the PC Oculus Desktop App to complete it’s update, restarted the machine and now that machine takes 20 seconds to enter play mode.
Here is the log from Machine one.
Editor.Log snip from C:\Users\micro\AppData\Local\Unity\Editor
The 20 Second Delay can be seen at 21:06:45 to 21:07:05
Have the same issue. Everything was ok with Desktop v60, then long play-mode-enter-time with simple scene and v62 desktop. Quest 3 is on v60. My Quest 2 is already v62 and enters instantly.
With V62 I get a very long delay when I first start the session this time 250 Seconds (4mins 10s) from hitting the play button to running. This is completely unworkable!
06:38:47.546 to 06:42:58.965
Subsequent restarts create a delay of 20 Seconds. It is really hindering development.
Looks like the Internal_StartSession of the OpenXRBaseLoader call is taking about 20s to process. I assume this is due to a bug introduced by oculus with the newest update to the pc link software.
I have tried going to the beta branch of the link software, and the problem is still there.
I’ve submitted a bug report to Unity using a very simple app as an example.
It would be worth sending them your reports as it may help them diagnose this problem.
Unity Freezes initially for 4 mins then subsequently 20 seconds after every play invocation with a Quest Attached and Linked.
XR Bug is not specific to the attached project but all projects. New or existing.
XR Bug can be replicated on Quest 2 and Quest 3
XR Bug has been replicated on 2022.1.20f1 & 2021.3.4f1
XR Bug is related to the Oculus Link Application on W10 PC 64bit - All updates installed.
A snip from the Log (Attached) is shown here
[Subsystems] Loading plugin UnityOpenXR for subsystem OpenXR Display…
[XR] [37468] [09:44:51.462][Info ] Available Layers: (0)
[Subsystems] Loading plugin UnityOpenXR for subsystem OpenXR Input…
[XR] [37468] [09:45:11.628][Error ] xrGetReferenceSpaceBoundsRect: XR_SPACE_BOUNDS_UNAVAILABLE
[XR] [37468] [09:45:11.628][Error ] xrGetReferenceSpaceBoundsRect: XR_SPACE_BOUNDS_UNAVAILABLE
[XR] [37468] [09:45:11.628][Error ] xrGetReferenceSpaceBoundsRect: XR_SPACE_BOUNDS_UNAVAILABLE
More information available from various users here
Ensure you have the Oculus link V0.62 installed. (Latest as of Jan 2024)
Create a new project for the Oculus Quest 2 or 3. with 2022.1.20f1
The project can be very simple but must include XR integration.
Press Play.
Unity will freeze and then run after a delay.
There will be a 4 minute delay on the first invocation.
There will be 20 second delays and subsequent invocations.
Log from my machine is attached.
Hey everyone! I’ve found a fix for that pesky bug! The key is ensuring your Quest 3 and PC Meta Link App are on the same version number (currently “62”).
Here’s the solution:
Update your Meta Link App: Get the latest version, 62.0.0.235.346 (62.0.0.235.346).
Update your Meta Quest 3: Grab the newest update, 62.0.0.247.343.563460087.
After that, you should be back to smooth development in any Unity version!
P.S. Stuck on Quest 3 version “60”? No worries! Join the Public Test Channel in the Meta Quest app on your phone. This lets you manually update to 62 using the Software Update option on your Quest 3.
Nicely worked out. Why would they allow unsynchronised releases.
I tried enrolling in the public test channel but it is apparently full, for the Quest 2. I wonder if there is another way?
Maybe it’s possible to rewind the update on the PC Link App?
I don’t know who is to blame here, but I hope someone can fix this. I was able to join the public test channel on Quest 3, but others might not be so lucky. I shouldn’t need to flash my device to get into play mode in less than 25 seconds.
