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?

[rfxcasey]

I have this problem and I do not have any Public Test Channel enabled.

[Sp0uny]

Today it no longer matters.
When I wrote that, it was a year ago, at that time, activating or deactivating this option had the effect of switching between 2 versions of oculus link, and more particularly between the last version which did not have problem, and the first version with which this problem appeared.
Given that since 1 year there have been between 10 and 15 new versions of Oculus link, and that all have the problem, activating or not this option in order to switch between the last 2 versions no longer have any positive effect.
Now the only known solution is to revert to V24 using fyte's method.

[SerHyo]

Im sorry, I don't want to sound like an a-hole but I see all the time that you give credit to fyte for finding the solution. But it was me who first found the solution by reverting it to v24 (as fyte wrote in his post). Fyte found the solution to fix the sound, because there was crackling sound after reverting.

So again, i don't want to sound like a douche, i would just like to receive some credit for finding a workaround and sharing with everyone. Especially because nobody from oculus/meta doesn't move a finger to fix the problem.

Thank you.

[rfxcasey]

Please provide the name of the specific service.

[Sp0uny]

You are right, I'm sorry for that.

Honestly I couldn't remember between you and him, who had found the fix and who had found the way to fix the sound issue, and now this discussion is so long that it becomes long and tedious to find the info throughout all these pages.
Sorry again, your intervention is normal, the credit is yours since you found the warkaround first.

If my memory serves me right, fyte deserves credit for having rewritten the whole procedure in a clear and detailed way, so thanks a lot to both of you.

[jakubito]

Thank you for finding the workaround

[fyte]

Reposting for all the new guys to find this to help fix the issues. @SerHyo Put your bit in bold to help peeps recognise your contribution here 🙂

Hi all, for those coming to this post looking for a solution to the issue... oculus has 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 initially 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 every time. 🙂

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 recommend sticking to 90HZ as it's far more stable). You do lose the ability to run via Airlink (currently bugged on build v33 and won't run more than 72HZ anyways) but frankly, Virtual desktop is tons better anyway and has a lot more to offer including ability to watch 3D films, etc!!!

Please follow the steps below:

1)  Turn on Public Test Channel in beta tab in oculus PC app settings, once the update has 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 and no white/pink stripes!!!!!!

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 (now almost a year ><) with 0 problems and have been enjoying all my PC VR games again since before this issue occurred. This workaround has been tested and works for both 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 their 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! (one can dream XD)

[SerHyo]

@Sp0uny, @fyte 
Thnx guys, again don't take this the bad way, but i just wanted some credit for time spent experimenting and finding workaround 🙂
Thank you too for spending your time on spreading the word, searching for solutions, and helping others find it, and also writing more detailed guide, since English is not my main language XD
PS: Anyone tried to contact some popular YouTubers to address this issue? Maybe they can help draw attention to this problem.
Thank you all and have a nice day!

[RustyKerman]

I tried doing this, but by the time I got to stage 7, it would not let me place the tmp text file in because there was a folder named TMP. 

[RustyKerman]

One question, wouldn't just repairing and getting a fresh install of oculus fix the issue it this is a software bug?