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

New Participant
October 31, 2021

Upgraded my 1070 to the 3060, no reformat, nothing, and this started to happen. Tried formatting my computer, issue still persists. I'm going to try the downgrade workaround. but, Oculus, fix this issue, this appears to be a old problem!

Participant
October 31, 2021

I upgraded from a 1080 to a 3060, then started running into this issue. Makes me think there's something there--even if people with AMD GPUs are reporting similar issues.

New Participant
November 1, 2021

I changed from 1080 to 3080 and same thing happened. Anyone found a solution yet? 

Participant
November 1, 2021

Hi all, for those coming to this post looking for a solution to the issue... oculus have yet to find a working solution to this ongoing issue. Please follow the guide I have made below to revert your oculus PC software back to version 24 which will fix the issue and allow you to use your Q2 on pc again. Big thanks and credit to Serhyo who initally found this workaround. All I did was find a way to fix the sound/mic issue and refine the guide/method to ensure a functioning downgrade everytime. 🙂

 

So after 24+ hours of solid tweaking and testing and all round pulling my hair out... i have found a way to downgrade the oculus software to V24 like in serhyo's post but also fix the audio and microphone issues whilst allowing 120HZ mode if required (though I recomend sticking to 90HZ as its far more stable). You do loose the abilty to run via Airlink (currently bugged on build v33 and wont run more than 72HZ anyways) but frankly Virtual desktop is tons better anyway and has alot more to offer including abilty to watch 3D films, etc!!!

 

Please follow steps as per below.

 

1)  Turn on Public Test Channel in beta tab in oculus PC app settings, once the update have finished reboot your PC.

2)  Once reboot is complete turn off the PTC and let oculus update back to V33 but this time DO NOT REBOOT YOUR PC,

3) Download https://drive.google.com/file/d/1H_Sgam3hVAtDFPajTu7ZcpUqSrEh681D/view?usp=sharing

4) Stop OVRService - (ctrl+alt+delete -> Task manager -> find OVRService -> right click Stop

5) Go to C:\Program Files\Oculus\Support, and rename folder Support to Support-backup.

6) Export the downloaded Support folder from step 3 to C:\Program Files\Oculus\

7) Create a text file using notepad named ''tmp'' and move it into C:\Program Files\Oculus\, then enable file extensions under the view tab in windows explorer and delete .txt extension from the file. (staging file is not needed, aslong as you have the "tmp" files in this directory it will stop automatic updates.)

7.5) Start OVRService again.

8)Open the oculus app, you should get a red banner appear at the top of the window telling you to "update the drivers" for oculus to run your hardware properly. Go ahead and click the button and let oculus app run its driver update. Once this is done go ahead and reboot your PC again. *It's vital you restart your PC before the next steps or this may not work!!!*

9)  Open device manager and navigate to sound, video and game controllers, click the arrow to open the list of devices.

10) Right click on "Oculus Virtual Audio Device" and then click update driver. Click search automatically for driver and let the update process complete. Once this is finished, windows should prompt you to reboot to finish installing the new driver. Let it reboot once again.

11) Enjoy playing VR games again with fully functioning audio and a working mic!!!

Oculus home will initially be broken/will not load in after this workaround is applied. If you care about home/want to use it again then navigate into the support folder and delete the "Oclulus-worlds" folder and "oclulus-words.zip" file. Then you just need to copy your "Oclulus-worlds" folder from your support-backup folder and paste it back into the support folder. You will need to make sure oclulus service is stopped before you start deleting and moving folders, but make sure you do this after following all the steps above first! Once you are finished you can restart the Oculus service and when you use link again, Oculus home will load up as normal :).

 

This should work for all affected users providing you follow the steps exactly as posted, I have been using this workaround for weeks with 0 problems and have been enjoying all my PC VR games again since bfore this issue occured. This workaround has been tested and works for both a RTX 20 & RTX 30 series graphics card owners. It should also work for any ATI users suffering this issue but do not own an ATI graphics card so I cannot test this to confirm.

 

I really hope this helps and please post to this forum your results and let us know if this worked for you. The more people who let me know this has worked for them, the more evidence I have to give to Oculus support to finaly make them see the issue lies with there software and look into what changed between V24 and V25 to brake this. But for now this should get most of us running again untill Oculus finally pull thier finger out and get us a permenant solution!

Participant
November 3, 2021

I am strongly considering using the v24 fix but before I do I just want to know what are all of the features that I would lose by doing so.

New Participant
November 3, 2021

The best feature you will lose would be the horizontal transparent stripe across your dirsplay while gaming 😄

 

I believe i had readed that oculus air link only runs in 72 hz mode but am not sure.

 

The downgrade is a big upgrade for your oculus link if you have that **bleep**y issue every 10 minutes.

 

 

Inspiring
November 2, 2021

I got version 35. Not solved. Yes, I knew. 🙄

New Participant
November 2, 2021

Hey dudes,

 

At first big thanks to fyte for this guide to downgrade to v24.

 

I have the same issue since i bought my quest 2 for a week only when im playing dirt 2 . Have a rtx3080 and i9 

 

I have tryed to follow the steps 1-9 

But my english isnt so good and i have some questions to step 7 and 8.

 

I have downloaded the notepadapp and created a new textfile named it "tmp" and moved it to the oculus folder.

Then i had enabled file extensions in the win explorer and was confused.

Wich .txt extansion is to delete there havnt seen whats to do. At the end i deleted all .txt files i could find in the oculus folder. Was that right?

 

Then the next confuse 😄

Can i start ovrservise tab before opening the oculus app?

I had after i deleted the .txt files opened the oculus app and clicked the red banner for updating drivers.

But the downloaded and installed alll driver to newest version. At the end i was at v33 again and in step 9 after restard hadnt find any update in the device manager.

 

I have deinstalled the oculus app now and installed new. Want to try your guide again and it would be nice if you could clear up my confusing 😄 ❤️

Participant
November 2, 2021

If you want to private message me your email address i can send you the tmp file ready to go if that helps? i'm not sure how to make my instructions any clearer. 😞

 

You need to restart the service before you open the oculus app. The lack of tmp file is the reason the oculus app updated back to V33.

 

hope this helps

November 2, 2021

remove tmp.txt only the .txt on the new file 

November 2, 2021

And not more filés 

New Participant
November 2, 2021

Ok update, i could now follow all steps in your guide and everthing works finde :)) 

 

Played dirt rally2.0 over 1  hour without that **** stripe was coming.

 

Im so happy. Thank you very much vor helping and forgive my dumpness 😄 

Was easy at the and to do that.

 

I kiss your eyes 😄 ❤️

Participant
November 3, 2021

Great investigation fyte!

https://forums.oculusvr.com/t5/Oculus-Quest-2-and-Quest/White-horizontal-stripe-across-screen-while-using-link/m-p/891732/highlight/true#M43921
This confirms our initial thoughts that this issue started around update v25 and that is definitely software issue (not overheating, not HW failure). This temporary solution should point Oculus devs into the right direction to solve this major issue soon. From my developer's point of view, it should be no problem to look at git and find suspicious code changes after v24. So, MetaStoreHelp, it's your turn and also the last chance before I buy another headset.

Participant
November 4, 2021

Problem is I’ve tried to tell support the same thing, I’ve begged for support to show my findings to the actual developers so they know where to look. However I’m being largely ignored. I’ve asked for contact information for someone higher up the chain 4 Separate times and this always gets ignored in my responses.

 

it baffles me how support is taking so long just to goto a programmer and say “hey! Some users having this problem! They have done all the work for you and have pinpointed where the issue stems, can you take a look and figure out which code is causing the issue?” This whole thing will probably take couple of hours to fix but the issue is not being brought to the right people.

Participant
November 3, 2021

I don't know what to say.

I'm here with this issue since the begining of the year.... yes... I was complaining for this issue in page 1 and 2 of this topic, that's crazy.

The first time I had this issue was directly after the update from V23 to V24 beta.

The issue was solved for 15 days because I unchecked the "beta" options which had the effect to replace V24 beta by V23.

The mandatory update that followed changed my system from V23 to V25, and I had the problem again.

I've never tested the official V24, only V24 Beta, on in my case, V24 Beta was already causing the problem.

This makes me hesitate to go back to 24 by tweaking my PC, It's not a clean way to proceed in my opinion, and I would prefer to wait for the problem to be resolved by Oculus, in the meantime I no longer play my games, nor with my Quest 2...

Participant
November 4, 2021

Look at it this way sp0uny…. What have you got to loose by trying?? Any changes done in my guide can be completely and easily reverted with a simple repair on the oculus software. A few steps and you could be actually playing VR again! If you wait for oculus to fix the issue officially you may never play VR again…. (I only wish that was a joke).

 

the more people who try the workaround and confirm it’s working and then shout out about it the quicker we can get oculus to pull there finger out and actually fix it. 

New Participant
November 5, 2021

Yeah can confirm that Fyte's workaround is really working. No more horizontal stripe after following your instructions. Been playing Assetto Corsa's, Dirt Rally 2.0 and not a single stripe has appeared anymore. Before fix I used to have them every time when playing with USB 3.1 cable.

 

Thank You for the fix Fyte and shame on Oculus support for ignoring this. This is after all most commented post on Oculus Quest 2 and Quest sub forum and one of the most viewed ones also so the problem must be very widespread and 100% software related.

Participant
November 6, 2021

That’s great to hear!! Don’t forget to tag oculus support and if you can be bothered raise a support ticket and link then to this post and tell them to pull their finger out!!

New Participant
November 6, 2021

I've tried fyte guide and did not work for me at all, still getting those horizontal lines...

Participant
November 7, 2021

Are you sure you followed it step by step? The workaround seems to be working for everyone else who have tried thus far! So maybe you missed a step or something? Please PM me if you like and maybe I can help you directly 🙂 

New Participant
November 7, 2021

I too have the same issue. Problem persists after closing the app Dirt Rally 2.0.  First saw this issue in American Truck Simulator. Fyte, could you please share your fix? Have you tried oculus debug tool? 

 

Thank you for your time.

ChicagoChad