These features and enhancements will become available starting the week of April 19th, 2021.
FYI Build 28 breaks the Rift S...persistent random black screens and driver crashes. I manually rolled back to v25 (most recent version I had available to test with) and blocked the Oculus app from auto updating in firewall list and it fixed the issue, no more black screens after testing for 8 hours...as soon as I unblock in Firewall and it auto updates to v28 again (or the PTC update) the black screen/driver crash issue returns. Someone in QC needs to get yelled at.
Edit - I fixed the issue by updating my nvidia drivers and disabling the Link settings in Oculus Tray Tools (OTT). Thanks to TomC for the troubleshooting help.
I finally for around to trying v28, PTC v29 on wired Link (busy and playing Quest titles). I too experience the same horizontal visual artifact in the lower 1/4 of the visual field. Below this line, there's also a different tint to the image. The lower visual field has a very noticeable difference to the rest of the image. I have never experienced this artifact when using previous versions of the Oculus PC app.
I recently purchased some PCVR games to play via Link, so discovering this bug is pretty irritating. I hope it is addressed soon.
I also submitted an Oculus feedback form via the PC app.
Using the Quest 2, RTX 3080.
@ShocksVR v28 (you should not try v29ptc yet imho) all working well with my Q2 with either my official link cable and Air Link. With Air Link there seems to be a few changes that may effect wired Link as well. Try going into ODT and make sure everything is default, esp. encoding and bitrate (both need to be = 0). Also go into you Oculus Desktop app device/q2 Graphics quality and leave the slider on default. With your strong gpu you should be able to select 90Hz refresh (then just accept the default rendering.
If you are using OTT go into the Link panel and disable OTT setting. After saving and restarting you can play around with global SS and ASW, and finetune these later using game profiles.
Also make sure your nvidia drivers and win10 are up to date. Sorry, all I can think of. With so many systems out there it's pretty hard to second guess exactly what is causing your problems.
If you are still having problems I think you are best to contact Oculus Support and attach your log files. This may give them a bit more info than the app feedback form. Good luck mate and cheers.
Thanks Tom for your advice.
I do use OTT and went ahead and disabled the Link settings, along with updating my GPU drivers (they were 1 step, 1 month out of date); I also opted to go back to v28. After doing this, that resolved the horizontal line+tint issue I was having with wired Link. Unfortunately, I'm not sure which thing (OTT vs drivers) fixed the issue for me.
I also did some preliminary tweaking in ODT (encode 300, width 4000) and the issues didn't come back. I will continue to mess around with the settings and report back (mainly with OTT to see if I can reproduce the issue).
Thanks again Tom.
@ShocksVR Glad to hear it seems to be working ok now. I'm finding it still best to keep OTT's Link panel options all disabled and just let the Oculus Desktop app device/Q2/Graphics settings at 90Hz and the slider at automatic. Then just use OTT SS and ASW globally. With my rtx3090 I'm using Global SS = 1.5 (your 3080 probably can use 1.4-1.5) and ASW = off (on is only useful for weaker pc's imho). I also leave auto gpu scaling = off (mainly because it does not seem to do anything anyway, lol!). Then I just adjust SS and ASW in OTT game profiles to finetune apps that can take a little more, or need a little less SS. I leave asw = off except for complex flight sims, where I use asw = 45fps, fixed (fixed aws=off).
In general, I'm finding that playing around with OTT SS gives me a better bang for my buck (visually and performance wise) than playing around with either OTT Link settings, or Oculus debug tool (ODT) encoding/bitrates. Leaving them all default at 0 seems to be let them be where they want to be.
Like everything, if it's working ok it may be best to quit mucking around with a lot of these. If it ain't broke, don't fix it, lol! Thanks for letting me know how you made out mate. Cheers.
The Link problem could be on your end.
Go back and read my previous replies in this thread. I had the visual line artifact in the lower 1/4 of my visual field, I was able to fix it by resetting my Link settings.
And what's the Encode Resolution bug ?