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?
Thanks for your explaination, I will volunteer to verify this claim about VRAM temperatures. I will buy new thermal pads and work on cooling, and we'll see if it helps.
On the other hand - Meta support sent me a solution, and while it didn't work, it heleped to reduce this problem, although I have a suspicion that it's possibly a coincidence. They told me to open debug tool, and toggle console visibility to show live terminal with logs. While I see no correlation so far I have been getting white stripe noticeably more rare, and they sometimes happen to clear by themselves, which would support your theory. Also - you might be right about common error appearing when white stripe appears - I get exactly the same error message shortly before white stripe appears.
17/03 15:17:38.820 {!ERROR!} [xrstreaming] Frame 781736 dropped due to encoder backup
I don't think Vram temperature is the issue. I had a 2080 Ti and I switched to a 3080 Ti last week, both GPUs caused the whitebar. The 2080 Ti Vram doesn't have memory temperature sensor but I limited the core to 78°C, the 3080 Ti I have now reaches 88°C Vram temperature which is well within the safe range.
Well that's the point i'm trying to make. It isn't just one issue for everyone. Your card may be just fine as far as heat. But there may be some other issue that is causing it. For instance, lack of sufficient power to the GPU can cause display artifacts as well. Not saying it is a problem you are having at all but it is just another possible cause. Quite a while ago I made a post about insufficient power as a possible cause. I did that because when I changed out my power supply from a 650W and doubled it to a 1300W unit the occurrence of the white stripe decreased significantly. So much so that I though it solved the problem. It didn't solve it but it sure made it even more random. It is totally circumstantial but now I suspect that lack of power to the GPU under certain conditions was a contributing factor.
From the research I've been doing the issue appears to be an interplay between the game app requirements and settings, GPU hardware (heat, power, amount of memory, encoder, etc), GPU driver settings, Oculus ODT settings, and Oculus PC app settings. It is complicated! When all these factors play nicely no issue. It is when one or more of these factors are insufficient or settings too high for the entire system to work as intended that display artifacts can and do occur. Now why it is that we are seeing this particular white stripe artifact is a dang good question but I'm hot on the trail!
The free version is sufficient. Once installed click on the 'sensors' tab and scroll down to see your GPU. The VRAM temps, if you have a temp sensor on your card, is labeled: GPU Memory Junction Temperature. It is the internal junction temperature measured inside the silicone itself.
Great and thanks. So another tack at this is if you are consistently seeing these same messages posted to the log about the same time the white line artifact begins to appear I would suggest starting to reduce your performance settings until you don't get a "dropped due to encoder backup" message any more. Then if the white line isn't showing up I think it makes a pretty good circumstantial case that the issue is occurring becuase the GPU encoder is getting behind what the headset is asking for. Though, yes, there can be a multiple number of reasons why the encoder is getting behind...settings too high, hardware issues, running out of VRAM, etc. etc.
So two weeks ago I posted the following questions that I was going to pursue as result of the review I did of this entire thread to summarize when the issue was occurring and what 'fixes' were reported to work. I have answered most of these to my satisfaction but still working on a few to get even more detail and some other questions have come up.
Tomorrow I will start posting what I've found with respect to each question. This is going to be quite lengthy so I will post one question with its results at a time. Hopefully it will be informative. It has been for me. Then others can chime in if anyone has something to add that will move the ball forward. I'm not responding to anyone who just wants to find fault or bitch about Oculus or anything else. This is a fact finding mission and only the facts count to the best of our ability to ascertain them.
How, exactly, does Oculus Link software work? Specifically what changes to a rendered frame may occur once received from the GPU, if any? What can cause a frame to be corrupted once it is received from the GPU?
What changes were made to Oculus Link between V23 and V24 (25) that could create display artifacts?
Is there an identified issue with RTX 30XX cards that causes display artifacts?
Generally, what are possible causes of display artifacts? Specifically what are possible affects of power supply, heat, and over/under clocking with respect to causing display artifacts?
What properties of simulation apps (Dirt Rally; iRacing; MSFS; etc.) that could cause display artifacts?
Identify detailed description of each of the Oculus Debug Tool settings and how do they affect the display? Especially Encode Resolution Width, and Encode bitrate and their potential to cause display artifacts.
Adding another voice to the crowd. Started getting this issue about a month or 2 ago. I only really play VrChat. Problem happens intermittently and I've been unable to replicate it on command, but happens just about every time. Using 3rd party cable, replacing it did nothing. Tried the debug tool stuff etc with no luck. Since we're 900 pages in I'll skip all the "I've tried" parts.
Quest 2, evga 3080, 9900kf.
3 oddities I've found: one is how it just started effecting me now and I've had my quest 2 for at least a year. No hardware or configuration changes, just one day boom there it was. Unsure if there was a driver or oculus update around when it started.
Two is the bar was always white, both eyes typically starting on the right. When I replaced the cable with the same one I ordered before the bar was purple and only in the right eye the first time it happened. I think it's been purple one other time but has gone back to white.still seems to favor the right. Most likely anecdotal.
Three is when I restart my whole pc and rejoin the world that had the problem it sometimes doesn't come back for the rest of my session. I've had it go away for hours. World intensity doesn't seem to be the culprit, I had it happen within a few minutes in a very basic world where I was alone in a simple model, and I did a dj set in a world with 20 people, lights, lasers and screens for like 2h without it showing up (it eventually did tho).
As far as temps, I'll watch the vram temps next time but my case has pretty crazy airflow. 7 fans total. Gpu rarely goes above 70, custom fan curve. I'll check my logs as well next time it happens as well and report back.
I just did MSFS test flight (with GPU demanding scenery) and for my ASUS GeForce RTX 3080 TUF Gaming 12GB OC LHR I have following temperatures (this time no white stripe but will run hwinfo during every flight to check temps. when white stripe appears):
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.
