cancel
Showing results for 
Search instead for 
Did you mean: 

v17 PTC PC Software Release Notes

ShowbizDonkey
Retired Support
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
54 REPLIES 54

sleepynero
Explorer
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
MVP
MVP


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 
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

marcinbijan
Honored Guest


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
Explorer
5 PTC/release versions since small-size pinned windows are completely broken and don't work, is this some joke?


davevillz
Honored Guest
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
Explorer
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
Rising Star
That is some prime quality coding right there in need of some "General Stability improvements".

MysticNinjaSoul
Explorer
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

DeliriumTrigger
Honored Guest
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.

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