Quest 2 Virtual Desktop Performance Thread

Folks, I want to use my PC wifi onboard as a hot spot but the 5GHz is not allowing to be enabled, it says "The selected network band isnt available" Select a different band and try again.

Thsi is a WiFi 6 AX201 160MHz Wifi capability, presumably this could be capable of connecting at 1200Mbs?

I would be grateful for your insights.

yeah, it's finicky as hell. You have to connect to a 5ghz wireless network from your PC, then enable the hotspot in windows, change it to 5Ghz. Then connect your Quest 2 to it.

Some people use Connectify's hotspot softwar, it's free. Just search for it on google.
 
Just tried it and unfortunately Im geting a steady 286. Its definitely capping at a ceiling of some kind...

I believe this is something to do with the 160MHz bandwidth? I cant select more than 20mhz it seems in the device properties?

Any thoughts?
 
Just tried it and unfortunately Im geting a steady 286. Its definitely capping at a ceiling of some kind...

I believe this is something to do with the 160MHz bandwidth? I cant select more than 20mhz it seems in the device properties?

Any thoughts?

It's windows 10, they changed the way the hotspot works.

Try making a 5Ghz hotspot on your phone.
Connect your PC to it.
Create a hotspot, using Wifi in windows.

If that doesn't work, try this.

Go into Device manager, right click on your wireless adapter, click properties. Go into advance tab. And there should be a option there to change your 5Ghz wireless mode from 802.11Ax to 802.11AC.

This should allow you to setup a hotspot without any problems, it will just be running at 866Mbs instead of 1200Mbs.

If that doesn't work. You should really try going to the connectify.me site and installing their hotspot software.
 
Thanks for your help mel.
Unfortunately whatever I do in settings or connecting my PC to my phone or to another 5GHz network, it is SOLIDLY locked to 286Mbps.
Im not even getting 866.

Does connectify allow me to change bandwidth?
 
Thanks for your help mel.
Unfortunately whatever I do in settings or connecting my PC to my phone or to another 5GHz network, it is SOLIDLY locked to 286Mbps.
Im not even getting 866.

Does connectify allow me to change bandwidth?

It's odd that none of the above worked for you.

Were you able to change the 5Ghz settings in device manager to 802.11ac?
If you were, did you do the same steps again? Connect PC to 5Ghz network, then setup hotspot, then connect Quest 2 to hotspot?

I haven't used Connectify.me, but, there was a Youtube video of a guy setting it up to work with his Quest 2. I saw it on some of the forums, can't find it now though, sorry.
 
Just tried connectify. Same

Damn, nothing working.

It's because of this (if you are interested)

Why Hosted and Ad-Hoc Networks Are Not Working on Windows® 10 (intel.com)

Try this though,

Make sure you remove the network from the Quest 2 before starting.

Now, Do the same as above, Connect PC to 5Ghz network using wifi. Make hotspot. Then connect your phone to the Hotspot. Now Connect your Quest 2 to it. See what speeds you are getting.

If that doesn't work, try this.

https://youtu.be/EV67AS4_TLs?t=201

I didn't find the video I was looking for, but I found this one instead.

Lastly, some people have had success from downloading the drivers for AX200 PCIe cards from Intel directly and manually installing them. Then download the manufacturers latest drivers and custom install them, selecting the repair option.

If none of this works. Buy a cheap Wifi 6 router.
 
Damn, nothing working.

It's because of this (if you are interested)

Why Hosted and Ad-Hoc Networks Are Not Working on Windows® 10 (intel.com)

Try this though,

Make sure you remove the network from the Quest 2 before starting.

Now, Do the same as above, Connect PC to 5Ghz network using wifi. Make hotspot. Then connect your phone to the Hotspot. Now Connect your Quest 2 to it. See what speeds you are getting.

You are a frikkin genius melmac. The above worked.

Except for one problem....

I was playing Roborecall. REALLY getting into it and then suddenly black screen.

Battery :D (Luckily my elite battery strap is on the way.

True wireless VR + PC games = FTW.


Why and how it worked, I dont know.
Very convulted process though! Why does it involve connecting my PC AND a mobile phone to the network...

I think... I THINK... connecting the phone to the hotspot PUMPS the speed up to 1200 and then disconnecting the phone after, everything fine.
So my latency has gone from 40-45 down to 26-30ish.

Is this reasonable?

Again very grateful to you melmac, thanks again.
 
Very convulted process though! Why does it involve connecting my PC AND a mobile phone to the network...

Again very grateful to you melmac, thanks again.

You are very welcome, glad it's kinda working for you now :)

The reason is that Microsoft has, basically, removed the 5Ghz Hotspot from Windows. So you have to trick windows into switching the hotspot into full 5Ghz.

The problem is, as you found out, finding the "trick" that works for you.

Your latency results are very reasonable.
 
Happy days :) Thanks again melmac, you really helped!

Are there any settings I could set in the WiFi to ensure best performance of the hotspot?
 
Virtual desktop + Quest2 is incredible!

Though I'm not hitting the 72hz of the Quests display (never mind the 90hz update) in Contractors VR, is this due to my network or because the my 1070ti is struggling with the increased resolution of the Quest2 over the CV1?

Right now I've capped the VR gsme streaming to 60fps, which feels perfectly fine, something im surprised about because for years we were lead to believe anything below 90hz in VR would make you sick..
 
Virtual desktop + Quest2 is incredible!

Though I'm not hitting the 72hz of the Quests display (never mind the 90hz update) in Contractors VR, is this due to my network or because the my 1070ti is struggling with the increased resolution of the Quest2 over the CV1?

Right now I've capped the VR gsme streaming to 60fps, which feels perfectly fine, something im surprised about because for years we were lead to believe anything below 90hz in VR would make you sick..

It could be a combination of both. What settings are you using in Virtual desktop?

And, I don't know what the ".." at the end of your last sentence means? Are you trying to imply they are lying to us or something? 90hz was needed for the Civ1, but tech has improved. Have you forgot that the Quest is 72hz and the Rift S is 80hz?
 
Cant remember off the top of my head, ill take another look when I get back on.

I dropped Contrsctors in game setting down to medium resolution and I got a steady 72hz, but everything is blurry, despite the increased Q2 resolution I would put it on par with the CV1

Maybe not lying, but its still something I read regularly about 90hz being the minimum, which obviously isn't the case, like you said, Quest 72hz Go 72hz and S is 80hz
 
Maybe not lying, but its still something I read regularly about 90hz being the minimum, which obviously isn't the case, like you said, Quest 72hz Go 72hz and S is 80hz

You didn't read my post, 90Hz was needed for the Civ1. The Quest 1 had improved panels and Lenses with lower persistence that offset the need for 90hz. The Quest 2 has LCD panels that are much better for motion than OLED panels.

And you capping the game at 60fps isn't changing the refresh rate of the Quest 2 to 60hz. The minimum refresh rate for the Quest 2 is 72Hz.
 
Now I have another problem.

I havent tried a game long enough to realise I am getting microstutters every... minute or two?

And they seem to be random.

I have no idea why this maybe... any ideas?

I have tried the lowest settings and still get the same, regardless.
Ive faffed around with the stream settings, nothing.
Ive changed the WiFi card settings to 5GHz only / 802.11ac etc.
Still same....

Could it be the wifi accesspoint from my PC?
 
Now I have another problem.

I havent tried a game long enough to realise I am getting microstutters every... minute or two?

And they seem to be random.

I have no idea why this maybe... any ideas?

This is an Nvidia driver problem. It's been like it for a few revisions. The good news is a fix will be in the next driver.
 
Back
Top Bottom