Skip to main content
New Participant
November 12, 2020
Solved

White horizontal stripe across screen while using link

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?

PokebertAnswer
Participant
March 20, 2023

UPDATE: POSSIBLE WORKAROUND/FIX USING REGISTRY EDITOR

As I theorized above, this issue does NOT occur for those who use Air Link. Air Link uses HEVC and uses 1 slice for its encoding, whereas wired Link uses H.264 and 5 slices for encoding. Whenever the white bar issue occurs, it is very likely the final 5th slice experiencing an error in the encoding. If you pay close attention when this occurs, you will likely notice it only occurs in the bottom slice of the screen.

To use this workaround, open Command Prompt and use the following:

  • reg add "HKEY_CURRENT_USER\SOFTWARE\Oculus\RemoteHeadset" /v "numSlices" /t REG_DWORD /d "1" /f

I will be experimenting with this for the next few weeks to make sure  I do not get the white bar issue!

Original Post on REVISITED thread:

I have noticed that this is related to the horizontal encoding slices that are visible only through the Link Cable. A very easy stopgap solution would be to offer a toggle in the OculusDebugTool that allows us to turn OFF these encoding slices. Additionally, the encoding slices do not appear with Air Link and thus the issue has almost never occurred wirelessly according to both personal experience and these threads.

1125 replies

Participant
April 16, 2021

Guys, I'm starting to be super triggered by this issue and Oculus itself. 😞 Oculus support stopped communicating after few automatic emails. It looks like they're totally ignoring this serious issue. I have no idea, how to force them to focus on this and fix it. Please everyone again, write an email to support with link to this forum, there are quite a lot of us. I'm considering to switch to another headset and throw Quest 2 through the window, this is insane.

April 16, 2021

Oculus told me it was a Codemasters issue and ended it after that. It's not a Codemasters issue. I am using my Rift S with Dirt Rally 2.0 and the Quest 2 with other games. Ridiculous. But at least I can put my desk in my virtual space. Wow! Great work!

Participant
April 16, 2021

Yeah, It's definitely not a Codemasters issue, since there are users, who has this exact problem in iRacing, Flight Simulator and other games. It started happening after some Oculus update, I've never had this problem before and kept playing Dirt 2.0 for hours rock solid. Now? Needs to restart Link every 10 minutes to get rid of that d.a.m.n. white stripe. 😕

Participant
April 16, 2021

Hi all,

I only use ACC pretty much, was working always fine and yesterday it started. What a nightmare.
Running a Ryzen 5900 + RTX 2070 Super + Quest 2.

 

This is what I tried:
Oculus VR - problem within 10 minutes white stripes
I read this: video how it looks like 
I can see the same distortion that suggests compression issue. There are up to 5 bars, but never the same have this issue. (looks like new GPU)

Oculus Mirror looks just fine
I reduced power + temperature - no luck
Steam VR - no luck + instable frame rate
USB 3.0 port instead of 3.1 - no luck
better link cable (not official) - now connecting via USB 3.0 according to Oculus rift. (Turns out I've been on USB 2.0 for months), but after one good race, still the same problem.
disable Oculus beta and install V27 - no luck + severe depression starting
install nvidia v457.30 driver, clean install - BOOOOOOOOM

 

Been driving for an hour now and works just like it used to
Good Luck

April 17, 2021

Never have done this before. Do you just find the driver you want and download it? Thank you. 

Participant
April 17, 2021

I have had this issue on and off with all drivers and previous Oculus versions. Sometimes unplayable, sometimes no problem for hours. Right now I am running latest NVIDIA 466.11, ver 28. haven't had issues ( hopefully I haven't Jinxed it.) What i have done is S#$^ tons of tweaks in NVIDIA 3D settings, Oculus Tray Tools and Flight sim. Too many to know what helped; but something helped. I suggest, if you have done any tweaks, to set everything to default, and then turn off or dumb down settings until it goes away.

 

I think this issue is related to bit rate, USB bandwidth utilization and the NVIDIA encoder. it could very well be Windows 10 handling of USB protocols. You know like how that one USB stick that works fine everywhere but refuses to work in the one port that's accessible, but everything else works fine in that USB port? that kinda nonsense.

 

Also try something like Game Boost. Something that disables other programs while you are running the game in case something else is hijacking a process.

It could also be an artifact of Direct X 12.

 

Another part is that NVIDIA's driver also installs a USB C protocol process. From what I have read this is not a USB driver per say but a process that allows NVIDIA cards to use USB as a Video port (like HDMI.) As far as I can tell its version hasn't been updated in any of the recent driver versions, nor have any of the Microsoft/Motherboard USB drivers.

 

So overall not necessarily an Oculus fault, or NVIDIA fault, or Windows 10 fault, but a combo that is too unpredictable for the engineers to recreate effectively. If Oculus could be run with HDMI, or Link could be done another way, then the the culprit could be found.

 

Cheers

 

Participant
April 19, 2021

Update: I am white strip free until I use AERUS ENGINE to OC my GPU. It stays messed up until I reboot the computer.

Participant
April 21, 2021

Issue still persists with v28 on the quest 2 and v28 the PC. 

GPU is not overclocked. 

April 21, 2021

I have a 3080 not overclocked and it's happening. 

New Participant
April 23, 2021

Hi lads, 

 

Went into the exact same issue than you since v28 (or perhaps earlier, didn't use it for a while). RTX2080 and all the stuff...


I even had this on oculus home.

 

I solved (apparently, no promise, no false hope) the issue by lowering in Oculus Debug Tool the encode resolution width from 4000 to 3000, and  encode bitrate from 500 to 200. For now it's fine, I'll tweak this later. 

 

Everything on my quest 2 is by default, except the frequency (90hz)

 

Everything else is disabled : ASW and all the stuff, only was remaining these parameters. Hoping to have helped a bit. 

 

I priorily tried all the stuff you've apparently already tried, with no success, I even went to 457.30 nvidia driver... Before realising that I already was on this specific version ^^

 

Btw a smart tip : Don't systematically update your GPU drivers if everything looks fine on your videogame sessions... ^^

 

Nicolas

Gladders67
New Participant
April 23, 2021

Many thanks for the tip Nicolas, delighted to say it worked for me too! I started to tweak the values back up, each time turning the headset off and on - got back up to encode resolution width 4000 and all was still fine. Pumped encode bitrate back up to 500 and....all fine still.

I can't work out why reducing the figures then increasing back to original levels doesn't cause the white stripe error to reoccur.

It's mighty odd but at least I can say 'white stripe begone' - at least for tonight 🙂

Thanks again for the heads up on this one.

Cheers

Martin

Participant
April 24, 2021

Thanks for the information Nicolas, I will try this solution.

It is a shame that it is the Oculus customers who try to solve this problem, the help of the Oculus developers would be appreciated...

From what I have observed with my hardware, the problem is with Oculus link and nothing else.

I played 2 months without ever having this problem, it appears just after the update to version V24 (beta), I went back to V23 and the problem disappears for 15 days (at least 40 hours of play), and when V24 becomes official and its  installation is mandatory, the problem returned immediately afterwards, never to disappear again, whatever the versions of oculus, nvidia driver, and so on...

Maybe some defaults values about encode resolution or something like that have been changed between oculus version 23 and 24, how could I know if only users are concerned about this problem ?

 

When this problem occurs in game (variable time between 1 and 10 minutes), I pause the game, I press the Oculus home button, I close Oculus link, I restart it and the white stripe disappears .... for a few minutes .

It's hell to play in these conditions, and I'm starting to get really disappointed with Oculus, not the hardware, but the non-existent support for this kind of issue.

I don't think this is a very complicated issue to reproduce, so it's probably pretty easy for a development team to diagnose.

I'm working on fixing this kind of issue in another area, our only real issues are troubleshooting isolated cases very difficult to reproduce, the rest it is a question of priority or will.

If they are convinced that this problem does not come from Oculus link, let them explain to us why, and especially what is the origin of the problem, because as long as they do not communicate on the origin of the problem, it is is that they do not know where it comes from (including Oculus link).

Participant
April 24, 2021

Just read through the entirety of this thread. Been having the same issue + even more artifacting in a very specific scene in Boneworks that I've been using to test this. Tried everything from new cables to new ports to changing any setting I could think of or saw in this thread. All to no avail. Virtual desktop gives me none of this artifacting so it must be a link issue. I emailed support earlier but I don't expect anything helpful from their response. Hopefully airlink's performance is good as using link has become unplayable at least in boneworks and Asgard's wrath.  I have an RTX 2080 super and a ryzen 7 5800x neither of which overheat so I know my pc isn't the issue.