The Public Test Channel (PTC) for Quest and Quest 2 v43 is starting to roll out. Let's use this thread for collecting feedback on it. Share your impressions and let us know if you see any issues. Please make sure to alsosend in bug reportsalong with posting here if you notice anything going wrong.
Thanks to everyone testing out PTC and sharing your feedback! We appreciate your help testing out the core functionality of software as we develop!
I also have high CPU load problem with v43 OculusClient.exe. Repair installation did not help. For me this makes Quest 2 PC VR unusable for sim racing ☹️
Up to date Win10, i5-7600K and 1080Ti, just Oculus software open, no games running:
Basically is 100% true what others have said regarding OCULUS LINK PC SOFTWARE (not on quest 2), version 43 PTC. I have a 9700k CPU , RTX 3080 and OculusClient.exe, without doing anything else just starting it, has 50-55 CPU usage. When i opted out from PTC and back to v42 on PC ( not on Q2), the usage was back to normal (0.5-3 %).
Something is definitely wrong in v43 OCULUS PC software.
V43 killing CPU so you rolled back to V42 a few days ago. All was now well. Why did you update to V43 again and not rectify the issue? CPU now working hard even when not using headset, AGAIN.... Task manager clearly shows Oculus software is not optimized again. So frustrating when the issue is known about and relaunched. I tried to remove my software and reinstall hoping to revert back to V42 with no luck!
Same here, i thought "well, at least its fixed" and hours later the V43 update appears.
This makes me want to throw the Quest through the windows, seriously, Oculus dev team test something? This is the things that makes me look for a headset not from Oculus for the next one...
I did not roll back. Oculus rolled there update back to V42 a few days ago. It was then fine of course. This morning they updated again. You totally misread my post. I did nothing. I do not do beta, i changed nothing. They moved the updates in house.
Estou tendo um problema absurdo com o uso exagerado e irracional do meu processador, não sou o único que quando você abre o ouculusapp se depara com 70% 80% da cpu usada, obviamente é um erro, nunca houve um problema com meu i5 9400f antes. na v42 sempre foi perfeito. Eu gostaria de tê-la de volta
Im running a Ryzen 5 5600g with a gtx 1080. used to run perfectly before V43 and now im getting screen tearing in the oculus link menus while navigating, its ridiculous how badly this update came out.
Hi all, thanks for reporting! I've updated the team about the CPU usage and they're investigating it. If you're still having trouble, it also helps to put in a bug report, with logs.
They did put out an update to correct a different issue which is why some folks saw v43, then v42 again, and back to v43. Also, v43 for Quest is starting to go out, outside of PTC.
Thanks again for testing and reporting! I'll let you know as soon as there's more to share.
This CPU-hog bug is affecting us Rift S users too. Near impossible to play my regular games without any warping now. Everything has been fine for months. It's absurd that you don't allow users to at least choose from the last 2-3 sets of driver revisions, or prevent unnecessary upgrades.
I own 2 Rift S headsets and my daughter has 1, we're daily users. Please fix this bug ASAP or at least revert back to v42 ASAP so we can continue to enjoy them.
This CPU-hog bug is affecting us Rift S users too. Near impossible to play my regular games without any warping now. Everything has been fine for months. It's absurd that you don't allow users to at least choose from the last 2-3 sets of driver revisions, or prevent unnecessary upgrades.
I own 2 Rift S headsets and my daughter has 1, we're daily users. Please fix this bug ASAP or at least revert back to v42 ASAP so we can continue to enjoy them.
TY!
@Skuzz420 I'm not sure why this should effect your Rift S unless you are enrolled in the public test beta on the Oculus desktop pc app which is v43? I'm on the non-beta and it's still v42 and I don't see this cpu-hog bug with my Rift cv1. Maybe download the oculus desktop app from the support website run a Repair. Hopefully that will land you back onto non-beta v42. Also, make sure to enable oculus openxr runtime on the top of the settings/general tab. Good luck mate and cheers.
Many of us had reported what we get V43 while not enrolled on Public Beta, right now the public version looks to be the V43.
I cant play with my Quest since one week due to the broken PCVR, im starting to think about selling my Quest 2 and buy another option, every new update comes with a surprise...
I wasn't in the public beta and was updated to v43 about a week ago. Then after a few days Oculus reverted back to v42 (works fine!), then later that same day, they updated back to v43 again.
I then tried the Beta drivers, which despite going through the download and install process, were the same v43 drivers as non-beta. I opted back out of Beta, it did the download and install, and I'm still on v43.
It's pretty much unsusable with v43. OculusClient.exe is using 30% CPU when idle, around 50% when gaming (usually 8% idle and 15-20% when gaming) on my i7 6700k, it causes most games to start warping.
I'll look for this Desktop App and 'Repair' option.
Im still stuck on v43.0.0.125 on the headset... PC app reverts back between v43.0.0.175 and v42.0.0.xxx I find it hilarious that we all got diff versions on our headsets and those of us that have broken PCVR (glitching etc.) isnt getting a new version pushed out.
Using the PC apps repair tool doesnt do anything - it just installs the same files from the Meta Cloud.
Thnx for upping the prices though - now I can squeece some more out of it on the second hand market! Im done with Oculus/Meta! Varjo have a diff level of customer experience 😄
I was referring to PC App too, no matter if you have a Rift or Quest, for PCVR the software it’s the same and the one that are causing the issue for all headsets
@Skuzz420 My pc app is still non-beta v42. Just lucky I guess, lol! I use the oculus tray tool to stop oculus runtime services after each PCVR session (link or air link) so maybe that’s helped, who knows? Also in the settings general tab I disable auto updates but that usually only effect’s games updates.
Hope it works! HMD is still on a broken v43.0.0.xxx version so cant use PCVR via Link or Airlink. Using it via VirtualDesktop atm. Can´t enter PTC again since Oculus Phone app says it´s full. My patience is running out and concider buying a Varjo Aero or Reverb G2 instead..
As I am forced to use v43, I will try to prevent the update in some other way, useless and horrible update. the funny thing is that the update was so poorly received that there are people like me who are trying to force v42 by dubious means for lack of support or control over the updates, disappointing and amateurish.
Did I read that correctly, v43 is being sent out to the masses??? What is the purpose of this thread then, I opt into the Beta (to help in any way I can) I report a major issue that others are seeing, I don't get any recognition of the issue what so ever and now the version is being sent to everyone. Well done!!
The worrying thing it's that it's not the first time, it looks like Oculus developers make 0, i men, ZERO testing and no ones looks for the user reports
From what I´ve seen, different versions of v43 is beeing sent out.. some seems to work fine while others includes the issues that several of us has pointed out. Seems like deadlines is more important that actual bugfixing.
What I find sad is that devs isnt working with us PTC testers at all - no response nor any signs of helping out. Would have been so easy for the devs to simply push out new PTC v43 version to our headsets to test out/give feedback on but nope.. silence and just a few posts where they say: We have found issues, new version out soon and we also release it to the masses.
I work for several game studios as a tester under NDA and they would run out of business if they did things like Oculus/Meta..
UPDATE! My headset have gotten a new firmware pushed out: 43.0.0.178.120 Finally my glitching issue is gone and I can use the headset for pcvr again.
This is my PC (1080ti and i5-7600k at 5 GHz) idling with the 43.0.0.175.173 client open and no headset connected. It is also a problem while PCVR gaming. I use the Quest2 for iRacing. With v42 I had 50-60% CPU during game (< 10% while idling) and smooth performance. Now, if I try to play iRacing the CPU usage is 90-100% and performance is poor.
After updating to v43 (43.0.0.178) airlink broke, when im moving the headset it also moves the menu bar and the whole room but desktop window stays still, it was working fine before updating. ( sorry for the first post)
Updated to Oculus App Version 43.0.0.175.173 (43.0.0.175.173). Developing in Unity and app performance is OK but CPU usage when idle is 30pct - fans are going crazy.
