MQDH framerate lower than OVR Metrics Tool or users perspective
My App submission currently failes the review on the VRC.Quest.Performance.1 reqiurement. When observing the frame rate in MQDH I do see the low frame rate of 18 even in the starting window. When properly entering the application, I see the framerate quickly switching between 18 and 72. When using the OVR Metrics Tool, it show me a constant framerate of 72. Even from the users perspective, I do not see the beginning low framerate in the starting window or the quick switches of framerates in the main part of the application. This requirement currently fails during my app submissions. Does someone have an idea how to fix this or how to properly debug this behaviour? I am using UE5.3.2 and the latest MetaXR plugin version for UE5.3.2. Thanks!855Views1like2CommentsCannot connect Unreal Insights with App Lab game with Quest 2
I am stuck trying to see Unreal Insights for my app which I am developing through the App Lab. I've tried the following 2 guides, but they are so poorly written, I don't know if I am missing some key steps in between. https://developer.oculus.com/blog/get-started-with-unreal-insights-on-the-oculus-quest/ https://inu-games.com/2020/01/06/unreal-insights-on-oculus-quest/ So Far, I've connected my Quest 2 through USB. And I have a Beta build installed through App Lab in my Quest 2. I can launch and play my app no issues. Unreal 4.27 Then I set up TCP connections, by opening a Command Prompt and doing this "adb reverse tcp:1980 tcp:1980" and I get a return value of 1980. Next I set up the UE4CommandLine.txt which is under This PC\Quest 2\Internal shared storage\UE4Game\MusicalRange\UE4CommandLine.txt which is a path in the Oculus Quest 2. I have tried various variations of these txt files. I know it is updated in the quest, because I can see the file size change which each version. The 3 versions are ID Redaced to random characters ../../../MusicalRange/MusicalRange.uproject -Messaging -SessionId=ABABABA565656 -SessionOwner="Eugenio" -SessionName="Quest_2 (CDCDCD898989)" -cpuprofilertrace -statnamedevents -tracehost=127.0.0.1 ../../../MusicalRange/MusicalRange.uproject -Messaging -SessionId=ABABABA565656-SessionOwner="Eugenio" -SessionName="Quest_2 (CDCDCD898989)" -cpuprofilertrace -trace=log,counters,cpu,frame,bookmark,file,loadtime,gpu,rhicommands,rendercommands,object -statnamedevents -tracehost=127.0.0.1 -tracefile=-tracefile=/sdcard/UE4Game/MostRecentTraceCapture.utrace ../../../MusicalRange/MusicalRange.uproject /Game/MusicalRangeReloaded/Maps/Map_MRR_ShootingRange -trace=log,counters,cpu,frame,bookmark,file,loadtime,gpu,rhicommands,rendercommands,object -statnamedevents -tracehost=127.0.0.1 -tracefile=-tracefile=/sdcard/UE4Game/MostRecentTraceCapture.utrace Next, I open up Unreal Insights, enable Auto Start Analysis, but no session ever shows up when I run app on my Quest 2. All guides seem to indicate that it's done. It should be working. What am I missing?4.1KViews0likes4Comments