3 weeks ago
- last edited
Wednesday
by
TheAntiSocializ
I am sick of this happening every time the devs roll out a new update.
Oculus app updated this evening, Quest Pro headset will no longer be detected via cable connection, only wireless.
Doesn't matter if I'm opted into PTR, or opt out and uninstall the new drivers that came along with this.
If anyone manages to get themselves out of this situation lemme know how ya did it!
Solved! Go to Solution.
3 weeks ago
The last three weeks have shown me I need to invest in a HP Reverb G2 and leave Meta behind. Meta is only interested in Wireless headset gaming and don't care to support PCVR, Its painfully Obvious now. The only thing they're lacking is an Official Statement stating their stance on PCVR support. I knew a day would come when Meta buying out Oculus was a bad thing. I think that day has come.
3 weeks ago
Hey there, @Rdrockt! We were just checking in with you to see if you were still needing assistance. We look forward to hearing from you, and want to ensure you're well taken care of. We hope you have a great day!
3 weeks ago
You have to be kidding me. Link Cable PCVR connection broken with the update a few days ago. Fixed with the hack/workaround of opting in to the PTC. Broken again today. I'm thoroughly fed up with this. Air Link isn't an option.
Here's my version info if it remotely helps anyone who actually might be QA'ing this awful software:
Oculus App Version 57.0.0.238.153 (57.0.0.238.153)
This needs to be fixed sooner than ASAP. This is just ridiculous.
3 weeks ago
I've done all of this. There was an answer that involved allowing a Beta version of the Oculus driver to load. That worked until the app pushed a new update. I am now having the issue again.
3 weeks ago
This issue has returned the very next day. I've tried v57 and v56.1 and the Oculus app again says my headset is not detected...
3 weeks ago - last edited Wednesday
I'm marking this comment as the solution so that people can know this issue is currently being looked into.
Hey everyone! I just want to say thank you for the information and everything provided. Our engineers have let me know that they are now currently working on getting this resolved.
I'll be checking in consistently and editing this comment to let you guys know the latest news.
Again, thank you and I apologize for misleading you with the solution. It's necessary for everyone to be able to see my comment.
[Edit 9/13] - This developer setup video is not an official Meta video, but someone has provided it within the thread for the meantime as a possible workaround. Along with that, the following has also been suggested:
3 weeks ago
same issue. Ptc fixed it yesterday - broke again today
3 weeks ago
same problem with my quest 1
3 weeks ago
Same. It’s really really frustrating.
3 weeks ago
A few days ago, I got the 56.1 and my PC couldn't find the headset after it installed. Followed the recommendation of going to the beta channel and it worked, until now... I got a notification about an update and new drivers, not neither the regular or the beta channel works. As an IT professional, I know that sometimes bugs get through testing but this is beyond ridiculous. This is like the 3 or 4 time you guys break PC VR. I was waiting for the Quest 3 to drop to upgrade but I think I will explore other options unless you include an opt-out of the automatic updates.