Davolink x Universal Korea - Minions Kevin Wi-Fi 6E Router

**Do not buy the Davolink Bob router for VR.** The Davolink **Kevin** router is good for VR yes, it performs very well and has good 6ghz support considering it's price and unusual branded origins. However, this Cnet marketing promo is for the Davolink Bob router, it is a weaker spec Wi-Fi 6 (no 6ghz) router and performs poorly for VR.

It sounds like a joke, but the davolink Kevin is a great pcvr router. Its what I use. Virtual Desktop recommends it for a reason

Nice, i got 2 of these setup as AP's in mesh mode, they do great for device handoff so i dont have issues when moving about my house like i used to with non mesh/handoff AP's. Also, the wan ports are 2.5g, I have mine to 2.5g switches, so if there is other traffic like streaming from my plex server on the 5ghz band, i should still have plenty of bandwidth for the 6ghz that my quest 3 uses.

I have Kevin and no issues

I bought this unit [last year](https://i.imgur.com/6krGLoy.png) as a literal joke. I already had the Asus GT-AXE16000, which is orders of magnitude better. But I laughed so hard at it I had to see if it worked. And the damn thing lets you do 500mbps Virtual Desktop without issue over 6Ghz. At the time, it was hands down the best deal you could get for WiFi 6E VR router. Ended up keeping it and giving it to my son to replace his WiFi 6 5Ghz router.

That's not how fast data is actually traveling, it's just a measurement of the signal quality. It's called PHY Rate. If you are connected with a device that supports 160Mhz channel width and it has a perfect signal, your PHY rate is 2400mbps. If it drops by 1 bar that goes down to 1800mbps. PHY rate is a representation of the theoretical maximum transfer speed the connection could handle. The max data you're ever going see between the headset and your PC would be if you're using Quest Airlink and you max out the bitrate manually. The Quest 3 can decode h264 around 900-960mbps but, you need a really strong router to handle it. Most need to use a Link cable to sustain those speeds. VD caps out the Quest 3 at 500mbps.

>On this ptc 83 I've had to reboot a controller once on start up. Just a warning on joining the PTC. The amount of issues I had after joining it was insane. I did it because I wanted to try out a few features that weren't out yet and I regretted that so damn much. Mostly because once I went "screw this, I am going back to the main channel", I had to wipe the headset to get off of it. I don't know if that's still required but, it was at the time and it had me so frustrated(My internet sucks ass and I had like 400GB of stuff downloaded) >Ive never used an index, but I have seen my friends on index get wild player heights sometimes. I guess that is the play space getting messed up. Didn't know they had issues with that. Yep, that is a sign of it happening. There's 2 choices, either restart Steam VR or use something like OVR Toolkit to manually correct it. But if you go that route, you will have to undo those settings next time you launch. I've got 5 Steam VR native headsets. Vive Pro, Vive Pro 2, Valve Index, Varjo Aero, and the Beyond 2e. All of them have their share of annoying issues that I just have to live with. >That being said, my quest 3 friend has to fix his almost every time we play. He is on standalone. Dunno if he did something wrong or what. Most likely he has a corrupt play space saved. It will hold a few of them and if one gets corrupt, it will cause this. All he's gotta do is remove them all and set it back up and it will stop. On the plus side, the process to setup a play space on Quest is insanely easier and faster. Here are the Steam VR steps. - 1. Take off the headset and controllers and set them on the floor in the center of your play space facing the front of the play space. - 2. Walk to your PC and click the 3 lines on Steam VR and click room setup. - 3. Wait for the program to detect the headset+controllers and click next. - 4. Go pick up a controller and point it at your monitor and click the trigger. - 5. Put the controller back down and walk back to your PC and click Next. - 6. Click the "Calibrate Floor" button. Once finished click Next. - 7. Click Next to start the boundary setup. Walk back to your play space, pick up a controller, and then walk around your play space holding the trigger to draw out the play space. - 8. If it worked and you're space is how you like it, click Next and you're done. The frustrating part is you can't choose where you want the front to be, Steam chooses for you and if it doesn't choose the way you want it to face, all you can do is start over. If you launch a game when facing the wrong direction in Steam VR, you end up facing the wrong direction in game too. You also can't just turn your body and hold the menu button, it turns the whole play space so the boundaries don't align with your walks anymore. In Steam VR, that button is meant to reset the play space, not your place within it. So then you gotta go to the center and face direction it told you to and hold it again and then check make sure it's now aligned with your walls. It will never be perfect again until you redo the steps. Meta's "just make the front whatever way they're facing when the app is launched and let them reset themselves within that play space" is soooo much better. >Its all infuriating when you have a good network connection and a 5090, 9800x3d etc. Good equipment. Agreed, any issues like that can become frustrating fast when you spend so much. I haven't played Walkabout Mini Golf since earlier this year so I can't comment on how well it works right now. But I have got a few hundred hours in it and haven't run into that issue. I also tested the hell of the Quest 3, Pro, Aero, and Beyond 2 in the last few months with both an RTX 4090 and 5090. I have not run into any issues with frame rates using VD. Everything has performed as expected. I did see that VD released an a bad update a few weeks ago but it was promptly fixed. I wonder if maybe it was that?

It does have 2.5GB. Scroll down a bit to the specs. But, it only has a single LAN port. So to get 2, /u/SgtRphl would need to use a switch. Which would cut the capacity down to 1.25GB per device if they were both going full bore on the internet at once. So probably not perfect for their use case. https://www.amazon.com/dp/B0CJXZSLNM