Participant

Solved

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

1055 replies
309403 views

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.

This topic has been closed for replies.

TheLegend271265668Answer

Honored Contributor

Not a solution - Marking for visibility

Known Issue

Status: Fix rolling out in V64 - Public Release

Hey everyone! Back with another update. I got word from the team that we should start seeing improvements in the upcoming updates, however, they want to stray from promising any specific timeline for the fix just yet. I know everyone is still prepped for jumping back into their pop-up free VR experience, but this is the extent of information available to me at the moment. Hopefully I can find out and share more with you all soon! Thanks for remaining patient while the team works towards improvements!

Update (3/27/2024):

Hey everyone! After waiting patiently from the team for any updates I was able to share with you all, I just got confirmation that we should see a fix in the upcoming V64 build. I've tried to get word about a potential release for V64 & V64's PTC, but I haven't heard anything about it just yet. Be sure to keep an eye on the Announcements board, as that's the place we'll be posting about the PTC and Official releases.

If you continue to experience the error on a V64 build, please let me know! I'd also appreciate if you included your V64 software version number.

You can check in Quick Settings > Settings > Software Update under the Current Version Details section. The formatting should be 64.#.#.###.###.#########.

Update (4/5/2024):

Hey again! I'm glad to see that a lot of you are no longer having issues after the rollout of PTC's 64.0.0.419.370.583580230. After bringing more reports to our team, I was notified that the official fix hasn't shipped just yet, but it's a really good sign that improvements are being shown in the PTC builds! The official fix should be rolling out in the public release of the V64 build.

Thank you again for your patience, and please be on the lookout on our Blog or the Announcements board for when the public build is officially announced. Of course, I'll be notifying you all here as well once I find out more information!

Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably

Show previous replies

Skippy111taz

Participant

If anyone is interested, here is my latest response from yet another different AI person from Meta Support 🙄.

"I trust and hope this email finds you well.

Thank you so much for your response as well as the information you provide me with.

My name is Bulela from Meta Store Support and I will be assisting you today on behalf of my colleague.

From what I have gathered you would like to be assisted with your link cable.

Would it be possible for you to please attempt the following troubleshooting steps to get your link cable set up with the v62 version.

Can you please attempt the following troubleshooting steps:

Disconnect the Rift/Link cable from the computer
Disconnect your computer from the internet
Backup any necessary content
- You can find steps on how to do so by clicking here.
Reboot into Safe Mode
- You can find steps on how to do so by clicking here.
Uninstall the Oculus PC app using the Control Panel
- You can find steps on how to do so by clicking here.
Delete all Oculus folders from the following folder:
- C:\Program Files
Remove any Oculus folders from the following locations:
- C:\Users\YourUserProfile\AppData
- C:\Users\YourUserProfile\AppData\Local
- C:\Users\YourUserProfile\AppData\LocalLow
- C:\Users\YourUserProfile\AppData\Roaming
- C:\OculusSetup-DownloadCache
- Note: The AppData folder is usually hidden. Use these steps to access AppData.
  1. Press Windows key + R to launch the Run dialog window.
  2. Type %AppData% in the Run box and click OK or press Enter
  3. File Explorer will launch to the AppData\Roaming subfolder.
  4. Click AppData in the File Explorer address bar to show all three subfolders in the AppData location.
Restart your computer in normal mode
Reconnect your computer to the internet
Install the Oculus PC app again using the setup tool from our website here
Reconnect the Rift/Link cable and re-test the headset

Once the above has been done can you please attempt the following:

When USB Link Auto-Connect is turned on, Link will now automatically reconnect if there is a software crash or disconnection.
- You can find this setting by going to Developer in System Settings. Make sure Enable custom settings is toggled on, then you can select the toggle next to USB Link Auto-Connect.

Should you have any further Meta concerns or questions please reach back to us.

Thank you for your time and please have a lovely day further.

I'd be delight to receive your response!

Warmest Regards,"

Anyone feel up to waisting time doing this, go for it.

J

JayBoogie34

New Participant

Quest Pro user here with the same issue. Today, it went away, hopefully for good. I can't pinpoint what changed but I can maybe shed some light for someone else. I sim race and fly in VR so I have a ton of usb devices connected all at once. I also run a direct drive wheel which was new and installed just prior to the error message. (I also had just installed V62 which I believe is the culprit) regardless, I unplugged every USB and in plugging them back in, shifted which ports they were in. I started with my Quest cable first and made sure it was a good connection. I also secured the wire to the port so there was no tension on the cable. Fired up the pc, then began to plug the rest of the usb devices in, with my wheel being last. Finally, I broke three wishbones, kissed my lucky four leaf clover and rubbed a genie lamp and wished for success. To my surprise no notification sound as a plugged in my headset. It's been a few hours now and no disconnects. It seems there are more than a few pcvr gamers here who all probably have a decent amount of usb devices plugged in, so I'm wondering if it has something to do with power draw somehow and how the V62 software safeguards the headset in such cases. Maybe someone could try unplugging all usb devices and start with just the headset and see if they have similar results?

S

SteveJaye84

Participant

It's a good idea but I get the error just charging the device through the ac adapter while gaming standalone sadly. I think a few others do as well.

L

Lemonhead401

Participant

Perhaps someone (or everyone) should consider sending in their v62 headset for replacement to meta so that the engineers have plenty of headsets to replicate the issue. 😁

W

wwsoa

New Participant

In v62. Today when I tried to connect to PCVR on my laptop with a high quality usb3.2 cable it kept jumping out this same message, which never occurred before. After I changed to another port on my laptop, it disappeared. They may supply different watts. So I guess the issue is somewhat related to PD detection on Quest side.

J

javiermares

Up and Coming

how many hours have you used it without it appearing? i got it usually every few minutes but i've just done a session where it popped up after an hour. it can vary, it's possible that you will still get it again.

W

wwsoa

New Participant

It has been several hours since the warning disappered and it feels different from playing with the existence of the warning. When I played with the warning, for every few minutes there will gradually emerge some blurs in the middle of the screen, makes it unplayable. Replug it solves the blurs but another warning will come out and repeat the same failure in few minutes. Now it's completely fine.

S

StarKnight929603Author

Participant

Yesterday I took some time to do some testing with my wife, now we both have firmware v63 PTC and as you know since v62 we have that issue.

We started with our visors fully charged.

We let them discharge for about one hour unplugged under heavy load in standalone, no PCVR (using VRChat is a good test). No warning at all.

When they reached about 50% of battery charge we plugged them to our USB 3.1 5meters cables and the original AC charger.

We kept playing for about 3 hours while charging our visors and still no warning message at all,

When we had our charge above 80% we got the warning message again.

So the conclusion is now clear:

This issue has something to do with battery charge and device usb-port heating
It affects only Quest 3 devices with firmware v62 or greater
It affects only devices which are powered (AC or PC) and battery charge is above 80%

Temporary workaround is to let them discharge to 40-50% before connecting the USB cable, this will give you several hours without warnings. If you need to use it in PCVR for a long time the only solution is using wireless connections (Virtual Desktop is the best one) and keep it charging-discharging from 40% to 80%.

L

Lemonhead401

Participant

Call me crazy, but I don’t like playing tech support for a 500 dollar headset made by the biggest tech company in the world. I want to pay my money and have the company provide working products.

J

javiermares

Up and Coming

exactly my feelings. I’m more inclined to just return it. It’s already an awkward solution to not have a proper cable and to have to encode and decode. I could deal with that, I cannot deal with functionality breaking updates that take weeks to solve. TheLegend27

D

DannyIrlanda

Participant

I seem to have gotten rid of the issue. So far so good. I opted into the PTC last night last thing and I just checked and I'm now on v63 today and link is charging the headset and no 'liquid/debris' error at all.

H

Hchest

Inspiring

Quest3?

Tried PCVR? What cable? How long did you test?

D

DannyIrlanda

Participant

Yes, Q3. I'm just using the official link cable that I've been using for the last 2.5 years. PCVR is fine. I run through VD or Steam Link so my link cable is always plugged into the wall socket rather than the PC.
It's been working fine for about 6 hours now. I've plugged it in and out many times over those 6 hours to make sure it's still working and no issues so far.

D

DraxzVR

New Participant

Have they fixed this yet? My bud is having this issue

I

Icebrain

New Participant

I have problem using my usb 3.0, warning from time to time , same cable usb2.0 no problem !

J

javiermares

Up and Coming

Always eloquent and engaging Mysticle has given us voice, please spread far and wide in social media and tag other VR influencers. Tag Zuckerberg too (he uses threads, facebook, instagram ofc). Thank you! https://youtu.be/TYM4UCelD4I?t=266

S

StarKnight929603Author

Participant

Bad recensions is all Zuckerberg cares so if we really want Meta to consider this issue we need to ask all youtubers in this sector to talk about it and let other people know how BAD Zuckerberg's company customer support is.

Show more replies

Update (3/27/2024):

Update (4/5/2024):

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO