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

Mazda_Ron
Expert Protege


Yep, it's looking good with the latest update + OTT at 3664 and distortion curvature Low. As above the Desktop is getting close to wireless/VD with 1.4SS.
It's gona be awesome when they unleash native res 🙂


have you checked framerate? putting 3664 and the preset to quality in oculus software, even with the asw turned off I was at 36fps locked in asw, I'm downloading latests ptc to see if things changed, but maxed before it looked no better than my cv1 but ran like absolute shit.

TomCgcmfc
MVP
MVP
I generally try a PTC to see if there is a problem or not, then go back to the current stable update (v21 in this case).  Rolling back by unchecking the beta box is usually pretty fast but in this case mine has been downloading for over an hour and I'm currently at 59% of 10 of 10 downloading.  I'm not sure why this is taking soooo long?  Maybe everyone else is doing the same thing at the same time, 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 2x2.0 base stations, Etsy lens mod and Index Controllers

TomCgcmfc
MVP
MVP
Took +2 hours to roll back to v21 but it did finally complete and all seems fine now.  I have very good internet (115mbps) so def a problem with Oculus server overload I guess.
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 2x2.0 base stations, Etsy lens mod and Index Controllers

Anonymous
Not applicable

TomCgcmfc said:

Took +2 hours to roll back to v21 but it did finally complete and all seems fine now.  I have very good internet (115mbps) so def a problem with Oculus server overload I guess.



It probably spent the first 1 hour 50 mins looking for V22, gave up, then installed V21. 🙂

VRus
Honored Guest
man, this update will go down in history books: true PCVR on standalone headset... finally happened! Many THANKS

SectionOne
Expert Protege
I'm using Nvidia GTX 1070.
In the past when I set the pixel density to anything above 1.3 I couldn't play because the fps was so low.
This time I tried 1.6 and the new Encoding bitrate with 500mbps and nothing happened. Looks terrible as always an no effect on performance.

With virtual desktop and 150mbps it looks much better.
Did the Oculus debug tool break with this update or something? (I'm Using Quest 2)

philneitz
Protege
UploadVR stated that there's a bug in the encode resolution option
Quote:
However, there seems to be a bug in this release preventing custom encode resolutions. The OVRMetrics debug tool indicates the delivered resolution simply defaults back to 2064. Interestingly, setting it to 0 (default) results in a new higher default of 2352.


I checked with OVRMetrics- and it's true, but it's "random" that it's staying on 2352 - don't know how to force it, even mit encode res set to "0"

Intel i9 9900K @4,8GHz
32GB DDR4 3700
GIGABYTE Aorus Pro WiFi
RTX 3080
Quest 1 + 2

AtlasActual
Explorer
Wow, I can say that I am genuinely surprised and happy they finally fixed something on the Rift S for once!

TheWors3
Explorer
I find it funny when people set the encoder resolution to a higher value and they think it makes a different when its actually bogged. I hope a fix comes soon because while compression is virtually non existant, the resolution is really bad.

Anonymous
Not applicable
I just leave the software set to use the PTC.
Has never really caused me much trouble.