Advanced GPU OVR metrics not working
I've been using OVR Metrics HUD with the advanced GPU metrics since it was made available, and for the most part it has worked very well. Lately though it just stopped working and is giving me garbage values, and I've tried factory resetting, downloading older versions of it, enabling different settings in different orders and nothing is working for me! It's something that I really need to be able to work efficiently so if anyone could help out it'd be amazing!
Can't meet FPS requirement in build - EDIT: partial fix
Hi, After running the automated VRC tests in the oculus debug tool, i'm growing concerned about the ability to accurately test my framerate for oculus rift s. The vrc testframerate fails, giving me an average of 67.5 fps (I should be hitting 80 for this oculus rift s). if I enable the performance hud and run the app again, i see conflicting statistics. Application GPU/CPU render times are about 3ms each, but the "app queue ahead" time is around 30ms? App framerate is shown perfectly locked at 60fps. If my total frame time is somewhere around 6-7ms, why am i getting a framerate at half that? The first scene in my unity build is a nearly empty menu scene, just a skybox and a simple menu. This runs perfectly fine in the unity editor, and usually a non-editor build will always run a little faster. I've tried changing vsync settings, running the app with nothing else open, restarting my computer even, nothing helps me hit the required 80fps in a near empty scene! Edit: I've upgraded from oculus integration 1.41 to 1.42, no change there. I also tried toggling the queue ahead option in the OVRManager component, didn't seem to change anything. Here's me rendering an almost empty scene in unity editor, easily getting 100+fps Unity 2019.2.1, windows 10 running a GTX 970, oculus integration from ap store version 1.41, will try upgrading to 1.42
Hello VR Project Failing VRC.Quest.Performance.1 on startup
I recently submitted a game to the Meta Quest App Lab, and it was rejected for failing VRC.Quest.Performance.1, which means the frame rate dipped below allowable levels. When watching the app using the MQDH Performance Analyzer, it showed that a drastic frame drop occurred at the instant the app was launched- before/as the Unity splash screen is shown. In an effort to understand this issue, I built the "Hello VR" introductory project described here: https://developer.oculus.com/documentation/unity/unity-tutorial-hello-vr/. When profiling this incredibly lightweight application using the Performance Analyzer, I still had performance-check-failing lag at application startup. I feel like I am missing something- what is the standard way to launch Unity games that does not result in frame drops? In my game I am using oculus splash screen and a lightweight initial loading scene, but it has not resolved the initial lag. This is a screenshot of the Performance Analyzer running the "Hello VR" app.
Understanding performance and workfow..
Hello! i'm a bit confused about differences between PCVR and Deployed APK workflow.. What i understand is that PCVR makes Quest to be used as a second screen (in this case VR screen), so, all the gpu process, computation and logics are made in the computer, Quest is only rendering results... In this case, Quest requires the computer running the application in order to work... By the other side, Deployed APK allows application to run directly in the Quest and there is no computer dependency, all computation are made directly in the Quest... Until now, this is all i know, my question points to performance, i'm using Unreal Engine 5, my game works smooth on standalone mode, very smooth...... but when i switch to VR Preview, my game lags a lot, i was wondering why is this happening if GPU computation is being made by the computer.... I tried using both Air Link and Cable, but same result... Any help will be very appreciated..Extended Periods Thresholds
Hello, I am working with a developer who is creating their first VR App/game. When reviewing the VRCs, in particular the VRC.Quest.Performance.1 test case. The expected results reads The application should not experience extended periods of framerate below the requested refresh rate of the display. Exceptions include when there’s a black screen or loading scenes, or when system menu overlays are present. We were interested in, what Meta considers an Extended Period? 5 seconds? 10 seconds? Any information would be helpful Thank you in advance, Lee-Roy
VR.WaitForGPU killing performance in Unity3D. Very difficult to profile other issues. Video Example
Here is a video showing what the issue is https://youtu.be/n5ngEzZSKH0 I'm trying to release an update to Vanguard V but perforance has become a real issue. The game runs at 150fps on my laptop but the framerate tanks when I touch the Oculus headset. I get these nasty yellow spikes and the FPS tanks to the 50s, even on my desktop (980 GTX TI). I then created a new scene with nothing but a camera and the default Directional Light. The framerate goes into the 800s until I touch the headset. It then tanks again to 90-100fps. This is an empty scene. Now, if this is by "design" it has made it very difficult to isolate any real issues in the profiler. Any help would be great. Unity 5.5.1f1 and observed in Unity 5.5.2 as well Windows 10 x64
