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?
So Public Test Channel v54 dropped yesterday, giving users the ability to turn Sliced Encoding on or off in the OculusDebugTool!
Upon being asked if my Registry Editor workaround entry should be deleted, I told this to a Redditor on r/QuestPro.
I’d wait until v54 is released to the public fully, but I suspect how it’ll work is:
• The Registry Edit will always launch Quest Link with 0/1 encoding slices if it isn’t deleted, even after v54 releases • If the numSlices Registry Edit is deleted, you will be able to switch between 5 slices and 0/1 slices at will using ODT. It’s possible this will negate the need for the registry edit, but also is possible it’ll need to be reactivated through OculusDebugTool every time Quest Link is launched (like with changing Asynchronous Spacewarp). If that’s the case, and you know you will always reproduce the white bar issue, you may want to consider just leaving the registry entry in place.
Thanks for keeping on top of this for us all. I've been very busy and haven't had a chance to even check this thread. I can't recall if I mentioned it or not but after several months I didn't see the stripe and then about a month or so ago I ran a dirt race and sure enough the white stripe began to present itself about 1/3rd of the way through the race. I hadn't changed any settings or had any driver updates at all. I think the difference is that with a dirt scenario there is so much more rendering of textures and therefore the ol Nvidia encoder just goes "blahhhhhhh!!!!".
I hadn't made the registry numSlices patch yet since I wasn't seeing the problem. So I made the edit to set it at '4' and the problem hasn't come back yet. I don't see any degradation in performance, at least none perceptible to me, so I'm just leaving it '4' and getting on with my life!
I recall you made the suggestion to add an option in ODT to allow changes to numSlices around the time when you first posted the solution. So is someone in Meta actually paying attention to what we've been discussing here for the past 2+ years? I don't know but it warms my heart to think so!!!
I just recently upgraded my GPU from 1080ti to 3080ti, and I can tell you that it's probably only 20** and 30** series issues. Everything used to work fine on 1080ti. The setting in oculus PC app (hz & resolution) and in the game (dirt rally 2) remained the same. I've even tried to do some undervolting on 3080ti to keep it on low temperatures/wattage, but it doesn't help. At first I though that I bought a broken videocard, now I can feel myself better 🙂
P.S. only numSlice "1" worked for me, but I can feel that latency increased. "2","3","4" and default value resulting in white/pink bar
Hey there, @TisCrowley! We couldn't help but notice that you are reaching out because you are experiencing some display issues with your headset. We certainly understand how disappointing something like that can be and how it can really effect your overall experience, so we'd like to help you get this issue sorted out as quickly as possible! So that we may gather some more information from you, we would like to invite you to send us a private message. Please select our name to get to our profile page, or click here. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
...and 40** series. I have recently replaced both my Quest 2 with a Quest Pro, and my 3080ti with a 4090. I can still replicate it, even with slices set to 1, so I know it is not a headset, or a broken card. Sometimes it runs fine, other times, I get the problem, I still can't nail down what it is that triggers it.
I am having this same issue with No Man's Sky. It will load up fine and then 15 - 30 mins into the session it will show up.. Most if the time i have noticed it seems to start just after i go to the marketplace terminal on space stations, but its not limited to that. Also i have noticed that it may not be specifically game related as when i exit the game back to the steamVR home its still there and then even logging out, back to the the quest-link home, it is still there. It only finally goes after i get back to the quest standalone home that it disappears. I have tried all of the suggested fixes but still nothing. Please help.
Specs: NVidia RTX 3060ti, CPU i7-10700KF, 32Gb ram
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.
