USB 3.0 issues with Quest 2
I see lots of similar posts about things surrounding this issue but they usually get brushed off, I am hoping that making this post and outlining what I have done so far it may finally prompt a fix.
Essentially the issue is that when connecting with a USB 2.0 connection, the link is completely stable, it reliably connects for several hours and even if the headset is removed and left to "sleep", it reawakens and is still successfully connected (team events in iRacing if you're asking). When using USB 3.0 however, the exact opposite is true, generally speaking in the best case scenario, when keeping the headset awake the whole time, I can sometimes get an hour before a disconnect, however, nearly every time it goes to sleep, it disconnects and sometimes the connection will be lost within minutes of launching with no explanation.
For a bit of history, over the course of trying to find a solution to this issue I have: Used a USB A-C 3.0 cable, 2x USB C-C 3.0 cables (including Oculus' own), a USB A-C 2.0 cable, a USB C-C 2.0 cable, replaced my PC's motherboard with a Asus Prime Z-390A, so I would like to think this firmly rules out the frequently posed "solutions" such as better quality cables or using different ports. I have also tried resetting experimental features as I read that sometimes causes issues but this didn't have an effect, nor has making sure that video drivers and my motherboards firmware are up to date, disabled legacy USB support in my bios settings or ensuring there is no power saving settings activated on USB ports.
The most frustrating part of all is that recently I did a factory reset of the headset 'cause I couldn't think of any other fix and seemingly this finally gave me a stable USB 3.0 connection using the official cable, which not only lasted until I disconnected it (several hours), but also through cycles of sleeping and waking the headset. I then didn't play for a week and Oculus app version 38.0.0.51.727 (38.0.0.51.727) / headset version 38.0.0.63.727.351486028 installed themselves and now I'm back to the same problem of 3.0 not working and 2.0 being absolutely fine, the factory reset and experimental features reset has not had an effect this time.
To be clear, there have been no hardware changes at this time so given it did work as intended previously, it has nothing to do with cable quality or any mechanical issue. Any other insight of fixes that I have not yet tried would be appreciated, although mostly an indication that this is being sincerely looked into as a known issue not just brushed off as an outlier. Please let me know if you need any additional information and I'll post when I can.