The Public Test Channel (PTC) for Quest and Quest 2 v40 is starting to roll out today. Let's use this thread for collecting feedback on it. Share your impressions and let us know if you see any issues. Please make sure to also send in bug reports along with posting here if you notice anything wrong.
When sharing feedback, try to include as much detail as possible to help the team investigate.
It would be really helpful for these announcements to give at least a quick over view of changes/new features so we know what to focus on.
That's something we've talked about, but often times features aren't turned on, or might not be available to everyone. The team also like seeing what changes people notice without a list. But it's also good to be able to point folks at a specific thing and say "test everything about this and try to break it".
It's really good for us to hear about basic things that wind up breaking somehow at the PTC level. Like with the PTC for v38 when it was identified that headsets weren't going to sleep with a lens cover and we were able to get that patched quickly. It never would have been on a list of changes, but PTC was critical in finding and fixing it fast.
That makes sense, thanks for the response.
Now please let me back in the PTC! 🙂 I had to reset the Oculus app on my phone and now it will not let me back in the PTC.
Ryanality I don't know about the Quest v40 ptc since I'm not enrolled anymore with my Q2 but I will say that the new v40 ptc with the oculus desktop pc app does not work very well. Hand controllers gestures and tracking is bad and with some oculus store games like ultrawings 2 I cannot even use/select cockpit switches. I opted out of this and it took me back to v39. Actually the same version as the previous ptc. All seems to work well again, or at least as well as it worked before, lol!
At least with the oculus desktop app you have the option to roll back beta versions. I'll never go back to the Quest beta program until this is also the case. Why this cannot be made possible?
What does hand-tracking have to do with the PC software? It only supports the controllers.
Feel free to ignore me. I see that some support has been added for hand-tracking in PC Unity apps when using Link.
Can anyone confirm is this solves the 72Hz bug?
it doesnt. i still dont have anything but 72hz. why even own a quest 2 anymore
So not having anything but 72Hz for a month or so makes your Quest, literally the only viable hybrid headset, completely useless? That is quite a statment.
Yes, it does. Plus, it fixes the black screen on power on/restart and app sharing. Fixed it all on both my headsets.
Every recent patches have a big problem. I don't know the point of PTC.
The point is to give them more info before the patch goes out to more people. Changes are that without the PTC, even more problems would make it to the public release.
Updates will never be perfect, but they need to top pushing new features and focus on fixing existing problems for a few months.
I find that the image seems to come back sharp both in native and with the link. I really feel like we are finally back to the same quality as the 35 version. The 120 Hertz parameter is available in the experimental menu
Still dont have anything but 72hz. Can you please fix this before i sell my quest 2 for something that actually works 🙂
what is the status on MRC for android phones? I seem to remember it being mentioned on the support page for MRC that android phone support would be coming soon. is that a feature of v40?
Did PTC v40 on PC fix the Win 11 bug?
Hi! I would like to get answers to my questions because support does not give exact answers.
1) Do you admit the error with the inability to change the refresh rate of the screen or was it done intentionally?
2) Will you implement the possibility of rolling back to the previous firmware version? (This will help users continue to use quest 2 when developers release a new firmware update with bugs)
Thanks in advance for the answer!
