02-07-2024 12:44 PM - last edited on 04-23-2024 10:21 AM by TheLegend27
v62 has a big problem with USB port sensor (found the very same issue on my Q3 and the one of my wife)... when used with an extension cable (even if it is a quality cable) from time to time star showing the debris-water warning message. Of course there is no debris or water, just a nasty software false alarm.
Solved! Go to Solution.
03-02-2024 06:39 AM
The method i mentioned works 100% of the time for my.
After Error Message I click it off for 5 sec and back on again
and the Errors are gone and its charging and working as expected.
03-02-2024 06:46 AM
Sure, it doesn't work for anyone else here though, and saying people are "crying" is extremely weird. Do you click "ok" on the error message before or after you use the on/off button to turn it off and back on again? Not that this minutia will likely make any difference to the fact that this doesn't work.
03-02-2024 07:31 AM
Ya man. I never said it was good enough this way but it does allow me to use my quest 3 without issue for the interim. Been able to race on iRacing, for over a week now, without any problems. I rarely have the time to play long enough that the battery completely discharges anyway, so until a proper fix is released this is how I'll be playing pcvr.
I just wanted to point it out just in case some people hadn't thought of it. I see lots of people claiming that their headset is a brick right now, which is completely untrue. You just need to not plug it into a power brick for the time being and just use the usb c port on your pc and it'll work just fine. Not ideal, but it works and you'll be able to use it. Also, like I stated in my last post, it doesn't seem to discharge as fast, while only plugged into usb c, as it did before the v62 update. Pretty sure I could easily get approximately 10 hours of use out of it right now before it drains. Unfortunately, I do have to adult for most of the day and will probably never be able to test how long the battery will take to die.
03-02-2024 07:33 AM
Not true at all. I have it plugged into a usb c port on my pc and the message pops up every minute. It is a brick indeed. I’m on an x670 motherboard with usb c 3.2 and it has become a complete brick since the v62 update.
03-02-2024 07:34 AM
The reason it probably works for you is because your usb c ports are older spec and don’t have power delivery.
03-02-2024 07:37 AM
10 hours? I lose 30% battery every hour, while plugged in to USB-C only and I have USB 3.2 gen 2v2 and USB 3.2 gen 2. And high wattage cables (240W). On iRacing 120Hz
03-02-2024 07:47 AM
Has anyone tried to drop resolution and frame rates to see if the reduced power drain works as a workaround or is that not technically possible?
03-02-2024 07:55 AM
I am in the same boat for over a week, my motherboard has 45w capable usb c port which i connect to using meta fibre optic cable and i get this message everytime i connect my headset, and only way is to click ok on that message and restart my headset and it connects well with no problems with link and fine all session but when i get off and unplug and replug its same issue again, very frustrating, i beleive its a sensor issue most likely.
03-02-2024 08:09 AM
Ya man. As I stated in my original post my headset only seems to discharge about 6-8% per hour now. 2 hour stints in iRacing, which is about my avg, only seems to bring it down to the mid to high 80s. This is using the official meta link cable. Like @Magiccarpets (sorry this doesn't work for you, btw) stated, my usb-c probably doesn't have power delivery but this seems to be my drainage rate right now. Before V62 it was horrible. Hence, why I bought the other cable, which, obviously, gives me the error now. I race on 90Hz instead of 120Hz. Maybe that's the difference. Seems an excessive difference but who the hell knows. As I also stated previously, your mileage may vary. Just sharing what worked for me in the hopes that it would help others get back to doing what they enjoy. Hopefully see you guys on the track one of these days.
03-02-2024 07:20 PM - edited 03-02-2024 07:22 PM
"You just need to not plug it into a power brick for the time being and just use the usb c port on your pc and it'll work just fine."
No. Can't play the games I play being tethered to my PC. I HAVE to be untethered. And what difference does it make anyway if its plugged in it'll most likely pop up with the error. Even though I do connect it to my PC to copy files (and the error hasn't popped up doing that) I play wireless PCVR only.
For a racing game I guess its fine. How do you deal with motion sickness? When I play fps games with locomotion movement I get motion sickness within seconds. I've played a racing game once at a VR arcade and it was not enjoyable at all. I was on the verge of throwing up. In racing games you're moving much faster so the faster you move the worse it is.
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
Check out some popular posts here:
Getting Help from the Meta Quest Community
Tips and Tricks: Charging your Meta Quest Headset