cancel
Showing results for 
Search instead for 
Did you mean: 

Meta Quest build v43 release notes

Ryanality
Community Manager
Community Manager

These features and enhancements will become available starting the week of August 8th, 2022.

Meta Accounts

We’ll begin rolling out a new Meta account structure in August 2022 that gives people more flexibility and control in VR. You’ll no longer be required to log into your Meta VR devices with a Facebook account. This also means:

  • We’re also evolving your Oculus profile to a new Meta Horizon profile, which you can customize as you see fit.
  • Your “Friends” will now become “Followers,” similar to Instagram’s existing model.
  • You’ll have the option to add your Facebook and/or Instagram account to the same Accounts Center as your Meta account, which unlocks connected experiences in VR.
  • We’re rolling out new controls to help you more easily manage your privacy settings.

Meta Quest Guide

We are rolling out the Meta Quest Guide. Now users can:

  • Watch device and feature tutorials
  • Check out what's new in our latest Meta Quest software release notes
  • Find answers to top questions and get troubleshooting tips to fix problems

Note, this will be rolling out to users gradually over time.

Help others find great discussions and answers by adding kudos and marking solutions to your questions.
63 REPLIES 63

Live a little and throw caution in to the wind.  You have a 3090 let it burn.

CutieMiku
Level 3

This last update v43 has serious performance issues...

 

Oculus bug CPU.PNG

 

Just have the oculus running without doing anything is consuming above 50% CPU usage.

In the previous version (v42) everything was excellent, but with the new v43 something is wrong...

Please, I ask you to make a report to the development team and make a revision in the changes and problems that this latest update released.

Under "experimental" there is a "Color-Space" (warm, cold, standard) ... this doesn't mean contrast, right?

So there is no contrast option on my device too.

I just shared this in the PTC thread, but for everyone here, there's a fix for the high CPU usage issue which some people are experiencing that's being tested right now. It's going to roll out gradually so that the team can monitor its performance. Keep an eye out for the PC build 43.0.0.188.173 which has the potential fix. If you don't have it yet, just wait a few more days and check again (I don't have the exact timeline for 100% deploy since it'll depend on how performance goes, but it shouldn't be too long). 

Help others find great discussions and answers by adding kudos and marking solutions to your questions.

Yes, it's different.

NomadsAnIsland
Level 6

Windows Oculus updated to v43 four days ago and again two hours ago. Headset updated to v43 yesterday.

 

Air Link has become unstable.

 

After the headset has been idle/standby/sleeping for a prolonged period on waking up and after the WiFi has reconnected the Quest Link status shows "not connected". Turning WiFi on and off or toggling between cable connection and Air Link does not re-establish the connection. Re-booting the headset in v42 would re-establish the connection but this is no longer the case in v43. The Oculus software has to either be restarted (Beta settings), the Oculus Service stopped and started or Windows re-booted to re-establish the connection.

 

Even if the connection is re-establish open Air Link in the headset often results in getting the three startup dots and dropping back into the home environment. After a few moments the connection will re-establish but opening Air Link once again gives the three dots and drops back to the home environment. After this you sometimes get a message that the connection was lost or not. In either case the connection will not re-establish until you either reboot Windows or restart the Oculus Service. Maybe one out of three times I'll be able to connect and startup Link.

 

Fortunately I have Virtual Desktop and Immersed installed so that I can restart the Oculus Service remotely. Neither of these suffer connection problems.


@Ryanality wrote:

I just shared this in the PTC thread, but for everyone here, there's a fix for the high CPU usage issue which some people are experiencing that's being tested right now. It's going to roll out gradually so that the team can monitor its performance. Keep an eye out for the PC build 43.0.0.188.173 which has the potential fix. If you don't have it yet, just wait a few more days and check again (I don't have the exact timeline for 100% deploy since it'll depend on how performance goes, but it shouldn't be too long). 


Honestly I don't see what's the need for all this rollout stuff?  Just put whatever is the latest on the Public Beta and leave it there and update it until most bugs are squashed.  Then maybe leave it on Beta for another month before releasing it as final. 

 

It would be nice if the same could happen with Quest updates and public beta program.  However, I guess if firmware updates were required then this may be a little tricky to do.  For example, you can rollback your PC motherboard bios firmware but there is always a risk that you'll brick it.

 

In any case, I think that Meta needs to review its Beta programs because right now quite a few of us feel like Volvo Crash Dummies, lol!

i9 9900k, rtx3090, 32 Gb ram, 1tb ssd, 4tb hdd. xi hero wifi mb, 750w psu, QPro w/Air Link, Vive Pro

Mantaray72
Level 2

Got the v43 and I don't see anything new.

Where or when is going to be possible to create a Meta Account and Horizon user?

My Q2 charges and works just fine with v43 as it did with v42. Sounds like an issue on your end. You also mentioned charging the device with an Anker (assuming) quick charger. Anker's chargers are known to kill devices. I know I've lost a few to them, as did a good bit of people I know. It's Chinese junk. Also, if it is a quick charger, you never want to use one to charge any device that doesn't support fast charging (pretty sure Q2's don't), regardless how 'smart' the charger is or what the marketing for it claims.  

Ryzen 9 3900X | Nvidia RTX 2080TI | 32GB G.Skill Trident Z Royal | Asus ROG CH8 | 2x1TB Samsung 980 Pro M.2 | Samsung Odyssey G9 Monitor | SMSL SU-9 DAC + Topping A90 AMP XLR Balanced + Audeze LCD-X Headphones | Spectrum Gigabit Fiber Internet

Charging happens on a hardware level, not software. The only time software 'might' have any influence or interference with a device's charging cycle, is when it is powered on and charging. Power the Q2 down completely then test its charging speed and capacity. If it charges fine completely powered off, then there might be some validity to your post, but I'm betting it won't matter and what you have is an internal hardware issue. I would also assume as I replied earlier that it was brought on from the Anker charger and it is either A) pure coincidence that it decided to finally manifest itself around the same time as the update or B) you're just now actually noticing it, cause you are paying more attention.  

Ryzen 9 3900X | Nvidia RTX 2080TI | 32GB G.Skill Trident Z Royal | Asus ROG CH8 | 2x1TB Samsung 980 Pro M.2 | Samsung Odyssey G9 Monitor | SMSL SU-9 DAC + Topping A90 AMP XLR Balanced + Audeze LCD-X Headphones | Spectrum Gigabit Fiber Internet