11-11-202006:30 PM - last edited on 07-19-202401:48 PM by TheLegend27
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?
Did you try airlink? It doesn't work on my Quest Pro and Quest 2. I'm getting a thicker strip + some terrible artifacts even after setting it back to 5
That’s odd. If you want to reverse this though, it’s really easy. Just open Registry Editor, locate RemoteHeadset under the same filepath as the command line fix, and right-click numSlices and simply delete it.
It's funny. Airlink works better for me but I think it's mostly on apps that were bought on the Rift store. Anyways I deleted it from the registry and it works fine. I'll fiddle around with it when I have more time. Thanks for the reply.
Keep in mind that Pokebert's fix ONLY applies to cabled Link and not AirLink. As he noted Link uses the h.264 encoder while AirLink uses the NEVC encoder. I haven't a clue what the Q Pro uses but probably Pokebert knows.
Also, there are lots of reasons for display artifacts to occur so it may be that you have one or more of the following issues:
It was definitely the string that Caused that airlink problem because it happened right after and It's fine after I deleted it from the registry. It was also doing it on my Quest 2. It's alright, I'll fiddle around with it later and probably find a way to make it work. Btw I think that Pokebert's deserves an award for finding a fix after all those years. I always knew that it was someone from from the community that would fix it as the support from Oculus is horrible. I'm having issues creating a second profile and they have no clue how to fix it
To clarify on this, the Quest Pro uses HEVC over Air Link just like the Quest 2 does. I checked in the Oculus Debug Tool - Performance Overlay. Link Cable uses H.264.
The main difference in how Quest Pro might operate when it comes to Air Link in the future is when WiFi 6E compatibility rolls out to it. Meta may have the ability to allow higher bitrates when connected to a 6E router using QPro.
Also, the reason I found the fix is by observing that Air Link only used one slice whereas Link uses 5 slices. I haven’t tested with 2-4 slices, but it’s totally possible they also circumvent the issue! You just might see those transparent encoding artifacts lines running horizontally across the screen. So, you can choose ultra crisp clarity with 5-10ms of added latency or take a very slightly less crisp image (especially in certain dark environments) and take the latency improvements.
AFAIK if numSlices is set to 1, it should keep that with Air Link too. I’ll test more over the weekend…
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
