Hmm... Usually when it shows 120 or even lower Mbps available, stuttering is more likely to happen and more severe, but that was with earlier version of beta firmware (should be from early this month).
I haven't tried to replicate the same situation again with the latest beta firmware as I kind of getting used to just restart the router before each VR session...
Had another VR session today. The Flint 2 has been running since the last post (3 days ago) and I intentionally not rebooting it before starting a new VR session.
When I first started VD, it auto detect and shows only ~45Mbps available. So I disabled the auto bitrate detection, relaunch it and manually set to 120Mbps, which is the same bitrate setting as my last post. The rest of the setup is the same as last time.
The experience is definitely worse and I recorded it. The network latency is quite unstable and there is an obvious major stutter around 1:32.
After that, I rebooted only the Flint 2 and everything is good again.
1 Like
Good day, I've just bought the Beryl for PCVR and have noticed the latest beta driver V.4.6.3 has "improved WiFi driver"
Would that be best to install?
Hello, I was just searching the web. I bought the Beryl AX and it works amazing with Virtual desktop. But now I can't seem to get Meta Link or Steam Link working anymore? Is the a setting I need to enable to allow these to connect again? Im using Quest 3
Hello. It should work out of the box, set as AP or not. Virtual Desktop is much more robust than AirLink, connection wise and stability. Try pairing your headset again to the Windows APP, maybe using a USB cable to help making the discovery of the device easier.
Hi, I have been using the Flint 2 for a few months now and am also experiencing lag spikes/stuttering. I can't really figure out what is causing it, as it seems to happen at any bitrate. I haven't been able to figure out how to fix it. Are you still experiencing issues with it?
I have ordered a Beryl which should arrive today, that I wanted to make a comparison with vs the Flint 2.
Hi, I am thinking of getting the Beryl or the Flint 2, did you manage to compare performance?
Thanks
Just got my flint 2 and trying to set it up as a separate AP dedicated for PCVR (Quest 3).
The setup is Orbi satellite-->flint2 AP-->PC. Will be playing VR in another room, as the PC room is too small. It's about 7m away, a wall and a door. Would really appreciate a tutorial/walkthrough with some recommended settings. Power mode, chanelselection, 2.4ghz on or off and so on. Sadly I have a chimney blocking the room i will be playing in to some extent, if that matters.
I'm afraid 7m away, with a wall, a door and a chimney in between the router and the VR headset might not give you a good signal, but you can definitely try and see.
For best chance of getting good experience, I would say disable all 2.4ghz wifi on the router, only have one single 5ghz wifi AP which your VR headset connects to.
For power mode you can set to max.
For channel selection, that depends on your surrounding. You can use some wifi analyzer app on your phone to see which channel has less wifi AP.
For channel width, at least 80mhz. If your surrounding are not crowded with other 5ghz wifi AP, try 160mhz.
And, the PC must be connected to the router via LAN/Ethernet cable.
Give it a try and see how it goes.
So I did a quick test. I set the Flint in AP mode connected to my Orbi node. I did disable 2.4Ghz network and put the 5Ghz to AC/AX only and in 160mhz range prior to putting it in AP mode. And fired up the quest 3 in my sons room. Connection seems to be fluctuating between 1777mbit and 2400mbit, that should be more then enough?
However I can't access the Flint now, should I have disabled DHCP before putting it in AP mode?
When I look in my main router device list the Flint is not displayed, but it seems to work. Although the led light keeps flashing white on the Flint.
In AP mode DHCP is disabled automatically.
You can find the IP of Flint 2 in your upstream router and access it using that IP.
I've already tried that. My router doesnt display the Flint at all.
When in AP mode Flint light is flashing, but everything seems to be working. Although i can't find it on my network, but today i noticed that the light had stopped flashing. I could see Flint in my router device list now and could connect to the ip adress. But after a couple of hours it starts flashing again and it's not displayed in the device list
I recently started using the GL-AXT1800 (Slate AX) so I could use a dedicated 5 GHz DFS channel and it fixed all of my lag issues I was having with the Flint 2.
The Slate is connected to the same network via the Flint 2 with the PC.
The Slate configuration is very basic. Fresh reset, configure 5 GHz on channel 52 (DFS) at 80 MHz in ac/ax mode in WPA3. Disabled DHCP server and connected the Quest to that wireless network.
My Quest Pro now streams using Virtual Desktop without any stuttering.
I really think the keypoint for me was having it dedicated to the Quest and also on a DFS channel. Those were almost unused here. I used 80 MHz to not use the band that's just above that had a nearby device on it.
1 Like