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?

[Brage1564]

Did you try to apply it through CMD? like just copy paste the code and enter?

I think you can also go to the Registry Editor location (HKEY_CURRENT_USER\SOFTWARE\Oculus\RemoteHeadset) and having it look like this image I have attached

[cam1061]

Thanks have gone the manual route. so will see how it goes.

[Frekkie_Monster]

Oh my god, I copy/pasted the text in command prompt and the white line seems to be fixed!!!!

Thank you so much!!

[Forsakenzombi]

There has to be a latency added when doing this right? Surely this change would increase the encoding time and therefore add latency to it…

[lagarto102]

Thank you very much. For the first time in years, the white stripe has disappeared using FS2020. I have the feeling that performance drops a bit with only one slice, but still, it is usable through the cable, which hasn't been possible since V29.

Thanks!

[Pokebert]

You’ll see on average, around ~5ms more latency. 

[Poziom_96]

Not necessarily - I just tested this fix, but using different values in registry, and it works fine, as long as you don't exceed "4", which reduces latency significantly. I haven't had white stripe with 1, 2, 3 and 4 set as this registry key during around 3hrs of continuous playing, where I had this issue after max 10 minutes before, so I can say that is really a fix.

[benji94]

What are your thoughts on what triggers the encoder error with the 5th frame slice?  I ask because my experience with it has always been very random as many others here have also reported.  Based on my review of everyone who posted on this list it was apparent that some resolved it (I guess "avoided it" is now a better description) with setting changes that reduced GPU workload as well as other workarounds.  It was also primarily with simulation apps that ask for higher resolution and need powerful GPU rendering.  Is it reasonable to consider that indirect factors impacted the GPU encoder's ability to keep up with demand from the headset to encode all 5 slices of each frame.  By lowering the number of slices it gives the encoder the slack it needs to keep up with headset framerate demand, though with a trade off of a little latency.

Just trying to understand this as clearly as I can.  I'm not going to make the registry change right now because it appears my experience with it has been eliminated by increasing cooling of the VRAM on my rtx 3090.  It is running about 5 degrees cooler than before and I've been in the headset for up to 3 hours at a time for weeks now and no sign of the white stripe whatsoever.  If it does happen again though I will jump on this.

You've done a great service to this community.  Thanks.

[go_super_sheep]

As promised...

Equipment lay dormant. Potential sat wasted.
Brief moments of leisure; our fun turned frustration.
Pandemic and war, when escape was most needed.
The forum, for years, claimed falsely 'solution'.

Then, out of nowhere, a champion emerged.
Self starting, deep diving, verbose in their sharing.
Not resting content with 'fixes' unsure,

Over the hill appeared: Benji94

Did not bid 'reach out through Oculus, (and then Meta) Support'.
They dug and they theorised, where all had found naught.

Dug deeper and deeper, the techmines, their home.
No copy and pasta was breakfast for them.

No profit to find; their gift freely given.
(as well, I suspect, we could not afford them.)

Countless hours could be seen in their thought and their toil.
Their background unknown, but clearly expert.

Their graft and their writings summoned Pokebert.

The fellowship of the Ring Rift Quest2 was formed.

We held with baited breath.

And then

Encoding insight...

One cmd line...

Clarity.

Holy sh*t.

Thank you.

[Pokebert]

Sweet! Honestly, this to me indicates that slices should be brought down to 4 from the default 5 and this would instantly fix the issue for so many users…

though I still think Meta needs to implement the ability to change how many encoding slices are used. 😉