For me not a single disconnection from weeks in V66 Europe 6E 6Ghz alone since I’ve switched the AXE TPLINK from AP to router and used max dedicated links between Q3 PC and router (dedicated adresses, HMD MAC and PC Mac use, no DHCP, reserved HMD adress etc… etc…) as well on the router, the PC and the HMD. I kept the channels in auto. So the problem seems solved now, at least until next update ?…….
My router has only basic options to change. The only channels available to select on my router are 36, 40,44 and 48.
So now it seems I have to buy a different router, even thought the one I have WAS working fine?
Which one should I buy that's NOT going to have this issue? Maybe, seeing this is a problem Meta has caused, we should get a voucher towards the extra cost?
Or, there's a simple answer, LET US ROLL BACK OUR FIRMWARE SO WE CAN USE THE WIFI. I don't care about features you've added, I only use it for PCVR.
This is not about WiFi on our side. I have all the options you mentioned enabled for WiFi 5GHz, and I am distant less than 1 meter from the Router. These drops are an OS issue. It is a software bug or whatever that needs to be fixed.
I agree, this is not a problem with the user's WiFi setup. Personally my headset was working flawlessly on 6ghz for the first 6 months since release day. Then came v64 update and the disconnections started, and now here we are on 40 pages of messages, 3 further version updates and users are still reporting it's not fixed and are being directed to adjust their wifi configurations. @TheLegend27 I don't think users are getting the feel good factor from the company at the moment. Meta should consider some kind of compensation to be offered to the affected users as a way of apologising for months of having not fixed the issue, it's not like they are short of funding after all.
This is useless advice and it aint fixing nothing. The team **bleep**ed up the firmware and has to fix it.
Either way, im sending in my quest since its still in waranty, tired of dealing with this bs, especially since we cant even downgrade our firmware to the last stable version. Literally no other device in my household (Laptop, TV, PS4/5, PC, Heater) has those problems
Hi I made an extensive description of my successful configuration in a previous post, you can search my last posts through my my ID. Typically keep the router mode in place of the AP mode and dedicate as much parameters you can like fixed IP adresses, stable MAC values etc….
That's great but that doesn't help tons of us who don't have combined wifi routers and instead have a router where the Internet enters the house and several APs hardwired throughout the house. There is no "router mode" on a real AP.
I think it would be great if we could get some reassurance from support that Meta is working to fix the issue, instead of always being told to check our setup. It's been proven time and time again that the issue is on their side. I've never had such a bad experience with a device. I have a PS5, laptop, desktop computer, cellphone, and the Quest is the only device presenting this problem.
This is my first experience with Quest and a VR headset in general, and it's been plagued by this issue since day one. I actually got the headset with PCVR as my main focus, and that experience has been completely ruined by this problem.
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
