Old topic discard

Old info , quest 2 has now had official update

I’ve been experimenting with it over the last few days and it’s definitely an improvement.

Are you saying you’ve somehow updated your Quest 2 headset to a beta v27? I have updated the link software on my PC to v27 but my headset is still at v26, I couldn’t see any way to manually force a beta update on the headset and I can’t find any info about it online.

Could you give a more detailed explanation of how you updated your headset to v27?

In Oculus software settings select opt in to beta channel. After a few seconds the software will install an update.

Yes, I understand that. That is for the PC software. The OP specifically mentions that both their PC software and their headset are at v27. What you have described (and what I’ve done) only updates the PC software, both the graphical frontend and the Oculus Server service that actually interacts with the Quest 2. My question to the OP was how to force the headset itself to update to beta software.

After a reboot of the software it asks to install new headset drivers.

Yes. Those are the drivers that the PC uses to interact with the headset. That is all PC-side software, not headset-side. After having done all that, your Oculus software on your PC (Oculus Server, Oculus App/Store) will all be at v27.

That does not force your headset to update to v27, however. Quest 2 updates are done on the headset as you have to assume that not all Quest 2 owners are going to connect it to a PC so the update process has to be native to the headset.

The OP specifically mentions having their headset at v27. I appreciate your comments but what you’re describing is how to update the Oculus PC software, not the Oculus headset. Having done all of what you are describing, someone would still see their Quest 2 headset at v26 if they looked at the version number in the headset’s menus.

2 Likes

Headset running at Beta
this is confirmed by pressing “about “ in headset

If pc oculus software is at beta then headset only runs at 72hz, thus moving that back to non beta

Headset runs better with the beta driver

I enabled the beta version and my Oculus app updated to V27 and asked for a restart.
After restarting I got a message at the top of the app telling to update some drivers, which I did.
After that the app restartet again.
The app says it´s V27, but my Headset is still at V26.

V27 is unacceptable due to the flashing issue, so I have now reverted to V24 following the steps described here: (1) MSFS VR TUTORIAL & FIX - FLASHING SCREEN IN VERSION 26 | QUEST 2 | OCULUS #microsoftflightsimulator - YouTube

If this really is true, you are the only person I’ve come across anywhere online who is running a beta version of the Quest firmware. As far as I’m aware, Oculus does not provide betas of the Quest firmware. Are you absolutely, 100% positive your Quest is on V27? If you disconnect the Link cable completely, and go the the About menu in your headset, it says V27?

Anyone notice the fail in all this lol?

In that case, I really doubt the headset is running at 90Hz. Turn on the performance overlay HUD and look at the graph on the left. It’ll almost certainly show 72Hz.

Also, the only difference I see in this beta update is that they finally fixed the Link frame sync bug that was affecting MSFS and X Plane. So now it behaves the same as if you set V-Sync to ‘Fast’ on prior versions.

Beyond that I see no performance difference. It is probably just placebo, because everyone that was running at 90Hz before is now running at 72Hz, whether they realize it or not. And that by itself adds some significant performance headroom, but adds latency too.

Yes checked & defo 90hz
Defo increased performance too

Maybe it’s just suitable to my pc configuration

In any case hopefully the official update will come & benefit us s as all

Every little bit helps
Cheers

How are you confirming 90hz? what number are you seeing when in the FS2020 menu in VR?

You checked HOW? Turn on the performance overlay HUD that you can access either through the Oculus Tray Tool or the Oculus Debug Tool. Look at the graph on the left.

I’m sorry, but based on your earlier faulty claim, as well as the fact others here have the same version of the PC beta software as you and nobody else is getting above 72Hz with it, means you need to provide some proof. You already said that the “About” menu inside your headset showed v27, which then turned out to not be true, and in reality it was the info section on the PC software showing a long number starting with 27. That’s a pretty broad stretch which calls into question your credibility.

Many other people online using Link with the v27 PTC/beta software are also stuck at 72Hz, and I’ve yet to find a single person except you claiming to be getting 90Hz with it.

Yes of course checked with the performance overlay , I’d not have a clue of hz otherwise

I actually started to doubt my own claim after some of responding posts & clicked the oculus software to update headset back to standard v26 , I noticed a slight decline in performance (but still a good experience)

Switching back to the part as explained in OP ) it’s also quick & easy it works well for me at least

Thanks for interest anyway
Looking forward to the roll out official v27

1 of 2 things is happening here, as v27 is broke at 72hz and Oculus have confirmed this, for everyone!!! not some, not a few EVERYONE!

  1. Your just lying and really are at 72hz
  2. You are at 72hz but because you picked 90hz in the oculus desktop app, and restart then you see it indeed does say 90hz, it is infact running at 72hz, Even though it says 90hz in the desktop app.

Either way, if you’re on v27, your stuck at 72hz.

2 Likes

Yup. If what he’s actually doing is letting it update to v27, and doing the driver update, and then downgrading to v26 but keeping the v27 drivers – well, I already tested that myself. And the fixes that come with v27 no longer work doing that (frame sync is broken again), but of course it does restore 90Hz.

I think he’s mistaking that version number it shows when you click on the headset for the actual Oculus app version, which it isn’t. It’s not even the same firmware numbering scheme as the headset itself uses. It just happens to start with 27, possibly by coincidence, but it’s neither the headset’s installed firmware version nor the PC software version.

See my message above. And just to clarify, nothing you’re doing here is updating the headset. Installing new drivers is not an update to the headset. It does zero, zilch to the headset’s firmware, and you can prove this to yourself because you can install those drivers without your Quest 2 even connected :\

I’m sure @Adystealth is just trying to be helpful, let’s not bite his head off…

But @Adystealth, you need to post a picture of the tray tool in-headset performance overlay giving you 90hz in the FS2020 menu or at least reaching 45hz, otherwise we have no choice to disbelieve you I’m afraid!

It just doesn’t add up based on other evidence from Oculus themselves and other users experiences.

If you can prove you’ve fixed the 90hz issue we’ll all want to find out how.

Yes, agreed, and I do apologize if I came across as overly harsh. I just get drained trying to weed out misleading information in forums like these, because there’s so much constantly being added into the mix, it feels like a never-ending futile endeavor. It’s especially true in VR flight sim forums, because flight sim enthusiasts tend to be of a slightly older generation, and many of them are diving into the depths of VR for the very first time with, hands-down, the worst-performing VR apps available, lol. I’m not saying that to be discouraging, it’s just the truth. Flight sims generally run abysmally in VR compared to big-developer VR games.

All those ingredients together make these forums a lot of well-intentioned blind-leading-the-blind, while those of us who have been using VR for 5+ years try to keep the info correct and the placebo to a minimum :wink: Ok, I’m done complaining now :slight_smile:

2 Likes