MQDH reports low framerate but other tools do not (Failed VRC.Quest.Performance.1)
Unity LTS 2022.3.37f1 / OpenXR I first submitted my game a few weeks ago and received a VRC.Quest.Performance.1 failure (running < 60 fps). It was running at a solid 72 fps on Quest 3, so I borrowed a Quest 2 and found it was quite low (30fps or so) and went on to optimise the game quite a bit and brought it up to 72 fps on both Quest 2/3 consistently as per the OVR Metrics overlay and the adb logcat -s VrApi command Now this is where things get weird. I resubmitted and received the same VRC1 failure again. I double checked the performance in MQDH and found that the fps look like a sawtooth pattern, where it reports 72fps and 19fps on alternate frames, seemingly at random. In some cases the low fps frames were reporting an early frame as well. The logcat VrApi command shows LAT (latency) as -1, meaning that the frame latency is dynamically managed by Phase Sync (which can no longer be turned off when using OpenXR in Unity). The game is running buttery smooth and I still get these VRC1 warning in MQDH on Quest 3, even when I set the refresh rate to 90hz where it runs fine. There's no way that the game can run at 18 fps higher and still somehow be dropping frames. It also isn't reporting any late or stale frames either so go figure. I think this could be an MQDH bug as none of the other reporting tools show the framerate drops but this seems to trigger automated failure during review and I have no idea what to do about itSolved1.3KViews0likes3Comments
Sudden bad performance in new and old builds
Heya Just a bit over one week ago the project I work on lost most of its build performance. After optimizing everything and triple checking the project settings we recovered barely any fps. I had tried to revert to older version of the project which did not help either. After many attempts to fix it I tried to play the older builds I had for comparison which were surprisingly low performance as well. These are builds from months ago which were running just fine until recently. An empty project with only the character controller results in the same bad performance, this plugin being the BNG Framework. As for some extra information regarding the details: It happens with both the quest 1 and 2. The project version is URP 2021.3.11f1 - the issues persist through other versions though. We have the XR Plugin Management, XR Interaction Toolkit, Oculus XR and OpenXR plugins installed. The headsets have been reset to factory settings. I'm hoping it's a temporary issue with the quest. However, answers/fixes would be deeply appreciated.2.2KViews0likes5Comments