Inspiring

Quest 2 / Quest Build 27.0 Release Notes

88 replies
30470 views

These features and enhancements will become available starting the week of March 15th, 2021.

Bug Fixes

Fixed an issue blocking the overlay keyboard from displaying in third-party apps where multiple fields are present in a form.

Known Issues

Some users may see an error message, “System Alert Error” related to the cooling fan. This error message is false and the headset is working as it should. Users should click out of the error message and continue to use their headset as normal.

This topic has been closed for replies.

Show previous replies

F

Fangzhou

Up and Coming

Tested Oculus Link USB connection speed several times, it is at 700-800Mbps even with USB 3 connection. Tried with different USB port, both USB 3.0 and 3.1, both USB Type A and Type C, all same result. I am using the official Oculus Link cable. If I still try to use the Oculus Link, the connection will break in few minutes and try to reconnect immediately. This cause SteamVR hangs and have to restart game, so I cannot finish any song in Beat Saber now.

Got Oculus Link connection problem and 100% reproduceable. After connected for few minutes, Oculus Link just disconnected itself and reconnect again, which causing game crash/fail. I cannot finish any song in Beat Saber when connected to a PC now, it is 100% going to crash before I finish a song.

And what I have mentioned in previous reply, Quest/Quest 2 controller tracking latency significantly increased and unstable after v25, and not fixed in v26, worse in v27. Now even Quest version Beat Saber not

BTW I tried to use Rift S after that, got controller tracking problem. The controller just hangs in fast movement, also 100% reproduceable.

Funny fact: now in all the Oculus devices, only Oculus Rift CV1 can be used for Beat Saber (which is a Oculus game). Oculus Quest, Rift S, Quest 2 all sucks for Beat Saber. These devices used to be good, until Oculus Software ruins the experience.

S

stargazer19672

New Participant

Since update v27 I have no sound on my Quest 1. If I restart it, it comes on again. But when I pick it up later on, the sound has gone again. Anyone else have this problem?

S

sniperfox99

New Participant

Hmm. On V27 with Quest2. With my Link cable plugged into my motherboard, the test shows 896 Mbps (Previously, id get over 2Gbps). But when i plug the link into my RTX 2070, I'm getting 1.7 Gbps. Does this tell us anything?

D

Dadbart

Participant

I lost Guardian from this update. Says there was an error and Guardian has been disabled. Numerous restarts and enabling-disabling Guardian does not fix it.

T

TomCgcmfc

Honored Contributor

I needed to re-do my guardian after my Q1 v27 update but no problems since. Actually everything including Link (with v26 Oculus desktop app) is working very well. When I first started up Link after this update the Oculus home environment was a bit shaky but after exiting it and re-starting it all was fine. Thanks to my nice new rtx3090 I'm able to use the highest quality graphics (slider all the way right, 1.3x with Q1) and everything looks very nice. Best I've seen with Link so far. Using official Link cable connected to my asus hero xi type-c usb3.1 gen2 port. I have not bothered to do a speed test since everything is in the green and seems to work well.

I still prefer to use my Q1 wireless w/VD and my Rift cv1 (with 2xSS) for Oculus wired PCVR (esp. flight sims). Link does seem to be improving all the time so maybe one day I'll be able to retire my good old Rift cv1, lol!

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 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

D

Diskord23

New Participant

This update has made my Q2 fundamentally useless, fix the tracking bugs etc or I will be asking for a full refund very soon

D

Dadbart

Participant

Agreed, it is widespread. They need to address it quickly and improve QA for future releases if they don't want to lose all the ground they gained to HTC when they release their new wireless HMD. This was really inexcusable due to the level of damage it caused to usability.

T

TomCgcmfc

Honored Contributor

More over-stated complaints imho. If you are actually having a problem contact Oculus Support. Complaining/ranting about it here or reddit on a user forum is not very useful imho.

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 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

F

Fangzhou

Up and Coming

Yes Yes Oculus never had any bug, all bugs caused by customers, lol

T

TomCgcmfc

Honored Contributor

Ya, maybe not all but probably the majority are user errors imho.

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 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

C

chert1024VR

Inspiring

The best thing Oculus could do in this situation is to allow downgrades of both the headset firmware and the PC app so that we can have the choice to solve these problems on our own. Not one version of firmware and PC app will flawlessly work with all the myriad of PC systems out there.

In this way, if the current versions of the firmware and app don't correctly work with your PC and headset, then you can always go back to older versions which do.

D

Dadbart

Participant

As an update. I was able to eventually get it working for now. I found that Guardian would work fine everywhere in my house except my usual preferred spot, which is semi-prone on my bed. I did clear history when it stayed enabled. Also I was setting it to stationary. I found that I could go all the way to the edge of the bed, facing the same direction, and it would work. I moved 6" at a time toward my usual spot by the headboard and about halfway up the bed it would stop working, turning it off and back on each time I moved. So I tried it again, this time leaving it on and letting it prompt me to setup Guardian as it moved out the previous one. Doing it that way I was able to get all the way to my preferred spot and have it stay enabled. I restarted and shut down about 10 times after this and it continued to work.

So at the moment I am working again with Guardian. However, something is obviously wrong that I had to go through all of that to get it working again. The problem started immediately after updating to v27, literally after the restart from the update. It worked moments (and months) before that update.

Regarding all the fluster since my last post. Just because someone does not experience it does not mean they don't have a bug in the software. In this case it appears to be very specific to how it is used for location and position. So many may not ever hit it, but others will. It is clearly widespread enough to know that it is a bug as opposed to "user error". My last communication with support leads me to believe they know this and are working on a fix.

S

Spyder17

Inspiring

Seem like there is something wrong with the guardian memory or cache. I can be in one space that I have used for months and constantly get the lost tracking. I can move just outside this area and I am able to create a new guardian and have no issues. Even have one play space that I created sitting down (Stationary Guardian) which has the tracking issue. When I stand up I can create a new guardian as room scale with no issues.

S

Spyder17

Inspiring

Got a response back from Oculus support so hopefully will get a fix soon:

"We have received number of reports with the same concern regarding Guardian on v.27. We are aware of this matter and our Engineering team is currently working on a fix on this.

Thank you for your understanding, and hopefully this will be resolved on the next update."