An "AirLink works better for me than Virtual Desktop" VR Wireless Performance Guide
!For a school project my teacher told me to make my wireless VR system smooth like butter and also to show my work. !<
My System Specs (midrange 90hz battered veteran):
- - Ryzen 5600X, 64Gb 3600 DDR4, RTX 3060TI
- - Windows 10 LTSC (very clean install: TODO)
- - Asus RT-AX55 [quad core model, #2 on the VD recommended list] with 5ghz for VR only (more or less) *flawless*
Tweaks Performed
OCULUS
- Changed 72hz @ 4128x2096 (Auto) to 90hz @ 3936x1984 (one tick above the auto for 90)
(I insist on 90hz for myself, but in a prior life (on Index) I was an 80hz guy from time to time. You might consider that if you someone like prior GTX 1070-owning me. Less so than the eyestrain, 72 hz just kinda scares me in how much of a smaller number it is than the other two.)
- Start initial AirLink connection and configure AirLink to use a fixed 200 Mbps Bitrate
(These days, maintaining a stable fixed transmission rate of 150-200mbps (or purchasing a used router on ebay to accomplish said goal) isn't as daunting as it used to be. Setting it to 250 (or higher) in ODT seems popular, but you may want to keep it at 200 just to avoid the potential settings-clash. Importantly, you'll want to try to avoid using the dynamic option, as it seems to be aggressive at lowering the bit rate when your otherwise decent router experiences a small hiccup. (Because it's drunk.)
STEAMVR
- Advanced SS Filtering OFF, set Default Resolution from Auto to 100%
(This generally regarded as common practice. If set to Auto, SteamVR will take the resolution from Oculus, and give you a higher resolution in SteamVR games if its math thinks your gpu can handle it. Mine defaulted to 150%, which does seem high.)
- Lower Quality of System Overlay to Low
( This shouldn't be noticeable and likely helps if running/switching between SteamVR and Dash.)
OCULUS DEBUG TOOL (ODT)
- Force HEVC Codec
(More or less a now brainer, unless you're on a old graphics card or driver. By default my RTX 3060ti on the latest driver defaulted to H264. Boo.)
- (Maybe) Disable Mobile ASW:
(AKA https://developer.oculus.com/blog/air-link-framerate-insurance-afi/ this seems to be a useful feature for those with less than great router or game in different rooms. I have it disabled.)
- (If desired) Change Link Sharpening to Quality:
(I didn't notice any 'harshness', and if it has a performance impact might likely be worth it.)
- Force Sliced Encoding Off:
(The default will likely be 'Off', but with this enabled the frame will be encoded in 5(?) seperate chunks to reduce latency, yet this seems to be a common cause of that horrible micro-judder. If your encoder frame rate shown in the Link Performance Overlay is maintaining frame rate then latency will likely not be noteacble at all (for most players/games) and you should aim to eliminate judder and disable Sliced Encoding.)
- Set Manual Encode Resolution Width:
(This is important. Due AirLink's conservative nature (or perhaps some small bug) leaving this to Auto/0 seems to result in the encoder resolution being much lower than the render resolution resulting in a blurry image that your GPU effectively spent cycles needlessly super sampling. My 3936x1984 in Oculus Home resulted in an actual render resolution of 3968x2000 (matched in SteamVR @ 100% and the ODT in HMD performance overlay). Setting this value to 3968 resulted in ODT reporting the encoder resolution @ 3968x2080, and NVENC was continuing to maintain frame. So. Much. Better.)
Bonus/Honorable Mentions:
- Holy hell you can disable Oculus Dash! https://github.com/LibreQuest/OculusKiller/tree/main/OculusKiller When this you cant play Rift games (unless through revive :/) and there is some awkwardness with quitting steam vr (it auto restarts if the airlink connection is still active, so just shut down oculus home instead), but this is otherwise totally awesome. Unless you play lots of Rift Games and/or can spare the video memory, considering disabling Dash, and then maybe also forcing the use of the SteamVR API by setting to be both the default OpenXR runtime and also enabling the experimental option in OpenVR advanced settings that attempts to force games to run in SteamVR mode.
- I maintain the superstition compelling me to force the OVR_Server process to 'High' priority, and I found a nice way to force that without having to install 'Oculus Tray Tool': https://www.reddit.com/r/oculus/comments/k6he9b/comment/jon4ia1/?utm_source=share&utm_medium=web2x&context=3 . You might need to allow powershell to execute scripts: https://superuser.com/a/106363
- Still a bit foggy on this. I enabled 'Universe Centered Rotation' in Open VR Advanced Settings in an effort to get something close to Virtual Desktop's quite effective 'Stage Centered Tracking'. This is useful if you want/need to play SteamVR games in a more roomscale fashion, and in the case of VD, it keeps the SteamVR playspace (not the chaperone) locked in the proper place -- with Airlink the playspace is at some random rotation, but the center marker stays put, which is at least half correct.
- Enabling VRSS (if your favorite game supports it) in the Nvidia Control Panel could be fun also. Were I to be on a potatoe GPU, I might also hazard an attempt at lowering the Texture Filtering to 'Performance' mode and enabling the Sample Optimization option. If even possible, that poor player is likely not going to notice the reduction in texture filtering through a hastily encoded low resolution stream anyway, and it could reduce frame times a decent amount right? Why else would standalone titles have such weak anistrophic filtering, eh? See the Crimson guide if you really need to outfit a weak system: https://www.reddit.com/r/oculus/comments/uwigp9/crimsons_new_and_improved_guide_to_optimizing/
Words:
I've been trying to find Morpheus through the staticky fog of wireless VR for a few years now. As others may attest, through the trials and tribulations of swapping out routers, updates, update bugs, experimental features, etc, it's somewhat of a two steps forward, one step back situation, eh. I had Virtual Desktop before Airlink was a thing, but the latter seemed to work better on a crappy TP Link router, so I wasn't able to use the solution many people were making earnest claims to being better for a long time. Then I got my Asus router (mwah) and switched to VD and couldn't stop raving about it.
Then after about a year or so of updates (juicy ones) something either changed (I think it was sliced encoding) or my want for a more smooth experience jumped up a notch, and I couldn't figure out how to iron out some pretty consistent problems with micro judder. I can reinstall VD right now, set it to low, use any of the codecs, jump down into the streets of MythOS city, wave my hands in front of my face all john cena like and get that horrible hitching. Again, I think it's sliced encoding, which might now be only disable-able in some kind of registry option? Is it tracking stutter? With my airlink setup, I glide down the tube onto the pavement and flash gang signs to the dead null men without a hitch at a frame time so low I'm pretty sure I should be running this all at a higher resolution tick in the Oculus Home slider. I'm bustin.
VD has alot of convenience features I really enjoyed, for both the desktop, video playback, and vr streaming sides. You can notice the improvement in color banding when the added HEVC 10Bit, I will miss that. There are dozens upon dozens of (non game streaming) applications/spam that aim to implement only some of what Virtual Desktop does. Were I to need to do lots of Cinema watching, or desktop work with my headset on (which I generally don't but think it's important) I would just use Virtual Desktop. Atm though, I'm back to Airlink, and it's so smooth. I also tried the recent version of ALVR (just for fun) and they're super far along in their progress, and it has lots of bells and whistles to play with.
YMMV glhf
Posted Aug 24, 2023, 8:36 PM UTC
"Setting it to 'High' is said to "give more pixel density in the center whereas “Low” reduces distortion on the border of the lenses and thus gives more clarity in the periphery of your vision."
The description of the debug tool says so, but in fact the setting item name is wrong, so the result we get is the opposite. In other words, Low makes the center clear, and High makes it blurer. When we display the layer HUD, we can see that the internal setting is high when we set low and low when we set high.
Shit, I thought that was the case the first time I read about it, then ended up deciding it was High. Thank you!