Is there no one checking these 'updates' before release? I encouraged two co-workers to go out and buy the Rift recently. With in one week of ownership, one co-worker suffered the 'infamous' no display crash after a forced update...the other co-worker is now suffering no display from the latest 'update'. Both were overjoyed upon initial setup. Both are extremely disappointed with the short span between going from fully functional to non-working experiences. I can't in all seriousness, recommend the headset any longer...not until the updates stop breaking already functioning features. Oculus needs to get a larger test group to better allow for compatibility testing BEFORE releasing 'fixes'. While we are at it.... Why is it necessary to re-download the entire setup package (5+ GB) each and every time a repair doesn't recognize the original registry entries through a simple broken link? Why can't I save the originally downloaded package complete with an executable like every other software program on the market and just reinstall from that? It's not good boys...fix these issues.
Just starting in with the Rift, and I like being able to see my desktop from Home, but I have to ask, just *how* was it not a no-brainer to emulate mouseclicks on the desktop by pointing and pressing the trigger with the Touch controller? Seems very obvious and intuitive to me, but perhaps there's some technical hall of mirrors issue I'm overlooking?
Just starting in with the Rift, and I like being able to see my desktop from Home, but I have to ask, just *how* was it not a no-brainer to emulate mouseclicks on the desktop by pointing and pressing the trigger with the Touch controller? Seems very obvious and intuitive to me, but perhaps there's some technical hall of mirrors issue I'm overlooking?
The Touch Controllers work like a mouse (point and click with trigger) for me. I wouldn't know where to start trouble shooting that one.
Anybody else having Oculus Dash go from using 7% CPU to using 25% instead? I'm not stuttering just having Dash opened, when that wasn't the case prior to this update
The only thing I noticed with 1.33 is that my Dash memory went up from ~500mb to ~750mb. Otherwise I have not seen any diff's with it's cpu usage, esp. when running apps that automatically shutdown home 2.0 anyway. Mine is usually ~5% cpu. Obviously Dash cpu usage will increase if you use the oculus button to activate it while you are running a game.
If you are experiencing stutters in some games maybe this is due to you having limited on-board RAM (like only 8gb vs recommended 16gb). This can cause your windows system to create swapfiles which will slow things down a bit and increase the demand of your cpu resources.
Also, check that your sensors are properly setup and preferably using usb 3.0 on at least one of these. I've noticed that with 1.33 sensor tracking is a little more sensitive and I needed to redo my sensor setup and reorientate my sensors slightly.
Games still run fine, it's specifically Dash that behaves this way. Updating drivers and redoing setup did not fix anything.
Neither did messing with its graphics settings.
There is most definitely an issue with it.
Well maybe it's a good idea to contact Oculus Support and start a ticket. Maybe they can help you track down this problem since it does not seem to be very wide spread. In fact there seems to be a lot less issues with 1.33 compared to the previous couple of updates.
You may also want to check that your gpu drivers are up to date. I just updated my Nvidia drivers from 398.82 to 417.35 and this seems to be working well for me.
Sending support ticket. I'll get back to you guys with how that went.
Anyone getting this update to work using a CPU Hack Installer for non-supported cpu? Can OCULUS SUPPORT please ask their Support if 1.33 blocks these even if we run a hack?
Support doesn’t know what they are talking about anymore. Telling people to repeatedly reinstall screams of a very lazy and unknowledgeable support staff.
Support doesn’t know what they are talking about anymore. Telling people to repeatedly reinstall screams of a very lazy and unknowledgeable support staff.
to be fair, I've been told this almost every time I've lodged a support ticket, so it's not a new thing
Though you are more than slightly incoherent, I agree with you Madam, a plum is a terrible thing to do to a nostril.
I have lodged a few support tickets and never have been told to reinstall. Always just asked to download/repair and this has sorted out any problems. This problem seems to happen if you opt in and out of the public test channel a lot.
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
