Yes, I have. And I sadly don’t really have a reply other than the most annoying developer answer - on my device it is not reproducible. It does seem like there are many stale frames in your test environment, which quite bothers me to be honest.
Controllers, shaders, other objects will of course slightly degrade the performance, but not to that level. I am sorry that i am not 100% dedicated to that, as I have other things on my todo list, but I promise to find time to fully debug this and see if we can improve here and what is the main cause.
Thanks for the feedback RaananW!
In the meanwhile, could you suggest me a tool or a method to check which apps are in execution on the Quest 2? A sort of “windows” task manager, to discover unexpected extra activities of the Quest 2?
that’s a good question. I would assume it works just like any android device - you can do that with adb. TBH - I haven’t tried it, but debugging sessions work the same as android and it is after all android under the hood.
Something like adb shell ps -e after connecting to the device should show you all running processes
@RaanaW, What version of the OS are you using in Quest 2, I’m using V69. In older versions I didn’t notice this huge performance drop. I’ve tried this in multiple Meta quest devices and it is happening in all of them (Quest 2, Quest Pro and Quest 3).
For grins, I pulled out my Quest 1 to try this. It’s locked at v50 since Meta stopped updating it. It’s a rock-solid 70-ish fps, yet my Quest 2 and Quest 3 perform badly. Frustrating.
(I’d done this test 2 months ago, just forgot to post until now)
I was actually testing with 72 on friday - solid 90fps even when hands are showing. seems like they have improved the browser rendering process. Have you tried with the latest update?
I haven’t tested with the 3 yet, but the 2 is a rock-solid 72fps with hands or controllers showing, looking around, and anything else I can do that used to cause a spike.
