Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v57 and the solutions for some have shipped, while others are on the way!
The Public Test Channel (PTC) for Quest v59 is starting to roll out for Meta Quest Pro and Meta Quest 2 soon.
If you're seeing an issue or bug after updating to PTC v59 jump on over to ourGet Helpboard and search for any existing thread, if you don't find one, make a new thread. Please add the tag PTC v59" to the thread and in the title. This way everyone can look for just PTC v59 issuestoo.
It's best if you can post each bug you spot in its own thread, to keep track of individual issues separately.
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 going wrong.
We know it's tough when you run into a problem on a PTC build and want to thank you all again for testing out PTC and sharing your feedback! This feedback is extremely helpful to our engineering teams. We appreciate your interest and persistence in testing out the core functionality of software as we develop!
@Ryanality At this point I don't know what to do. Did you find a way to fix Wifi 6E connectivity issue on Quest 3 in v59? I tried all wifi configurations and 2 different routers. Some people also have trouble connecting. My Quest Pro connects just fine. I tried factory resetting the headset, router etc. Nothing works. I'm not alone with this. I can't use other bands because only 6 GHz is not crowded. I have like 2 weeks left only for return period and I don't want to give it up because I know once I am on 6GHz wireless PCVR experience will be great but I don't want to risk staying with non working 6GHz connectivity headset for who knows how long.
We’re making changes to how you receive updates for Meta Quest software. Automatic updates will be on by default. You’ll see a notification in Settings when a software update is available. You can delay the update for up to 30 days. You can still opt-in to receive automatic updates for your device. We highly recommend you keep automatic updates on to get the latest features and security updates.
You can control automatic updates by going to Software Update in your System Settings.
Today I put on my Quest 2 and found it updated to the following version v59:
Software update
System version
50670960040800150
Version
59.0.0.157.706.532516435
Running version
59.0.0.157.706.532516663
Operating system version
SQ3A220605.009.A1
I haven't the faintest idea if it's still PTC or the official version since the release notes have been released but Meta persists in not providing the official version number so as not to drive people crazy.
In any case, I find myself having to point out that I have completely lost tracking of the right controller.
He is no longer recognized.
Never had controller tracking/recognition/pairing issues before today.
My controllers are intact.
I tried changing the battery to a fully charged one, nothing.
I unpaired and re-paired, nothing.
After re-pairing the controller is seen by the Meta mobile app, but it is absolutely not seen by the Quest 2 which keeps telling me that it doesn't detect the right controller and to press any button to activate it, but nothing at all (the Quest 2 detects a few times, but randomly just pressing the home button).
The controller behaves strangely: its logo flashes but with a much stronger/intense LED light than normal, it vibrates randomly and doesn't want to be detected by the viewer. I have no idea what's going on.
Until the day before yesterday everything was working perfectly as always. I didn't use the Quest 2 yesterday; today I wore it and found it in this absurd situation.
v59 bricked my Quest Pro L controller. Currently struggling with an RMA process where I am getting conflicting reports on my order.
I did all possible troubleshooting methods I could source, and it just won't pair. Factory reset sets me back to v59, and I assume the same for the controller. Why is unproven firmware set as the hardware default?
Quality customer care is the best form of advertisement. I will avoid further ranting.
Update: Replacement controller paired with no issue
Nothing, even after restoring the Q2 to the factory settings, the right controller refused to work again. I think it was blocked due to an unsuccessful firmware update. In fact, the controller only pairs with the mobile app but was not tracked by the viewer, it did not have the 15 sensors turned on on the halo, it only had the LED under the meta logo which, after pairing, continuously flashed a very intense white (I think it is the equivalent of the white LED that gives SOS in morse code). After 4 resets of the viewer, the system tried 4 times to update the controller but the update always failed because the controller no longer communicated well with the device.
The visor only saw it appear and disappear in the controller icons in the quick menu, but it didn't track it at all.
in the end I also sent it today for RMA replacement.
At this point, given that v59 probably also includes the firmware update of the controllers, I advise everyone to keep them charged and be careful not to deactivate/switch them off and worse, replace the batteries while the update is in progress.
