Metrics Hud crashing Quest 2
I'm seeing the Metrics HUD crashing the quest 2 device. I install the apk from the MQDH, it restarts the headset, and then I get stuck a the "objects detected in area" visual with no UI to continue past it. Looking at ADB, my logs are filled with this: "Warn VrRuntimeClient perfmgr: GetSystemPerformanceData(): unexpected version: 0 (vs. 3)" If I restart the headset, it gets stuck at the same place. If I uninstall the metrics hud, it eventually recovers and I can get to the home ui again.
Random spike in CPU usage and longer render times
Hello, I am a developer on a Unity app for Quest 2. We have a performance problem with our app that causes huge spikes in CPU usage. The app performs well and as we want it to at first, seen here captured by OVR metrics: All of the systems in the app test well and do not cause problems but after a certain amount of time doing various things, a user has a random random chance of having the framerate plummet. In this next picture, I experienced the bug and then returned to the login screen where the bug persisted: You can see that CPU usage has skyrocketed to a locked 100%. You would think that there is some process taking up frame time in the background. I took a look at the profiler on a build to see if there was a key culprit. Here is a frame under good conditions where performance is as expected: And after the bug, the frame looks like this: You can see that the player loop has almost doubled in duration, but the scripts portion of the frame is actually pretty much the same. The change is entirely in EarlyUpdate.XRUpdate and PostLateUpdate.FinishFrameRendering taking 5x as long as before. So why am I getting a huge CPU usage spike while also the rendering of the same workload is suddenly taking so much longer?? Is there any chance that the quest is downclocking under stress? Once this happens, there is no way to retrieve the old performance until you restart the app completely. There is no surefire way to trigger this to happen, it just randomly takes place when there's a decent amount going on and then stays forever. I do not understand what APP T and TW T mean in the OVR metrics panel as well, if those might lead to a culprit. Any ideas would be much appreciated, thank you.OVR Metric Tool v1.6.1 has memory stats unavailible (crossed out)? How to enable?
I have been using OVR Metric tool to help me profile my memory usage. I noticed it displaying zero for that metric on 1.5.1 so I updated to 1.6.1 but now it seems those stats are no longer available? How can I view memory usage in the new version?OVR Metrics Tool (Native Mobile): setOverlayDebugString does not work
Greetings! I am trying to add some custom debug info to overlay in OVR Metrics Tool and this does not work for some reason. I am using OVRMetricsToolSDK.aar which is distributed inside OVRMetricsTool_v1.5.1.zip. I've added this aar to my android project and this is how I try to set custom debug info: MetricsService.bind(getApplicationContext()); while (true) { MetricsService.setOverlayDebugString(getApplicationContext(), "hello world"); } This does not change anything on the overlay and I cannot see any custom text. Default overlay is running fine and "Display Debug Data on Overlay" is enabled. I can also see from logs that Metrics service is running: 2020-10-25 19:52:15.534 6866-6866/? D/MetricsService: Connected to metrics service: ComponentInfo{com.oculus.ovrmonitormetricsservice/com.oculus.ovrmonitormetricsservice.MetricsService} If I use MetricsService.appendCsvDebugString() instead, my custom text is logged, so I assume that communication with metrics service is fine. Could you please help me with this issue? I would greatly appreciate it! Thanks a lot in advance!
