White horizontal stripe across screen while using link

[Panzer_mk2]

Headset seems to work fine stand-alone.  I use the headset with IRacing, and often (not always) get a translucent horizontal stripe across the screen after about 15 minutes or so.  It doesn't feel like the headset is overheating.  This doesn't show up on the screen mirror on PC, or if I "mirror" with the debug tool.  Is this likely a failing display or is there somewhere else I should look?

[Xerberuz]

So after being gone for hours after changing the bitrate, the stripe came back last night :(.  I uninstalled the oculus software and deleted all oculus temp files and the ones in the app data folder and is back to being gone.  Will report back if it comes back.  This is really frustrating.  Is like sometimes a small change gets rid of it temporarily and then is back.

[kodiz.mdq]

Please FIX THIS, Ques2 is unusable for PCVR with this problem. I was telling everyone about how awesome the Quest and Quest 2 are, (yes I have both) and now its broken, and you dont fix it.   maybe if we all the users do our part on social nets, the NSP score goes down and they look eventually this problem and start solving it. 

The white stripes beggins to show at random times, sometimes at the first minute .... sometimes at 10 minutes after the encoding started. stripes and artifacts everywhere. Can not recomend it anymore. It was amazing one time, now its time to save for a Valve Index or and HP VR one.

[Poiju]

I've tried multiple, suggested fixes in this thread. We need a work around or at minimum, a better response. @Ryanality 

[peqpy]

This seemed to fix the purple/pink/white horizontal lines at the bottom of my lenses and I can finally use Oculus Link to play my games now thanks a lot. 

[Xerberuz]

I followed this fix and it seems to have fixed the white/purple/pink stripe issue.  I have an RTX3090 so I can confirm that it works on this card.  I only tried it on VRChat for a few minutes and will try it with Demeo  later on, but I am confident that it solved it since VRChat would show it a couple minutes into playing consistently.  Thanks a million for the instructions!!! 

[benji94]

I've read through this entire thread and have found it both enlightening as well as disturbing that this problem has been going on for so very long.  I don't have the technical expertise to solve it myself but I thought at least I'd offer my latest experience with this issue that might give some insight for the technical geeks (and I use the term with the utmost respect) that are working on it.

First my current system:  i7-6700K overclocked @4.5; FE RTX3090 GPU (latest driver 497.29); 32GB RAM; WINDOWS 10 HOME 64 bit (ver. 21H2); and Oculus Quest 2.

I principally use the headset for iRacing via the official Oculus link cable and I've only had the issue occur when in iRacing.  I don't ever recall seeing it in any of the other Oculus PCVR games/apps though honestly haven't been in many long enough to say if it develops or not.

I've had this issue occur, seemingly randomly, awhile back, I think sometime in mid 2020 is my best guess.  At that time my gpu was an RTX2080 Super.  When it occurred I would play around with the bitrate settings in the ODT and, if seemed, to solve the problem.  At least for awhile.  And then maybe weeks later it would happen again.  I would adjust the settings, reboot everything, and then I'd be fine for awhile.  This led me to believe it was in someway connected to bitrate settings.

Then the issue disappeared for me for quite awhile.  About a year ago I was lucky enough to snag an RTX3090.  All was fine and the issue didn't develop for me all last year as I recall.

I hadn't updated the Nvidia drivers since last summer so I just recently decided it was well past time to update.  On 1/6 I updated to the current Nvidia driver ver 497.29.  By the way, I don't install GeoForce Experience software and always run Display Device Uninstaller (DDU) in safe mode prior to any GPU driver updates).

(An aside:  I learned the hard way to always use DDU.  When I first got my Quest 2 and after it was updated to run 90 fps I was unable to get it to run more than 72 fps.  I engaged in the Oculus Support boogey woogey shuffle for nearly two months which included every Oculus suggestion mentioned in this thread, most of them multiple times, as well as Oculus replacing the headset, and trying different cables, USB ports, and on and on.  It kept getting bumped up the Oculus Support ladder until FINALLY a fellow had me run DDU and THEN reinstall the graphics drives.  BINGO! that worked and I was able to use the headset at any fps setting I desired.  Just thought I'd include it hear in case it might save others the aggravation I went through.)

Now back to the original programming....after I updated the Nvidia drivers all was fine UNTIL about 3 or 4 days after 1/6 there was a WINDOWS update.  The very next day I saw the white horizontal band begin to form on the bottom of my headset display while in an iRacing session.  Hmmm...haven't seen that in awhile I thought but ok I'll just adjust the bitrate down.  Nope...didn't work.

I then embarked on days and days of testing.  I tested the bitrate settings from default to max at 50 point increments.  No change.  I tested Oculus fps settings from 72 fps to 120 fps.  No change.  Within each fps setting I tested each and every pixel density setting from 1.0 to max.  No change.  I investigated possible heating issues with the headset and my pc, as best as I could anyway....all is running cool as far as I could see.  I ran DDU and reinstalled the previous Nvidia drivers.  No change.  I ran DDU and reinstalled the current drivers.  No change.  I rebooted the Oculus headset and reinstalled my Oculus software.  Nope...no change.

At some point I found this thread, read through every single page and tried every suggestion that I hadn't already tried..  No change.

What was especially frustrating is how random the problem is.  I could be in a race server and the problem wouldn't develop.  Change to a different server about an hour later and then it would.  I started to wonder if it was a connection issue of some sort and checked me internet connection and modem.  Everything checked out ok, again as far as my meager skills allowed.

I was at the point where there were only two options, either live with it and wait for Oculus to finally figure it out and correct it with an update OR employ the workaround posted by "fyte" which seems to working for some.

So day before yesterday (1/13) I ran two different practice sessions each about an hour or so long.  In each session the problem occurred as usual at around the 45 minute mark or so (and gets progressively worse from there).  I finished around 11 pm and as I was shutting down my pc there was the notification that there was another windows update.  Ok, so what's new???....I chose "update and shut down" and walked away.

Yesterday (1/14) morning I fired everything up and ran another practice session.  The white band never appeared.  Strange, I thought, but then maybe I hadn't run long enough so I didn't think much of it.  Then, last evening I ran a 3 hour race.  All the while expecting the white horizontal band to appear..  IT NEVER DID!!!  All was fine for the entire session.  I couldn't believe it.  And I had made absolutely no changes to ANY of the Oculus settings.

So today I ran another long practice session and it still hasn't developed!

Obviously, I need to do more sessions to be sure but it sure looks like there is some correlation between Windows 10 updates and this issue occurring.  For me, it didn't start until after an update and then it went away after another update.

Sorry for the length of this but I felt that the details are important.  With any luck it will at least give some insight to those who know a ton more than I do about all the sorcery that makes all this stuff work.  I'll follow up if it crops up again but in the meantime I'm going to keep a close watch as well as a log of when any updates occur with Windows, Oculus, and GPU drivers.

[Xerberuz]

Thanks so much for the detailed post.  I have a similar setup as yours and have gotten it to work with Fyte’s work around, but I will check if going back to the normal oculus drivers and support files and updating windows works for me.  Thanks again.

[Xerberuz]

• So unfortunately this did not work for me :(.  I got the latest windows updates, latest nvidia drivers (Version: 511.23 Release Date:01/14/2022), and I booted into safe mode, uninstalled the oculus software and got rid of all temp and app files, then re-installed the oculus software.  I jumped into VRChat, and for like a minute it looked fine, and then it started showing the white strip at the bottom again.  I am going to revert back to  Fyte's fix.  Thanks for trying to help though.  I hope that yours keeps working ok.  My pc specs:
  
   Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz 3.70 GHz
   64.0 GB of RAM
   Nvidia RTX-3090

[benji94]

Well, sorry to hear that.  So far so good here but I guess it could change at any time.  I'm still on 497.29 Nvidia drivers so I will go ahead and update to the latest and see if I'm still ok.  If it comes back though I'm done wasting time and will just do the work around offered by Fyte.

Its crazy that Oculus isn't addressing it, or if they are at least acknowledge they are trying.  I thought about submitting a support ticket but so many have done so already and, frankly, I saved all of their previous email suggestions to me and so I think it would be just as productive if I simply forwarded all of those back to myself and save everyone some time.

[Xerberuz]

The only issue I am running into with Fyte’s fix is that the drivers make so the mic in the oculus doesn’t work. I kind of need that for when playing Demeo and VRChat with friends. I followed his instructions and confirmed that the sound works but the mic stops working, so I ended up going back to the newer drivers and putting up with the white band so I could have a working mic.  I ordered the Varjo Aero and hoping it ships soon, I would like to play PCVR games without that darn line!