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
June 28, 2021

Still having this issue with Wired Link. Also having a related issue where the image "desynchronizes". When I move my head the images displayed are out of order or something. It's sort of like a ghosting but not the typical performance related one. May be associated with a game freezing due to a high CPU load. This happens on both Wired and Airlink and does not go away on it's own. It will persist even after the game is shut down and only the Oculus Dash is visible.

 

Example: DCS World

1) Connect to a server

2) Select Airplane

3) Airplane loads

4) Game freezes while finishing loading the airplane (Or something else CPU intensive happens)

5) desync happens with link

 

The only workaround I have is to double tap the Quest and go into passthrough for a second. But this is only a temporary fix and a minute later it happens again.

I've tried messing with all the Oculus Debug settings, Nvidia Control Panel Settings, Overclocking, Underclocking. It does not show up in Oculus Mirror either, only inside the headset.

 

My specs:

I9-11900K

3080 FE

64GB RAM @ 3600mhz

1TB PCIe 4.0 NVMe

 

I should also mention that this doesn't happen with the *other* virtual desktop software. (But it forces using steamVR which is far worse in DCS than the Oculus API one)

 

New Participant
June 29, 2021

hey guys

 

might have gotten rid of the **bleep** thing. i don't wanna say "fixed the issue" cause we shouldn't have to compromise quality to get this working properly. 

 

Here's what i did

 

1. Set MSI afterburner settings back to default

2. Set encode width to 0 on the debug tool

3. Set framerate at 72hz and have render resolution at 4128x2096

 

Specs: 

i5-8500

1660 super

16gb ram

i'm using a 3rd party usb c to usb 3.0 cable

 

got to use link for about an hour without it coming back. i was on discord and ran a couple of games on steam vr.

 

i'll post an update in a couple of days. 

New Participant
July 2, 2021

Having the same issue, so far it seems only Dirt Rally 2.0 (Steam version running in Oculus VR mode) is doing it on my end. It *always* starts for me when a "flat" screen is being rendered like the menus or car repair screens. It will then continue into the car in VR. Starts dull but gets pretty bright quickly. So far, I have not seen it start while driving, but I have seen it get brighter. As for my other PCVR games, no issues in countless hours in American Truck Simulator and European Truck Simulator 2, or in the few hours I've played Star Wars Squadrons, and I only just bought MSFS, so I haven't had a chance to try that yet.

 

Specs:

i9-10850k

RTX 3070 w/ 8GB

16GB ram

Tried several USB 3.0 cables (A to C and C to C) with no difference.

Inspiring
July 2, 2021

Looks like this is a common problem now.

Participant
July 8, 2021

Has anyone found a solution to this? This is driving me literally NUTS right now - I am using Oculus Quest 2 for Simracing and Simracing only. Happens in all games and any games - no matter what - the only game I have never had that happen was HL Alyx - but all other games it happens.

 

What is absolutelly the worst thing is, that I will go into single player, or TrackDay only and I will drive for 4 hours straight without it happening a single once. I jump into serious 30minutes race where are real people, and it starts happening after 5 minutes. There is NOTHING I can do during the race to stop it from happening and it will be getting worse and worse. I have seen 2nd horizontal line appearing, over the time they get brighter and brighter, until I cant see anything after 30 minutes race.

 

This is insane to the point that I want a refund for the quest. It is so far the worst thing I ever decided to spend money on. Should have paid more for other product and wouldnt have this problems.

 

I have seen that some lads didnt have issues with this pre-25 patch. Is there a way to roll back the upgrades? For as long as I can do 80hz via link from PC, I do not care about any other features

July 8, 2021

Got this issue on my laptop with rtx3070 in it, started to show up after the latest update. Also, it keeps asking me to recreate the guardian on every single boot and I keep getting messages about com.facebook.spatial... crashing a few times. The white bar only shows up when I play on my laptop with 3070 in it - it works fine on my PC with 1080ti. Just tried reinstalling the graphic drivers with the help of DDU and also the Oculus software, and after an hour of running vrchat, it seems to be okay... For now.

Participant
July 9, 2021

Keep us updated on the drivers please - I have RTX 2070 with always up to date drivers. 

 

I have however bit the bullet and while I was afraid of wifi connection to the headset, I gotta admit, that sitting in the same room where the router is, right on the 5ghz network, it does work really well via Virtual Desktop. Had to cash in another 20 quid, but if it will work, I see no problem with that really

JamesButlin
Participant
July 9, 2021

So basically.. What seems to have happened for us all is that RTX cards have started having the issue after an Oculus Home update at some point (either that or a Quest software one..?). I did update to the public test drivers so I could try out 120hz mode, that was working fine on my 3070 but since I upgraded to a 3080ti (or had an Oculus Home update at the same time) I've started having the issue.

 

For those of you that have also got the issue - did you start having it after an update or a change in hardware? Out of curiosity?

Up and Coming
July 9, 2021

Nope, I started having the issue after V26 update. Same hardware and same drivers.

JamesButlin
Participant
July 9, 2021

Right.. My hardware change was probably just a coincidence then. I'm going to try a fresh uninstall and re-install of Oculus Home later today after having moved off the public test channel.. I don't think it'll change anything but can't hurt to try πŸ€ž. It's definitely some software/driver bug so that helps to rule out a few things.

Participant
July 9, 2021

Is there a way of reverting back to V25 of Oculus? I really could not care less about any other 'features' for as long as I can stream at least 80hz

New Participant
July 11, 2021

I had this issue a month and a half ago on DCS. I used tray tool and adjusted settings and it went away. Now as of last night after hundreds of hours of working fine it started again…. No hardware changes, no setting changes.. no reason for it. Seriously wtf oculus help us out