Hi,
does anyone have this kind of artifact using Quest 2?
It appears slowly during flights in VR (you can see it in VR only). Latest MSFS version (not a Beta one).
(THIS IS NOT A SCREENSHOT, I created this image using photo editing software to show how it looks like)
2 Likes
Hi there. Thanks for posting.
I am interested in this as well. I experience this occasionally and, although unable to explain what it is or how/why it happens, what works for me is a simple exit from the VR session (MSFS remains open) and re-entry into the session and the white band typically goes away. If that fails to work I restart the headset (again MSFS remains open) and reconnect to the oculus app and then re-enter the VR session in MSFS.
Sorry I could not offer the technology behind what is happening but this forum is filled with impressively intelligent and experienced members, and looking forward to their responses.
Again thanks posting.
1 Like
@Jaco15020, do you use OpenXR Toolkit? I use it but I have enabled “Turbo mode” only. Do you use 531.18 NVIDIA driver (the newest one)? I’m asking 'cause maybe it’s somehow related to these ones.
It’s really annoying especially when you’re flying online and you’re on the approach and have to restart your headset 
you are probably using the Oculus Link (cable) right?
I could not pinpoint why/when it does happen but the only remedy is to close the Oculus app on your desktop (to disconnect the Link) and re-enter from Quest home. You do not need to pull the cable and physically disconnect nor quit MSFS. Just re-establish the software link.
For me, it seems that since joining the Public Test Channel under Beta in the app has resulted in no more occurrences of this.
Anyway, good luck.
1 Like
I use a Quest 2 with RTX3070.
The issue you’re describing happens to me under the following circumstances:
- the Oculus resolution for the headset is set too high (e.g., maximum which is x 2736 I think)
- the encode bit rate is set too high (e.g., 400+)
- I’m flying in a demanding area (or aircraft) and the VRAM in my GPU is being overloaded (my card only has 8GB)
- or any combination of the above.
I usually fly with a headset resolution that ends in x 2448 at 80Hz. My encode bitrate is usually default (0) or maximum 350. When I do this, the problem goes away.
I can use most 3rd party add ons, however, the recent Vancouver city landscape that was released still tanks my PC and overloads the VRAM and I can’t fly there unless I disable that add-on. Can’t wait to use it when I get a better GPU.
Cheers,
1 Like
This works fine.
I’m on PTC but since I have installed the app, so this doesn’t solve the isse for me.
I have RTX3080 w. 12GB (DX11 in MSFS) and have never had any problems with VRAM being overloaded, but will check this using some VRAM monitoring tools. Encode bit rate set to 250, refresh rate 72Hz w. headset resolution 5408 x 2736.
For me this occasionally happens when the system is taxed AND when I’ve overclocked either or both my CPU and/or GPU, even though they are otherwise very stable overclocks. In your case it could also be a “factory overclock” if applicable. It might be worth experimenting with dialing down the clock rates a bit.
I have experienced this occasionally but much fainter than depicted here unless that is emphasised. Coming out of VR and back into VR does not usually cure it for me, I have to restart the sim. I believe it was on Oculus wired Link.
I checked this issue once again and:
- I have 10GB / 12 GB VRAM usage + 100% GPU activity (RTX 3080 12GB), so my GPU has some free resources (2GB)
- CPU with factory settings in BIOS (no OC)
- reconnecting VR (with reopening Oculus Home app) but the problem is still back (had it 5 times during 1 flight, even at cruise altitude)
- Oculus Link (cable)
- have never had this isse with P3D in VR (so it looks like it’s somehow platform related)
Hope someone will find a solution for it (users or maybe Asobo).
This happens on my Q2 occasionally as well, but not as often since I upgraded my CPU…. May having something to do with it.
I have Intel Core i9-11900K, so not that bad.
Just found very interesting topic:
Hmm, you have 2GB available VRAM but you’re running the GPU at 100%. I reiterate my earlier post: the only time I experienced this in the past and occasionally now is when my system is set up to work on the edge of its capabilities, often when I have overclocked it a bit too much.
Just a suggestion: install MSI Afterburner if you don’t already have and run the GPU and/or its VRAM at a lower clock rate. Just go down a lot and see if it still happens. If not, bring the rates back up slowly until the white bar appears again and then back down a bit. Experiment. It might not work, but it’s worth a try, I think… 
I have the same issue. Using Virtual Desktop is a way to avoid this problem, and it works way better than AirLink. This issue is specific to the Oculus software.
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”
6 Likes
Thank you so much for sharing! 
I was aware of the other Oculus thread, however, given the length and timeframes involved I’d practically given up hope they would find a solution and was no longer monitoring it.
So far, this solution is also working for me when using a cabled connection. I also tried 4 slice (instead of 5) and so far it seems ok too.
1 Like
No, I disagree, Quest 2 is NOT compatible to use with Microsoft Flight Simulator.