Bug GPU Profiling not supported by Oculus Quest with URP 11-12 for Unity 2021.1 and 2021.2

Hi,

When I am using profiler for Oculus Quest, it shows that GPU profiling is not supported by this device. It has been very helpful to use the Unity's GPU profiler for understanding issues and saving a ton of time.

I have tried with 2021.1.7f1 with URP 11 and 2021.2.0b6 with URP 12. But no luck.

Is there any ways to make it work or which version of Unity it will work with ?

 

Facing the same issue. Is there any preferred workaround, perhaps a user created tool that works? I've tried using the Snapdragon profiler but it gives rendering information at an OpenGL level which is hard to understand.

 

It was so convenient with the GPU profiler to find bottlenecks without much guess work and efforts. Also the way it showed the details at high level was very useful.

Knowing those GPU timings(for different parts of the renderings) was so helpful before further debugging and optimizing things with renderdoc/frame-debugger. I haven't found any good alternative to the GPU profiler yet.

Hope you guys fix it on priority. Sure a lot of devs who switched to URP are praying for this.

 

@MartinTilo
Hey does the GPU profiler work by any chance with 2021.1.7f1 version of Unity in a builtin project ?
I tried it with a builtin project with the above version and it doesn't work.

 

I'm still quite confused @MartinTilo .

Does this mean that any Android/ARM project using Unity 2021+ (regardless of rendering pipeline) won't be able to use the GPU Usage part of the profiler? Assuming it's on OpenGL and Graphics Jobs is turned off.

Because that's the case for me when I try debugging the GPU usage with OpenGL, Graphics Jobs off.

I have tried using Unity 2021 + URP 11 + Oculus Quest -> GPU usage just says "This device is not supported".
I have tried using Unity 2021 + Built-in + Oculus Quest -> GPU usage just says "This device is not supported".

Sorry, I'm just trying to understand this better.

To clarify, this worked in 2019.3.11f1 + Builtin + Oculus Quest

 

Done. id - 1359552

Thanks for taking the time to help.

 

@MartinTilo Hi, sorry for the ping but any updates on this issue?

 

Did some more testing - GPU usage turns up for these
Unity 2020.3 + URP 10.6 + Oculus Quest
Unity 2020.3 + Built in + Oculus Quest

At this point I have to strongly consider going to back to Unity 2020, because the Unity GPU usage is a crucial feature for us. Would love to know why this is happening in 2021.1 asap so that I can revert back if I have to with a clear conscience. Is it be possible for you to test this directly or if there's any other way to quicken this process.

 

@MartinTilo
Hi, thanks a lot for helping.

So I have tried out with Graphics Jobs disabled and other Project Settings options as well, following the unity forums regarding gpu profiler issues. But in all these cases it just doesn't work and empty.

Even if I disable Graphics Jobs in settings, then the empty GPU profiler just shows that the device is not supported.

 

For anyone else reading this wondering how to use the currently working and available URP/HDRP profiling tools in 2020.1+ @MartinTilo was able to help me though all of the step on getting a few basic profiler recorders working for GPU last winter here:

https://forum.unity.com/threads/how-to-use-gpu-profiler-stats.1058645/

I ended up making a script which logs all the currently available gpu profilers and let's you see when they become available to the developer (a few seconds after launch normally), which I posted in the above thread. (Note: These only work in editor and dev builds for anything pre-2021.1). This definitely isn't a strong replacement for a full GPU profiler but I was able to make it into a makeshift frame rate graph in game, which has been night and day for allowing me to see when I'm creeping up to 90hz in game (super important for VR, since going beyond simply half's the frame rate).

 

Yes, I had tried with this before. Just to be sure, I tried it again now with both "Graphics Job" and "Enable Frame Timings" turned off. Doesn't work.

For graphics API I have been using OpenGL which is the supported one for GPU usage Profiler. (So I disable Auto Graphics API option to remove Vulkan and keep OpenGL API only)

 

Got an update saying that they were able to successfully reproduce the issue.
https://issuetracker.unity3d.com/product/unity/issues/guid/1359552

 

@MartinTilo

Hi, is there any update on this, has the devs already picked up this issue after the above QA check?
Sorry, for asking, but will be helpful to know if there is any progress on this.

 

Thank you for explaining why this bug started happening and what's the possible resolution being planned.

Yes, having an option to select any of the three GPU measuring systems will be helpful if it runs these systems one at a time and the GPU profiler starts displaying the data soon. This will save us a lot of time and will be able to use the GPU profiler again soon, while the full GPU Profiler Module with Profiler are being redone.

After researching on the forums and a lot of consideration we had upgraded the game from 2019.3.11f1 builtin to 2021.1.7f1 urp but sadly didn't expect this bug and the GPU profiler has been very helpful to debug the specific rendering costs in the levels. The project is too big now and downgrading only for this signle issue will take up a lot of time and uncertainty of breaking the project. I will take your advice and stick to this version of unity hoping for a GPU Profiler quick fix sooner in the upcoming Unity 2021.x updates.

I had also tested with an android build on mobile phone and PC build sometimes back, to know if the issue is device specific or platform. Yes, the GPU profiler didn't ran for android mobile builds as well. Then wondered, this should have been a common issue between mobile(android) game devs but there was not many posts about it on the forums.

Thanks again for helping out.

 

@MartinTilo

Can you please give a rough time estimate for the fix to the GPU Profiler, with the "Player Settings" option you mentioned? That will help a lot in making progress and decisions with the game.

 

Could you give provide code using this api that will show a similar GPU frame timing breadown as the profiler? Specifically, I'm looking for a way to get the detailed info that the GPU usage UI gives like Skybox render time, Render.OpaqueGeometry etc, not just set pass calls.

I've been scourging the forums to get a better understanding of this and understand it's limitations since I really don't want to implement yet another Unity workaround only to get stuck again. Posts like this -> https://forum.unity.com/threads/fra...esttimings-always-returning-0-timings.544325/ don't give the highest confidence that this will work for Android. Also, is there any known issue with this approach that we should be aware of?

Also, in one of your responses on that thread, you mentioned
>Btw, as of 2020.1 Recorder can already get you GPU timings where the profiler UI can too, but only on Development builds. The newer ProfilerRecorder API allows us to also expose some of the stats in Release.

Is that also an option to get the same info as the GPU profiler UI? I'm still confused by all this.

 

I understand things a bit more, especially the ProfilerRecorder API.
I'm able to get the timing info of some markers using the code provided from this talk

Am I doing this right? And, is there an easy way to list everything (hierarchically) the way the GPU usage profiler does or do I need to code that myself? Where is the hierarchical relationship available between the statistics? GetAvailableStats doesn't have this information.

Furthermore, I can view the stats on my PC in the game view, whereas in the Oculus Quest (which I haven't tested yet), I'll still only be able to view the stats in the headset (assuming it works). Connecting via IP address to a Unity window seems like a pretty big task in itself, so I'm wondering if there any other options for this. Perhaps logging to file from the Quest could work.

 

Thanks for the the response!

One more question - using ProfilerRecorderHandle.GetAvailable() I get all the Rendering markers of which some do seem like GPU markers (I'm on 2021.1). Does this mean that while querying these, I'll just get 0 as the return value since I'm not on 2021.2?

 

So, I'm not getting any GPU markers in an Oculus Quest build -> only CPU stats.
Getting GPU, CPU stats in a PCVR build. Using Recorder API (2021.1).

PCVR build -


Quest build (attachment)

 

Okay, that's unfortunate. So confused what to do now. Downgrading Unity, URP versions to 2020.3 will be a nightmare.

Do you have an estimate for when a fix will land? Also, will it be backported to the earlier Unity versions?

 

Got it! Thanks a lot for everything, by the way. You've answered all my questions so quickly and intelligently, I really appreciate it! I certainly understand profiling a lot more now!

Looking forward to the fix

 

@MartinTilo
*bump* GPU profiling on Android devices still not working in the latest stable Unity versions...
Any news on the fix?

 

Going to add that this issue is definitely blocking us a bit, so fingers crossed you guys will be able to get that fix in soon!

 

I see on the Issue page that this is fixed in 2022.1.X, does this mean that it will not ever be fixed for 2021.2 or the upcoming 2021 LTS?

 

I am right now trying to profile in 2021.3 and it is still a problem. Isn't this implemented yet?

 

Oh thanks! Sadly, I am using Vulkan for better perfomance and it seems to be incompatible. Is there any ETA for the profiling working with it? Them same with Graphics Jobs