cancel
Showing results for 
Search instead for 
Did you mean: 

v23 PTC PC Software Release Notes

ShowbizDonkey
Retired Support
Quick note on release numbering - v22 was an internal only build, so we're jumping to v23!

Oculus Rift S

  • We resolved an issue in Oculus Dash where pinned windows would show graphic distortion across the entire pane and not be visible to the user.

Oculus Link

  • Increased encode resolution which improves visual quality while running Link.
74 REPLIES 74

tanubon
Heroic Explorer
v23 is test version. You need to enable public test channel in setting -> beta.

Anonymous
Not applicable
tanubon said:
v23 is test version. You need to enable public test channel in setting -> beta.


He's already done that, he said so in his post. He was asking about a V23 for Quest (or lack of) and how others are using link with the current PC V23.

CactusCowboy
Adventurer
Is there an ETA for 90hz link and full resolution patch? It's been a month since the hardware is out. A wee bit embarrassing.

artscout
Protege
yeah, also why do you need to compress/decompress video with USB 3.2? Couldn't you just check Link speed and if it's enough - just send uncompressed video? 2.5GBps should be enough for that, no?
i7-8700, RTX 3080, 32Gb RAM, 2x1 TB NVME, Quest 2.

artscout
Protege
BTW the reason of why I'm ranting about the Link is that they discontinued Rift making Q2 default Oculus HMD from now on. And for that reason Q2 should be better than Rift S in PCVR. Right now in Beta it is better in some aspects, but encoding width (also I think that encoding itself too) makes picture somewhat blurry, especially letters in cockpit in DCS - with PD 1.5 and high enough resolution they should be clear, but it's not the case ATM even with 500 Mbps rate. Also it would be nice if FB/Oculus post progress updates.
i7-8700, RTX 3080, 32Gb RAM, 2x1 TB NVME, Quest 2.

Globespy
Expert Protege

artscout said:

BTW the reason of why I'm ranting about the Link is that they discontinued Rift making Q2 default Oculus HMD from now on. And for that reason Q2 should be better than Rift S in PCVR. Right now in Beta it is better in some aspects, but encoding width (also I think that encoding itself too) makes picture somewhat blurry, especially letters in cockpit in DCS - with PD 1.5 and high enough resolution they should be clear, but it's not the case ATM even with 500 Mbps rate. Also it would be nice if FB/Oculus post progress updates.


Oculus have stated they intend to have a space at the PVCR 'table', but for now they wanted to focus on the Quest/Standalone since that's the fastest growing part of their business.
They did not say that this was going to be the Q2, what you seem to have assumed.
Maybe in the future, but clearly right now it's not as good as a dedicated PCVR HMD or they would have controlled the market with the Q2. That's not happening, and I think you would be foolish to assume that LINK is going to be all that in this generation of the Quest.
The Q2 is first and foremost a standalone HMD with LINK being a nice add-on but not in the same league as dedicated.

artscout
Protege
Well ok, maybe they'll do dedicated PCVR in future, that would be great. But ATM they going to discontinue Rift S and no replacement announced and we'll have to do with Q2 anyway (cause there's no G2 selling in Russia ATM and none on Amazon) and as far as I see Q2 is second best for image quality ATM after G2. Also  I see that VD (Virtual Desktop) picture is much, much better with 90Hz enabled via ADB commands and 5Ghz WiFi. Yes there's latency issues with VD but we want to have such picture via Link and VD shows that it possible. But waiting for that is just killing me 🙂
i7-8700, RTX 3080, 32Gb RAM, 2x1 TB NVME, Quest 2.

artscout
Protege
Another thing that just baffling me is why they felt the need to encode video for Link, correct me if I'm wrong, but ATM I have two 4k monitors connected via single USB-C port with HDMI adapters to my macbook pro at my job and it works just fine and I don't think that there's any encoding going on there. So they have usb-c on Quest - why not just send uncompressed video signal through? As there's "ALT mode HDMI" released in 2016 it certainly possible (well maybe there's resolution to consider, but anyway the point stands). But I'm not pro in such things so this is just speculation, never mind that 🙂
i7-8700, RTX 3080, 32Gb RAM, 2x1 TB NVME, Quest 2.

TomCgcmfc
MVP
MVP

artscout said:

Another thing that just baffling me is why they felt the need to encode video for Link, correct me if I'm wrong, but ATM I have two 4k monitors connected via single USB-C port with HDMI adapters to my macbook pro at my job and it works just fine and I don't think that there's any encoding going on there. So they have usb-c on Quest - why not just send uncompressed video signal through? As there's "ALT mode HDMI" released in 2016 it certainly possible (well maybe there's resolution to consider, but anyway the point stands). But I'm not pro in such things so this is just speculation, never mind that 🙂


Well, you're a Pro at multi-posting, that's for sure, lol!
i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 32Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with Etsy lens mod and Index Controllers

CactusCowboy
Adventurer
Even worse, Oculus Software seems to constantly encode the dashboard even though the Quest Headset is in sleep mode which causes a lot of power consumption. Even with Rift S you can see a at least 30W power increase of your system, depending on your graphics card. How hard can it be to add a
If (headset == Mode.sleep)
{
Encode.link = false
}
to it?. Even worse, the Software starts randomly on bootup at times. 


In numbers:

PC in idle: 145Watts
PC with Oculus Software running and Quest in Standby: 253Watts