The intersection of Unity development and virtual reality continues to be a powerful combination for creating immersive experiences. But developers using Unity 2022.3 with Oculus Link on Windows 11 may encounter a frustrating problem: the constant hourglass or “loading” icon that won’t go away inside the headset. This issue disrupts testing, breaks immersion, and hinders productivity.
If you’re experiencing this problem, you’re not alone. This article explores the causes, workarounds, and potential long-term solutions for the constant hourglass issue when developing with Unity and Oculus Link on Windows 11.
What Is the Constant Hourglass Problem?
When connecting your Oculus headset (like the Meta Quest 2 or Quest 3) to your PC via Oculus Link or Air Link and running a Unity project (especially one built with Unity 2022.3 LTS), you may see the hourglass icon inside your headset, usually indicating a loading state. However, in this situation, the hourglass:
-
Stays indefinitely.
-
Appears even when the scene is fully loaded.
-
May cause poor frame rates or stuttering.
-
Makes testing and debugging within the headset nearly impossible.
Even though the Unity scene appears to be running fine on the PC, the headset behaves as if it’s waiting or stuck.
Why Does This Happen?
The hourglass issue is often caused by a combination of factors rather than a single root cause. Developers have identified some recurring themes:
1. Compositor Timing Mismatch
Oculus Link uses a separate rendering pipeline compared to standalone Quest apps. If Unity’s frame delivery doesn’t align with Oculus’ compositor expectations — especially on Windows 11 — Oculus might assume the application is “stuck” or not responding properly.
2. Low Frame Rate
If your Unity scene doesn’t meet the minimum VR framerate threshold (usually 72Hz or 90Hz, depending on your headset settings), the hourglass can appear. Unity may technically be “running”, but Oculus Link interprets the frame drops as a loading issue.
3. Windows 11 Background Services
Windows 11 introduced new system-level processes and background optimizations that can interfere with real-time rendering, especially in performance-sensitive environments like VR.
4. XR Plugin Management Misconfiguration
In Unity 2022.3, the XR Plugin Management system needs precise configuration. A small misstep in enabling or initializing the Oculus provider may lead to inconsistent runtime behavior.
How to Fix or Work Around It
Until Oculus and Unity release more targeted patches for full Windows 11 stability, here are some practical fixes and workarounds:
1. Update All Software
This includes:
-
Unity 2022.3 (ensure you’re on the latest minor patch)
-
Oculus software (via the Meta Quest PC app)
-
GPU drivers (NVIDIA or AMD)
-
Windows 11 (install optional updates too)
Incompatibilities between older Oculus drivers and the latest Unity versions often lead to rendering bugs like the hourglass.
2. Correct XR Setup in Unity
Make sure you’re using Unity’s XR Plugin Management correctly:
-
Go to Project Settings > XR Plug-in Management.
-
Enable Oculus under both PC, Mac & Linux Standalone and Android if you build for both.
-
In Oculus Settings, enable Stereo Rendering Mode as Multiview for best compatibility.
-
Use OpenXR only if you’re comfortable debugging additional runtime layers — Oculus Link still behaves best with the legacy Oculus SDK in many cases.
Also, check your Player Settings:
-
Graphics API: Use Direct3D11, not 12 (D3D12 is still less stable for VR).
-
VSync: Turn off VSync; let Oculus manage frame pacing.
-
Set Target Frame Rate explicitly to match your headset (typically 72, 80, or 90).
3. Use OVR Metrics Tool or Debugging Info
The OVR Metrics Tool (or in-headset performance overlays) can reveal whether your app is consistently hitting performance thresholds. If you’re dipping below frame rate targets, consider optimizing the scene — disable shadows, lower post-processing effects, reduce draw calls, or bake lighting.
If the scene runs well but the hourglass still appears, it may be a synchronization issue rather than a performance one.
4. Force Oculus Dash Focus
Sometimes, Oculus Dash fails to properly “foreground” your Unity application. Use the Oculus Debug Tool or run a simple app switcher script that triggers window focus back to your app. Alternatively, clicking the Unity window with your mouse after launching the build can help it regain focus in some cases.
5. Run as Administrator
Launching Unity and the Oculus app as Administrator ensures that permissions for hardware-level rendering are properly granted. This is especially relevant on Windows 11 where certain security contexts can throttle app access to GPU or USB devices.
6. Switch to Standalone Builds
Many developers experience the hourglass only in Play Mode. Try building the project and running the compiled executable instead of testing directly in the Unity Editor. Builds often run more smoothly and are more likely to trigger Oculus Link to behave properly.
Long-Term Solutions
While workarounds are helpful, developers need sustainable, long-term fixes. These may include:
-
Unity optimizing XR Plugin Management for Windows 11 and Oculus Link.
-
Meta improving the Oculus Link runtime’s tolerance for minor frame drops or timing jitter.
-
Standardized OpenXR workflows with fewer proprietary quirks.
For now, keeping your software stack up to date and simplifying your scene for VR are your best bets.
Pro Tips for VR Developers
If you’re regularly developing with Unity and Oculus on Windows 11, here are a few extra best practices:
-
Test frequently in small scenes to isolate bugs like the hourglass.
-
Use logging to confirm the scene is running even when the headset isn’t reflecting it.
-
Keep the Unity Editor lightweight — disable extra tabs or windows to reduce UI lag.
-
Close unnecessary background apps like Chrome, Discord, or screen recorders.
-
Use USB 3.0 or higher for Oculus Link and ensure your cable is not throttling data transfer.
Conclusion
The constant hourglass issue when using Unity 2022.3 with Oculus Link on Windows 11 is a frustrating hurdle in an otherwise exciting development environment. Fortunately, with careful setup, regular updates, and smart testing strategies, you can reduce or eliminate the problem.
VR development is still an evolving frontier, and bugs like this are part of the growing pains. By staying informed and adapting your workflow, you’ll be better equipped to deliver compelling virtual experiences without being stuck staring at an hourglass.
