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

Inspiring
August 27, 2021

I got PC app version 33.0.0.22.194 now...

 

Not solved... 😩

New Participant
August 27, 2021

I tried absolutely everything.

  • all USB port
  • Couple of cables
  • Many possible settings in OTT debug tools.
  • Factory reset Quest 2 headset
  • Reinstalling system
  • Under clocking 30 series nvidia cards
  • Re-installing oculus home
  • running on 457.30 nvidia driver
  • Changing bit rate to fixed number then back to default

Nothing helps.
It’s Very frustrating. WHY! Some have it and some don’t.
Cant understand.

Up and Coming
August 27, 2021

FYI

If you did not buy your game from the Oculus Experiences Store you are OUT OF LUCK for Facebook to help. According to them, It is up to the developer to fix the issue not Facebook.  Here is a clip of the support response:

 

I can appreciate your concern and want to expand your experiences in VR. However, Resident Evil Village and several of those games mentioned in Oculus Forum thread you kindly provided are not available on the Oculus Experiences Store, which means they have not been tested to work with our headsets and are not guaranteed to be optimized.

I know that this is not the news you want to hear, but if you're experiencing an issue with a SteamVR game, please reach out to their support team and they may be able to help you either reach the developer or get the game running smoothly. "

August 28, 2021

I have this same issue and it starts while in Oculus Home before I load ANY game. This IS an oculus issue!

Participant
August 27, 2021

Except that the problem is absolutely not related to other developers, and that it concerns Facebook and ONLY Facebook.
The problem is linked to compression/decompression issue which is managed by Oculus Link software, to pass the signal between the PC and the Quest 2, and unless I am mistaken Oculus Link is a software developed by Facebook.

This is THEIR problem, not that of other developers.

Participant
August 27, 2021

Especially when the whiteband also happens in Oculus PC menu, without even starting SteamVR.

August 28, 2021

in Oculus Debug Tool, set Encode Resolution Width (ERW) to 3664. If you get this white band again, decrease it a little bit (3600, for example). I had this problem in Dirt Rally and DR 2.0. With ERW 3920 - the problem exists, with 3900 not anymore. Find your settings! It takes not much time.

New Participant
August 28, 2021

Thank you but changing resolution not works for me. No changes at all. I trued many possible setting.

They only setting make a difference is FOV. When I set to 0.9 0.9 lini is thinner. More bottom.

jeremepowers
Participant
August 29, 2021

Issues is still happening on Version 32 of the headset and Oculus App Version 33.0.0.22.194 (33.0.0.22.194).

 

I have (since my last post) also tried a new cable with the same results. At this point I have tried everything possible and have determined like many of you this has to be an Oculus Link issue.   

 

I was finally able to capture a screenshot of the white box on the bottom of the screen on Demeo running from the Oculus App. 

 

 

I have been updating Oculus support with everything I have tried. I suggest everyone do this. 

 

I have also brought this issue up on some of the bigger "Oculus Quest / VR" YouTube channels just to have my comments removed. I Also suggest everyone start trying to get the word out on this issues so Oculus has to acknowledge it. 

 

Participant
August 29, 2021

today i was try again....the same after 10 min boom white on the bottom....i know that over air link not have this issue ...but need to lower the settings to work smooth ...sad that oculus ignore this issue ...need to take ticket support ..and show that we exist...and they must to fix it ...i hope so ...and i hope that someone fix the problem 

Participant
August 30, 2021

Still continuing my technical support ticket from Oculus. They requested to disable Oculus Tray Tool, MSI After Burner, and send the logs. Here is my reply, which proves that it doesn't come from any external software, hardware, or even from the Quest 2 headset itself :

 

Hello,

As requested, here are the logs after disabling MSI AfterBurner, and OculusTrayTool. I couldn't disable SteelSeries as it's the interface for my keyboard to work.

I also uninstalled SteamVR.

A few notes :
- I only have MSI afterburner since 1 month,
- I only have SteelSeries since 3 monthes,
- I have a 3080 ti since 1 month, but had a 2080 ti since October 2020 (date of Quest 2 purchase),
- I have been having 3 different Quest 2 since October (RMA'ed two for dead pixels)

Considering all these infos :
the whiteband problem exists since late 2020 (I didn't tracer the HMD firmware and PC app exact versions since it happened though). So as this issue appeared on 3 different units, through 2 GPUs and different Windows setups, it doesn't seem to be linked to the HMD, but rather to PC encoding / HMD decoding.

About the today's logs :
A whiteband appeared nearly as soon as I launched the Link, just inside Oculus menu.
times 19:01, 19:07.

I managed to capture the HMD lens display, attachment "Capture_whiteband_in_HMD.JPG".
I then capture a PC screenshot to show that it's coming from the HMD, attachment "Capture_screenshot_from_PC.jpeg".

About Oculus Tray Tool : it seems like playing with encoding width and bandwith do lower the issue. It still persists, but not so often.

Thank you for your support, as you can see in the capture, it's making any PCVR Link experience unbearable.

 

____________________________________________________

 

Screenshot from pc : 

 

capture of Quest 2 display, where you can see the horrible white band popping just right at entering Oculus Menu :

 

As tests become more precise, it's more and more obvious that the issue comes from the way Oculus are encoding the data to the headset.

Up and Coming
August 30, 2021

I was at about the same place over 6 months ago with Oculus "support", when I first filed a support ticket. That's before they simply decided to start ignoring my emails. 

Have you encountered this problem before running any games through link? I've had the same thing only after the that stripe appeared in game - only in the bottom part of the screen though. If it appears for you before running any games, then that's interesting. Chances of Oculus taking responsibility for the problem are slim to none though. That would take honesty and mental fortitude that they lack.

Participant
August 31, 2021

AlexiTQ yes it's happening right before any game, just after plugging the Link and just when entering Oculus PC menu.

 

Additional infos, hinting at potential Oculus encoder issue :

I tried with AirLink for 1 hour, as suggested by several sources.

 

For the 20 first minutes everything was perfect, and then suddenly, huge artifacts started to build in my headset :

 

Once again I took a simultaneous screenshot from the PC, to show how it's supposed to render before encoding :

 

 

a few observations :
* for this AirLink scenario, the only way to make artifacts disappear is to look away in a complete direction, to "clear" the messy pixels.
* unlike the wired Link scenario, that "clearing" doesn't last. Visual artifacts always return after 10-15 seconds.
* the more seconds are passing by, the dirtier artifacts are becoming. To a point where after 20-30 seconds without clearing the view becomes simply unreadable.
* I tried the experience for 30 minutes, and couldn't find a way to make artifacts go away.
* I tried dynamic compression setting at max bitrate (200 mb/s), and fixed compression (max bitrate aswell), there was no difference.
* My Wifi is excellent, I'm 60 cm from a professional Wifi 6 router. The wifi infos in the Quest 2 mentions 1200 Mhz speed (the maximum for this headset).

 

Now if this is not a proof of bad encoding (or decoding), well I don't know what is ...

Forwarded to support indeed. If support doesn't aknowledge the issue, I think I'll escalate to John Carmack on Twitter (he's still a consulting CTO and often have commented some Oculus technical choices).

jeremepowers
Participant
August 31, 2021

Oculus support has asked me to return my headset. Has anyone had this solve the issue? I am hesitant to return my well cared for and maintained headset for a refurbished one if this will not solve the issue. 

Participant
August 31, 2021

No, this will not solve the issue and this thread is full of these stories. Forward Oculus support to this thread. They should read it whole and solve it. Not replacing working headsets due to this evident Link SOFTWARE issue, which started to appear somewhen around updates v23-v25. Total amateurs. 😕