v17 PTC PC Software Release Notes

ShowbizDonkey · April 2020

Social Reporting

We’ve made improvements to in-VR reporting. These changes include:

Streamlined the reporting process.
Updated language around reasons for report.
Prevented reports from being submitted without evidence.
Improved clarity around when a report has been successfully submitted.

Oculus Link

General Stability improvements

Kareshi · April 2020

Oculus Rift/Rift S

Absolutely nothing, thanks for buying our HMD that we don't support.

MakGarett · April 2020

Oculus Link

General Stability improvements

Link still doesn't work anymore for me after updating Oculus app. Still no V17 on Quest side for the moment hope it will start to work again.

dhrto · April 2020

Yay more social features! Those are indeed the most important functionalities!

OK joking aside... in-VR reporting doesn't sound bad at all I must admit. Guess the Rift S died an early death. It's been just a over a year since launch and already seemed to be abandoned... tsk tsk...

adam.poole.313 · April 2020

dhrto said:

Guess the Rift S died an early death. It's been just a over a year since launch and already seemed to be abandoned... tsk tsk...

They didn't just abandon it they broke it first.

maxstep · April 2020

Rift S connected to USB 3.0 ports - before v17 I would rarely get the Rift S not show USB 3.0 and restarting the software would have always fixed it. With the latest v17 no amounts of restarts or power downs bring up the usb 3.0 status, I updated the drivers for the headset when prompted of course.

The only way to go back to USB 3.0 functionality is to un-enroll into beta, but if I understand correctly once v17 becomes public Im looking at a likelihood of the headset not seeing that the port is 3.0 for some reason, and just am worried. Thank you for the help!

Richooal · April 2020

My CV1 still works on this version V 17.0.0.83.462

I note that the experimental feature of glancing down to show the floor boundary is still missing from the "Experimental" tab.
Those people who enabled it are now not able to turn it off without a complete reinstall of the Oculus software.

Asking people to join in testing the experimental stuff seems like a good idea, but if you're going to end the experiment it would be nice to let people know. "What's New" could be used, for example.

sleepynero · April 2020

Any idea on when the new platform SDK will be up?

dburne · April 2020

Hmm interesting, not much of an update it would seem this time.

Richooal · April 2020

dburne said:

Hmm interesting, not much of an update it would seem this time.

A quick turn around too. Their "progress" stops for nothing. Not even fixing problems.

Meanwhile, millions of Oculus users around the world are rejoicing the ability to send and receive clickable links and report each other more efficiently. The joys of "social" media.

sleepynero · April 2020

My titles now crash on launch when my PC doesn't have internet. I've been able to play all of my Oculus titles offline prior to this update...

TomCgcmfc · April 2020

sleepynero said:

My titles now crash on launch when my PC doesn't have internet. I've been able to play all of my Oculus titles offline prior to this update...

Please let Oculus support know. Thanks

marcinbijan · April 2020

sleepynero said:

My titles now crash on launch when my PC doesn't have internet. I've been able to play all of my Oculus titles offline prior to this update...

Same here, Oculus exclusives crash on start

I rolled back to V16 and it's all fine

Koot · April 2020

5 PTC/release versions since small-size pinned windows are completely broken and don't work, is this some joke?

davevillz · April 2020

Many reports of crashes on startup on Pavlov even with people just using revive.

LibOVRPlatform64_1 0x00000000a3100000 + 180525

LibOVRPlatform64_1 0x00000000a3100000 + fa6ce

LibOVRPlatform64_1 0x00000000a3100000 + f6ffa

LibOVRPlatform64_1 0x00000000a3100000 + 17fe3b

Pavlov-Win64-Shipping 0x000000003d300000 + 40764c

Pavlov-Win64-Shipping 0x000000003d300000 + 963840

Pavlov-Win64-Shipping 0x000000003d300000 + 9a2b2c

Pavlov-Win64-Shipping 0x000000003d300000 + 9abead

Pavlov-Win64-Shipping 0x000000003d300000 + 9a285d

Pavlov-Win64-Shipping 0x000000003d300000 + 274e3a

Pavlov-Win64-Shipping 0x000000003d300000 + 2781ac

Pavlov-Win64-Shipping 0x000000003d300000 + 273243

Pavlov-Win64-Shipping 0x000000003d300000 + 27346a

Pavlov-Win64-Shipping 0x000000003d300000 + 27bb97

Pavlov-Win64-Shipping 0x000000003d300000 + 229ad76

KERNEL32 0x00000000f1bf0000 + 17bd4

ntdll 0x00000000f3800000 + 6ce51

sleepynero · April 2020

Some new system they're working on called "Verts" that now has to initialize when games start up.

This new system needs a oauth key to talk to graph.oculus.com, and crashes the platform initialization when it can't get it (eg, you're offline) since its eventually tries to convert nothing into a string.

jab · April 2020

That is some prime quality coding right there in need of some "General Stability improvements".

MysticNinjaSoul · April 2020

Wow really, completely forget about the ones that supported you the most. The Rift/Rift-S users, you have completely just thrown us in the corner. Guess I will be selling my Rift-S here soon, since every last update pretty much bricks it and I am spending wasted time trying to troubleshoot and fix it

DeliriumTrigger2113 · April 2020

This update causes my CV1 to report that it needs a USB3 connection despite being plugged into one. Switched ports, got the green check mark for a solid connection, put the headset on and nothing happens. Go back into the devices screen and it says "Poor tracking" when the screen is black and there's no audio. Tried reseating the HDMI cable, plugging into every USB3 port on my system, nothing worked. The only thing that fixed it was rolling back to v16.

I really hope you take this seriously and actually fix this before pushing it out to everyone as a release. My headset has been a bundle of problems since December, with low overhead, constant stuttering that can only be fixed by a reboot, a complete inability to do any supersampling without stutters despite having an RTX 2080, and other nagging issues like pinned Dash windows being glitchy. But at least on some level it still works. If this update is pushed to release as is, my headset will be non-functional.

If you need any further information from me like logs or want to do some troubleshooting steps to try and figure out the issue feel free to contact me at the email associated with this account. I'll happily help in any way I can if it means this software wont be released until the issue is fixed.

dburne · April 2020

Would be best to open a support ticket really, or at the least use the submit feedback feature.

Fangzhou · April 2020

Hope Oculus can unlock 90fps (or even more) for Rift S and let user choose 80fps if their PC is not powerful.

LuluViBritannia · May 2020

You're going to lose everyone if you keep making social updates only. A lot of people already lost faith in you.
Although for now, I'll pretend the lack of actual updates is due to coronavirus. After that, you better have something worth it for PC VR.

joaquitoguevara · May 2020

I notice some wobbliness in Oculus Link. I think this update reduced it, but it's worse than v14/v15. Like when in Virtual Desktop you throw your controller in a lattice fashion. Maybe it's some movement prediction or something. Anyone?

Xarstealth · May 2020

LuluViBritannia said:

You're going to lose everyone if you keep making social updates only. A lot of people already lost faith in you.
Although for now, I'll pretend the lack of actual updates is due to coronavirus. After that, you better have something worth it for PC VR.

Oh well ill keep buying games from steam untill they dont do something for cabled rifts and i also save some money due to lower prices in most cases,
rift s is not even getting new features wich should be for both rift and quest ^^ wtf at least enable us to use wmr so we can do more without you

Aesthetiker · May 2020

Are the developer aware of this problem? https://www.assettocorsa.net/forum/index.php?threads/issues-in-vr-with-latest-oculus-rift-firmware-update-resolved.61524/

Please have a look and report back.....

BigJimHunter · May 2020

Rift S broke again... Everytime I restart the oculus software that it tells me to, I touch my headset and it needs to restart again. I had this same problem a month or two ago.... why are they breaking the software in the same way they just fixed it prior????

Whoever they have making drivers for this stuff really is not learning from their past mistakes.

dburne · May 2020

With the latest updates seemingly more Quest centric, I wonder why they don't just put the PTC out for the Quest first, or even release the PTC for both Rift and Quest as well.

HwangPL · May 2020

Pavlov not working on 17. Reverting to 16 fixed the 'issue'

TheWors3 · May 2020

can you guys please allow quest to use the full color range while using link? blacks are grey and contrast is reduced, colors washed out...

blazeflre · May 2020

MakGarett said:

Oculus Link
General Stability improvements
Link still doesn't work anymore for me after updating Oculus app. Still no V17 on Quest side for the moment hope it will start to work again.

Same here I haven't been able to play since april 12

Richooal · May 2020

TheWors3 said:

can you guys please allow quest to use the full color range while using link? blacks are grey and contrast is reduced, colors washed out...

If you want the real deal, buy a Rift. They cost a bit more than a cable though.

v17 PTC PC Software Release Notes

Comments

Howdy, Stranger!

Quick Links

Categories