Unable to reproduce low performance from VRC1
Hi, I am developing a game for the Quest 3 and I have made 6 submissions till now but every time it gets rejected for not passing the VRC1, the performance one. The las 2 builds I received feedback telling me that "The app runs noticeably lower than 60 frames per second on supported devices." Those devices as I checked are just Quest 3 and Quest Pro. The problem is that on my Quest 3 I can not reproduce that behavior. Using the performance analyzer from Quest Developer Hub with the flags activated I see just 5 flagas, 3 of those are under 70 fps and just 2 are under 60, all of them happens when changing level/scene which is normal and definitely not "noticeably lower than 60". So, my question is ¿How does Meta test apps?¿Is there a way to get performance logs from them to know where exactly is the problem? Here is a capture of the performance analyzer: Thanks.
User Reporting Service - Using something else than Meta ID to report users
Hello everyone With the update to the Meta VRC's and the requirement of having an in-app user reporting mechanism, we opted to use the User Reporting Service offered by Meta. We have set it up for our apps which was a mostly smooth process but ran into two issues/questions. Is there a way to report a user using a different kind of id or by using a free-text field rather than the Meta user id? Currently, using the Meta user id seems to be the only way, but to report a specific person we would have to make this id visible in the app and would prefer not to (for aesthetic reasons and safety concerns). We do not receive the reporter's email address. Despite it being part of the reporting process and checking the box that I am willing to share my email address, it is not part of the report. Is this a bug that anyone else has experienced? Thank you very much for your help!extended periods threshhold
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
Can we Drop the Quest 1 VRC Requirement?
As Meta how now retired the Quest 1 and is only providing basic updates, can we now drop the requirement to test on Quest 1 to be accepted into App Lab? https://developer.oculus.com/resources/vrc-quest-performance-1/ I have a Quest 1 sat in my cupboard, gathering dust, solely to test my app before I submit to App Lab. If Meta, a $350 billion corporation, aren't supporting the device any more, why should indie devs be forced to! (I'll email support also and post any useful response here)
Privacy policy issue when publishing the app to app lab
Hi everyone~ I am running into a privacy policy issue when we try to publish the app to the app lab. We didn't collect any user data in any form for our app, so we show that on our privacy policy page. But still, we receive feedback from the review team indicating we have some issues with our privacy policy. Here are 2 feedback from oculus team: I have 2 questions: 1 I have an assumption of the issue, which is our client wants to show, that in the future version, we will collect user data, but in the current version, we don't. Is this causing the misunderstanding? 2 If we show that we didn't collect any user data, do we still have to have a clear explanation of how the user may request all their data? If anyone has any idea or experience, please leave your thought, thank you so much.
Streaming and Handtracking cases
Hi, I have questions while reading the VRC requirements for Oculus Store. 1. Is it mandatory for Oculus Store application to support streaming of interactive/immersive VR content? 2. Handtraсking input - is it mandatory or optional input type? Thanks in advance for your reply!Cannot pass VRC.Quest.Performance.3 on a built Unity APK
We are struggling to hit the 4 second requirement for AppLab submissions in Unity 2019.4.7f1. Our app takes around 8 seconds to hit our empty scene except a canvas image and some text. Upon testing a sideloaded standard empty URP project with the Oculus SDK it takes longer than 4 seconds just to get into an empty scene with nothing but the default URP and Oculus SDK assets!! A splash screen seem to doesn't improve this at all either? - Worth noting that we are still needing to use the Legacy Oculus VR SDK as we need to remain cross-platform with SteamVR for the PC client. I was wondering how it's possible that apps like Superhot and Beat Saber have managed to have a logo above the three Quest loading dots. And if that's something we would be able to set up for our app and would be appropriate to meet the VRC.Quest.Performance.3 criteria? I have done much Googling for this and have come up completely short, this is completely stumping me so I hope someone can help!AppLab submission failed VRC.Quest.Functional.3 (user gets stuck)
I submitted my Quest application to AppLab and got the feedback that it does not pass VRC.Quest.Functional.3. This is the requirement that the user shall not get stuck in the experience. The remark was that the user got stuck in the main menu. I have tried to reproduce the issue in many ways: I have run the app for 45 minutes, tried all scenes and back to the main menu, shortpressed the Oculus home button and then resumed the app. Recentered the app and continued. Made a photo and a video and resumed. Took off the headset for 10 minutes and resumed the app. Everything worked fine. I asked Oculus for some more context, so that I can troubleshoot this, but they could not give more details. Fair enough, they get so many apps these days. Has anyone experienced this before? Any suggestions on why this may have happened? Thanks!
