After researching many cable vs. wifi posts, I tested both ways to see what the difference is?,
At the beginning, I did not doubt the convenience of wifi in VR environment. I was a beliver of wifi ways until I tested 7 wifi6e hubs and a PD-240w spec cable.
Basically after these test my experience is wifi connection is just for move convenience. It cost me 2 wifi6e hubs, but the connection was unstable and there was no real high video quality. Of course, I spent a lot of time improving the poor quality (wifi bandwidth is 2400 Mbps=2.4Gpbs), I still have the confidence to try everything to improve the poor quality of WIFI somewhow~ HAHA,
Then magic happened~
I selected a TYPE-C cable from the volt analyzer kit (PD-240w), Qlink started…
Then saw the true quality of Q3’s capabilities (maybe 2k? 4k? in VAM game) I’m not sure, but in msfs2020 still much better (quality + stable) than wifi6e.
All I can say is that wifi vs cable is like .mp3 vs audio CD,
My PD-240w cable is 2.5~3Gbps in the Qlink desktop app connection test. I don’t understand that the bandwidth sometimes changes? The wifi6e is 2.4Gbps but the results are very different~
Quality and stability are priority for me. will update to let you know when my new 5m cable + ceiling rope set arrives (usb3.2-G2-20 Gbps)~
If you want to know the new cable test details, please leave a message +1
If you haven’t already, perhaps something to also consider is video coding, e.g., h.264, h.265 etc. as well as the encoding bitrate (default vs override), fixed vs dynamic bit rate, latency etc.
It’s possible some of these factors, including others, may also be at play when making comparisons between wifi and cable.
I have a Quest 2 and by default, cable uses h.264 and airlink (wifi) uses h.265, however, that can be changed so wifi also uses h.264 which may look sharper at times under certain circumstances (pros and cons).
Virtual Desktop also supports additional coding options and configurable bit rates etc.
Today i tested the new Oculus app.
I have a 78003xd/4080 on a Asus 670E board. AX55 from TP-link is within 3 feet so full bandwith there.
VR is set to TAA, 100 resolution (TAA for readability of instruments).
So the Oculus app causes unsharp / blurred characters in the instruments and black areas when moving the head from one to the other side.
I did not notice a difference between cable and wireless connection with the Oculus app. But the experience was certainly not as you want.
Then i used VD on wireless and the instruments were crisp (can easily read the GTN750 from the pilot’s position without moving forward into the dashboard.
So i stay with VD and have put the USB3 cable back where it came from.
If that is what works best for you then just stick with it imho. I still think that Link works a bit better than VD or Air Link but maybe that’s because I have a rtx4090 and a Z790 mb. You can see my current Link, ODT, nvidia, win11, and msfs settings here;
The main thing to note is that while TAA can def give you better cockpit clarity, dlss/balanced will generally be smoother and produce less distant shimmering. The secret to improve dlss/balanced cockpit clarity to almost TAA levels is to add a little extra super sampling (pixel density in ODT). I use 1.20x and this seems to help a lot.
Unfortunately you cannot do this using VD (because it doesn’t have the official Oculus sdk), only with Link or Air Link. The only way I can get VD to get smooth stutter-free results is to add SSW, but this produces too many ugly artifacts above my heli rotor or single engine aircraft prop (clouds and tops of buildings). Might work better with a twin engine plane with clear sky.
Again, everyone’s systems, settings, and preferences are different so you just need to find out what works best for you imho. Cheers.
I installed Oculus app and was able to configure everything according to the settings as you described. Instrument related text on the dashboard is softer than with TAA but still readable. However the PC seems to be much less loaded and there is less heat coming out of the fans. This is for me already a big win. So i switched from VD to Oculus + Cable…
One thing is unfortunate: the Pixels density setting needs to be re-inserted in ODT after PC startup as ODT looses that particular setting after shutdown.
Ya, that’s why I use the free app Oculus Tray Tool (OTT) and setup game profiles to set super sampling and asw modes. Also, very easy to set/change Link/Air Link bitrates on the fly as well. I’ve been using OTT for +5yrs starting with a Rift cv1 and have always found this to be a very handy addon. BTW, you cannot use OTT with Virtual Desktop because VD doesn’t include the official Oculus runtimes, just their hacked version of this. Glad you’re have a bit of a win with Link mate. Cheers.
Dlss and ss combo works well for better graphics with less performance hit. Have you tried higher numbers than 1.2? For me, 1.2 is yet insufficient and 1.5 or 1.6 could bring more clarity for both the cockpit and sceneries.
Yes I’ve tried higher SS values and I haven’t seen any significant improvements above 1.20. This is with my Q3/QPro device graphics settings at 80Hz refresh rate with res slider full right. I think that adding this extra SS increases the upscaling target for dlss. So, 1.20x plus my device graphics setting is already upscaling to about 3500x3500 resolution. You may also get a bit better improvement by installing the latest dlss driver into your msfs user folder. I’m currently using 3.7.20. Maybe google how to do this.
I can easily use up to 1.50 but this starts to increase latency (and the occasional micro stutters). Above 1.6 and I start to get some stability issues. In any case, it’s very easy to change this to see what works best for you. To change in on the fly you can ctr+tab to exit VR and change the ODT pixel density (then enter). Go back to VR and see how you go. Also, you can try dlss/quality ti see if this helps. I don’t notice any significant differences in clarity between quality or balance and balanced seems to run a bit smoother. Hope this helps mate. Cheers.
Ya, lots seem to find that works well. Personally I just do this manually by going to my Steam/steamapps/common/MicrosoftFlightSimulator folder and copy paste the newest version nvgx_dlss.dll file into it, renaming the current one nvgx_dlss.dllOLD beforehand. Whichever way you do this that’s easiest for you is great imho.
First of all I suggest you read the OTT manual that’s in the OTT program folder. This will help explain what OTT settings do (or don’t do). I mainly just use OTT to finetune SS and ASW modes, nothing else.
For me, I set the startup OTT settings all pretty well stock defaults except a few things;
Default SS = 0
Default ASW = off
The rest don’t seem to do anything or are not important. Just leave them at defaults (usually 0’s, off, or default).
Link tab
encoding bitrate = 0 for Air Link, 500 for Link (hit save button after changing this and it will automatically add this to ODT). Don’t use the preset top tab, leave it blank.
As I’ve said before, I use OTT game profiles to finetune SS and ASW modes. For msfs202 I use;
SS = 1.20
ASW mode = 45Hz forced (= 1/2 your refresh rate with asw = off)
Again, the rest of the setting don’t seem to do anything, leave them at defaults.
I also use a few other OTT features like audio switching but I’ll leave it up to you to experiment a bit with all of these. Hope this helps mate. Cheers.
Hi guys: I’m really glad to see you sharing on here, and my updates so far are here below.
The test result of the new cable（usb3.2-G2-20 Gbps） in QLINK App is 2.6G-3.2G that is so mystery~ where the 5Gbps of USB 3 bandwidth?
The Q3 performs with new cable just much like my DP240W (120cm) , that still doesn’t touch my goals.
I ordered a PD1.4 to Type-C video capture card (3 meters), hoping to improve the quality of my PCVR. (GPU to Q3), my solution is running out…
I did try various methods to test my WIFI6e setup (in VD or games), but I am not satisfied with the quality and performance.
After checking the new information on Google, the type-c input of Q3 and Q2 seems to same have a max limit of 2.5-2.6 bandwidth , not sure. I guess the max limit is a problem of the Quest hardwares. maybe Meta is not very interested in developing PCVR?
6.WiFi wireless bandwidth seems to require Mbps÷2=real performance
Wait my next update, (display port 1.4 to Type-C 3.1)
I try various way to test my WIFI6e setup (in VD or games)，that’s hard to detail descript,(English not my speech ~ forgive me) my new cable evolution is failed~
Wait my next update, (display port 1.4 to Type-C 3.1)
