For Blubear - Quest3 stripe Issue

Friar · February 9

I did a bit of searching this morning over breakfast ref your issue and found this after seeing lots of people having the same issue in v3 or earlier.

The guy from Meta Forum (my link in this topic) has found solution for this two weeks ago after almost 3 years of investigation.

Open Command Prompt (cmd.exe) and paste this:

reg add “HKEY_CURRENT_USER\SOFTWARE\Oculus\RemoteHeadset” /v “numSlices” /t REG_DWORD /d “1” /f

Of course you have to use straight quotation marks (this forum changes them to typographer’s quotes).

It’s necessary to restart Oculus service (or better restart your OS if you don’t know how to do it).

You can experiment with different numbers (“4”, “3”, “2”, “1”), however only “1” (one slice) works for me with cabled connection.

Quest renders image using 5 slices and when 1 of this slice (usually 5th one) is not encoded correctly you get this white stripe. The command above changes image rendering to 1 slice. This adds some latency but I haven’t noticed any performance drop so far.

If you want to remove this fix use this command:

reg delete “HKEY_CURRENT_USER\SOFTWARE\Oculus\RemoteHeadset” /v “numSlices”

I got the above from here in case you want to have a read through

https://forums.flightsimulator.com/t/quest-2-white-artifact/579744/10

BluBear · February 10

Thanks mate! Yes I think I stumbled on a similar post somewhere else. I'll give it a try. Sounds like it's a problem that only arises when using link cables with Quest 2 and 3 and not over airlink. All fun and games!