dude this issue has been driving me crazy. i recently took out my headset after a long time of no use, updated everything, and this occured. i had no idea this came from v2.1. no matter what i googled i couldn't find this issue, i thought it was a hardware issue.
cook1e0 It might still be a hardware issue.. Most people don't have the problem, I don't and the group of people I play with don't either.. Only around 8 people according to the OP has reported it. Out of millions of headsets with v2.1 that isn't many. It's not a wide ranging bug. If it was thousands of people would be complaining. As stated in other comments, you should report the problem through the headset bug report system and they can discover if you need an additional update or possibly a hardware issue. As so few people are reporting it, I'm thinking it might be hardware but that's not certain. Hopefully it's just a glitched software update. 🤞
a 'faulty update' doesn't magically create a highly specific rendering bug that only affects 2D UI overlays while leaving full 3D environments completely intact. that's a compositor issue in the code, not a broken download. people are already submitting bug reports, but denying the issue exists just because you and your 4 friends didn't trigger the bug doesn't help anyone.
cook1e0 Where did I deny the issue exists? Read all my comments. Not one time did I deny it exists. It obviously exists for a small number of people. It's not just me and 4 friends. Lol. There are a tiny number of complaints. It's obviously not widespread. If the problem was as you have theorized, obviously incorrectly, , if there was a problem with the code itself, we would ALL have exactly the same issue. Your theory makes no sense. I understand it's frustrating but don't take it out on me. 😉
if it was a problem with the code, we would ALL have exactly the same issue
literally anyone with a basic understanding of software knows that's not how this works. code doesn't execute in a vacuum. a compositor bug can easily trigger based on specific memory states, minor hardware revisions, or even just the constant background a/b testing that meta does.
it is explicitly not a 'glitched software update' and it's definitely not a hardware issue. you've genuinely said nothing of value in this entire thread other than trying to downplay a documented bug. why are you even commenting if your only goal is to run defense?
