Other XREarlyUpdate spikes any news?

Hey all! Is there any news about case
• XR: [XR SDK][Oculus] EarlyUpdate.XRUpdate spikes inconsistently (1262597)

Wondering because this problem is almost 1 year old, and do not allow to upload games to Oculus Store. That very critical for marketplace.
Every week i checking changelog of 2019.4 , 2020.1 , 2020.2 , 2021.1 with hope that this bug resolved.
I really would be happy to know more news about progress of fixing this bug (Already uploaded several ticket with different projects to help out fix this bug faster).

Thanks!

 

Where are i can find the new version of Oculus XR Plugin?
I'm on 2021.1 alpha. playing with latest URP versions =)

 

Here is my test of Unity 2020.2b12 with Oculus XR 1.7

Now i see Initialization.XREarlyUpdate (5 ms) + XREarlyUpdate (10 ms)

Here is recording of that - https://www.dropbox.com/sh/jj1k0jp1za4vqn3/AAAqE7WvdmQASvS0yExa-0lua?dl=0

 

Here is example of rendering without VR. just rendering two 4k display in scene and its about 2.5 ms to render

 

Maybe i can send to you a project files?

 

Unity 2021.1a9 Oculus XR1.7 pre 2.
https://www.dropbox.com/s/cacazb32o0t0l34/Unity_Profile_2022.1a9_HDRP_OculusXR1.7.data?dl=0
https://www.dropbox.com/s/u3tk7twkzv4snmo/Unity_Profile_2022.1a9_URP_OculusXR1.7.data?dl=0
Keep in mind that i have same result in complex and simple blank scenes =(

 

Still happens on Unity 2020.2 with Oculus Integration 20.1, Oculus XR Plugin 1.7.0 preview 2.
The time is spent in OculusRuntime.WaitToBeginFrame.

 

I tried with an older version of Unity (2019.4) with legacy XR and Oculus Integration v15(?) (OVR 1.46.0) and the FPS is still low (on same Oculus App v24 and Oculus Quest v23). This wasn't the case before the update of either Windows 10 (20H2 from 1809), NVidia Drivers (v460.89 for GTX 1070) or Oculus Quest/App.
Since it works fine (i.e. 80-90 FPS) the first time I start the app (Unity, Oculus App/Link) I tend to believe that is the latest update of Oculus Quest.
The issue is not present if I build & run directly on the Quest (Android Player).

 

Happy new year everyone!
jj-unity
Any news about that?

 

Happy new year!
After some research on various forums, I think this is caused by a mix from Windows 10 (20H2 in my case) and NVidia drivers (mine is GTX 1070). Basically, this started (at least I started to notice it) after the Windows 10 20H2 update from 1809.
In various topic NVidia forums I found that other users have this issue but not so much on older Windows 10 build (1909 is the last stable one - don't take my word as an absolute - 2004 and above are problematic).
I tried disabling all kind of "features" from Windows 10 (Game mode, DVR, etc.) and enabled the most performance for other (NVidia Control panel, Windows 10 baterry settings, OVRServer priority to High etc.) with little success.
So, I am looking forward to new Windows 10 Updates and/or NVidia drivers.

 

maybe, not sure about that. its happening at everyone from my friends. Even on RTX2080

 

Are you using an older built of Windows 10 = below 2004?

 

My windows version is 1909

 

Can you check on an even older build?

I still think it is a Windows/GPU Driver issue for the following reasons:
1/ It happens on SteamVR/Oculus default apps (SteamVR Home and Oculus Link/Oculus Home), too - not Unity related
2/ It works fine for some time (1-2 minutes) and then the FPS drops (in both Unity and default VR apps) - this is experienced by other ppl on NVidia forums (especially if I start a fresh Unity & Oculus Link session)
3/ the entire system is getting very slow and it recovers as soon as I exit the app.

So, it is like something is not keeping up with the demand or is some Thread.Sleep/while(1) forgotten in the code...

 

I've updated to 461.33 and seems to be better - average FPS is 30 but the spikes are there after running the VR app in the Editor.

 

It looks like directly setting Application.targetFrameRate at runtime can cause intermittent lag spikes (every second or so) afterwards in 2020 LTS with Oculus Integration. Problem is consistent in the editor and when built for PC. During these spikes, the profiler shows the following two entries taking up a large amount of time each:

EarlyUpdate.XRUpdate => OculusRuntime.WaitToBeginFrame
TimeUpdate.WaitForPresentationAndUpdateTime => WaitForTargetFPS

I upgraded from 2019 LTS and ran into this problem right away. Removing my call to Application.targetFrameRate seems to have fixed it.

Hope this helps anyone else running into this when jumping to 2020 LTS.

 

Hi, can you explain how did you remove that please?

 

Any news on this? I am currently wasting 17.82ms on OculusRuntime.WaitToBeginFrame alone, 60 ~ 80% of my frame time is just this.


I profiled on a oculus build directly, so no editor influence.
My scene is super small, never going over 30 drawcalls.

Everything is up to date:
- Unity 2021.3.7
- XR Management: 4.2.1
- Oculus Plugin 3.0.2

 

Something simillar happens with the OpenXR plugin, but the execution is stuck in "FrameEvents.XRBeginFrame > Gfx.WaitForRenderThread"


The render thread is doing nothing though...

 

Having the same issue, did you find a fix?

 

Wanted to add my "me too". In my case, it spends 40ms(!) on OculusRuntime.WaitToBeginFrame causing my frame rate to drop to around 20 FPS on a scene (an empty room) with one point light, 4 walls, a floor and a ceiling and nothing else.

 

This happens to me as well.

Spikes every other frame, with the culprit being OculusRuntime.WaitToBeginFrame.

It only happens in the Unity Editor and only after taking off the HMD and putting it back on in a different area of the play space. Afterwards it will continue to spike until restarting the game.

 

OculusRuntime.WaitToBeginFrame seems to be taking up over half the CPU budget in every frame. How is this possible?

 

Me too. The difference is my OculusRuntime.WaitToBeginFrame not spikes, but taking 50% cpu time at every frame.

 

up. Am also having the same issue wiht OculusRuntime.WaitToBeginFrame, but instead of spiking its consistenlty taking at least 50% of cpu time every frame.

 

Hi everyone, I'm facing this issue too... Has anyone been able to solve it?

 

I was able to solve this by realising that it was an optimisation problem of my game. Basically, the CPU is waiting for a long time for the next frame, that's why EarlyUpdate.XRUpdate takes such a long time, it basically waits.

It waits for the GPU to complete its job on the frame. So, in the profiler, if you have a look at the Render Thread, you should see that it is running all the time, and takes much longer than the CPU to compute its part of the job to render the frame.
Just try different GPU optimisation techniques, so as to release stress on your Render Thread (GPU), and you'll see that the CPU will wait less time, thus reducing EarlyUpdate.XRUpdate.

Hope this helps !

 

@jj-unity
My application have the same issue. But it's with "OpenXR Plug-in Providers", not "Oculus". We developed our own OpenXR runtime. Now the XRUpdate function always take about 10~20ms.

 

Trying to get our Quest 2/3 app a stable 90 FPS with 8 players. So, our frame budget is 11.11ms. Which most of the time we are in budget. But, every now and then we get a spike that puts us over 20ms. When Profiling, I see its due to OculusRuntime.WaitToBeginFrame. Its waiting for 10 ms. In other frames, it waits 3ms or less. All my other threads appear to be idle.