(Resolved) Known Issue - V62/63 USB-C Debris/Water Warning

[Star.Knight]

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.

[Veisenberg]

Got this twice today. I normally play without a charging cable attached because I don't use the headset for very long. But today I was attempting to do a bit of sim racing so I connected a rather expensive USB C cable and used the charging plug supplied with the headset. It happened once whilst playing smash drums which ruined my in game score. Then it did it in Assetto Corsa, competely pulled me out of the race, flashed up with the USB message and then went back to the track as if nothing had happened. By that time I was in the wall... I turned the headset off after that.

If I can't rely on the hardware to work without silly false possitive errors flashing up on screen then I'll be seriously concidering selling this Quest 3. If I can't use it for what I want to use it for, what's the point in keeping it?

[JonnoW]

I'm amazed that this isn't an absolute priority issue for Meta and at the top of their list of fixes.

I purchased the Quest 3 a few weeks ago to replace my Reverb G2 primarily for sim racing. So far I've managed just a couple of laps before this issue popped up and it's appeared constantly every since. It's currently unusable for wired pcvr despite this being a selling point for the headset.

I have until early April for my return window and will be doing so if this issue isn't fixed by then. What a thoroughly disappointing experience.

[Hchest]

Its a dealbreaker for simracers, known to be early adopters of VR, real shame!

[Veisenberg]

This post was from 6 MONTHS AGO Meta! WTF!

This issue is clearly something you're not going to fix. So this Quest 3 is useless for what I want to use it for. A real shame. But no problem I'll try and return it to the retailer for a refund on Monday.

To everyone else, good luck.

[Halaster]

---

@Veisenberg wrote:

This post was from 6 MONTHS AGO Meta! WTF!

This issue is clearly something you're not going to fix. So this Quest 3 is useless for what I want to use it for. A real shame. But no problem I'll try and return it to the retailer for a refund on Monday.

To everyone else, good luck.

---

It is actually much worse now than when that thread was started. There were easy work arounds back then that no longer work. From that post:

•  The issue seems to only occur if the other end of the cable is not plugged into the computer. 
• Therefore, if I plug the cable into the computer before plugging it into the headset, no issue occurs.
• If I un-plug the cable from the computer before I unplug it from the headset or plug the cable into the headset before I plug it into the computer, the issue occurs. 

There is no way to work around the problem now, and the order the USB cable is plugged in makes no difference at all. It is just plain broken for me 100% of the time regardless of cable types or brands.

They have at least also fully acknowledged this issue now, and appear to be actively working on fixing it, which can be seen with the update posted on the first page of this thread.

[Veisenberg]

Yea, I mean, I've tried everything. I've tried having it charging directly from the wall socket using a meta link cable and the official charging plug. I've tried using a third party cable plugged into the wall, I've tried a meta cable plugged into my PC, then again with the third party cable. But every time I start a game up it'll do it. It's even doing it when playing standalone games like Smash drums. No matter what I do or what I use if it's charging whilst I'm using it I get that error. Which is why I say it's no good for me and what I want to use it for (sim racing, some races go on for hours)

So, given that this has been an issue from launch I really can't see them fixing it any time soon which means I'm going to have to sell it or attempt to get a refund. Which is a shame, because I really like the headset.

[Halaster]

---

@Veisenberg wrote:

Yea, I mean, I've tried everything. I've tried having it charging directly from the wall socket using a meta link cable and the official charging plug. I've tried using a third party cable plugged into the wall, I've tried a meta cable plugged into my PC, then again with the third party cable. But every time I start a game up it'll do it. It's even doing it when playing standalone games like Smash drums. No matter what I do or what I use if it's charging whilst I'm using it I get that error. Which is why I say it's no good for me and what I want to use it for (sim racing, some races go on for hours)

So, given that this has been an issue from launch I really can't see them fixing it any time soon which means I'm going to have to sell it or attempt to get a refund. Which is a shame, because I really like the headset.

---

While it has been an issue from launch, it was not to this scale. It was one of the most recent updates that caused it to go widespread on a large number of headsets. It was also not until very recently that they officially reproduced it and started working on it. So I expect/hope they will fix it soon.

[er0s3nnin]

I mentioned a few pages back about it being an overclock/unstable power situation and I have found since then that if I turn off 120hz and body tracking I don't see to have the same issues with the usb-c or the with the other issue I was having (graphical artifacting - The so called "rainbow sparkles" mentioned every where else on this forum).  The only caveat to that is if I plug the cable into the headset without the other end already in the PC then it does still give the debris warning.

Basically it seems there are two scenarios for the warnings, Firstly, if the cable isn't plugged into the computer first it just fails straight away (PD negotiation issue maybe?) and then secondly, if the headset is being pushed too hard and running too hot!

Usually, if I don't get port disconnects and the debris warning first, then I will get the sparkles artifacts which get worse and worse until either the port error and/or the app crashes. This happens in native apps too that aren't even using the cable if you just have the cable plugged in.

Regardless, I haven't had much time to test it as I have been busy but it was happening to me earlier so I turned off 120hz and body tracking and then it worked fine for the next 2 hours (and the fans were much quieter).  But essentially thats just one test so maybe I was lucky but it's the longest I have gone without issues and I had already been using for a while when the early indications it was coming started (the "rainbow sparkles" and the passthrough flicker)

[Hchest]

It happens regardless of having the cable in the pc or not, regardless of having any cable attached, regardless of having the headset on 120 hz or not.

Its not a "in this case or not" its a BUG that started for many ppl at V62. 

The community trying to figure it out, and posting their findings seems to leave Meta with ammo to say "its because of user error"

[Davilos]

So I performed a litttle expensive experiment. I went out yesterday and bought a new Quest 3 from Target. It’s on V62 and has has zero issues from any of the cables I tried. This issue seems to be a mix of hardware and software.