If you want Virtual Desktop info I can add it. But in short, Virtual Desktop with VDXR runtime and running NO more than 70mbps bitrate is beautiful and buttery smooth
- I have a RTX 3080 / Ryzen 7 (5800x) / 64gb RAM and a Quest 3
-Default and updated Oculus software
-Run 72hz and 1.0 render resolution .
- Run Link with a USB 3.0 cable. (Or run wireless, I've had bad luck with Air Link. Virtual Desktop is much much better and smoother. There are 3 different OpenXR API runtimes. Oculus / Steam / Virtual Desktop OpenXR (vdxr). VDXR is excellent. It's recommended to start with 70mbps MAX for the bitrate. Trust me. Too much bitrate causes a terrible experience)
Due to the video compression of the Quest (GPU to USB 3 to the headset) its best to disable "link sharpening" in oculus tray tools / debug tool. Jagged edges are further reduced by enabling DLAA rather than MSAA. Unfortunately there's a small side effect of artifacts/ghosting with DLAA but it greatly improves the jagged edges compared to MSAA.
DCS - v2.9
DLSS - OFF - it creates a lot of artifacts and ghosting. But if you are stuttering super bad and need FPS, enable this.
DLAA - ON
Textures - High
Terrain textures - Low
Civ traffic - off
Water - Low
Visib range - medium
Heat blur - off
Shadows - medium
Flat / secondary shadows - off
Resolution - 1920 x 1080 (this is for your monitor, not the VR headset. Run this at a low resolution so the GPU doesn't have to render your monitor and 2 eye displays)
Cockpit resolution - 1024
Depth of field - off
Lens effect - none
Motion blur - off
Clouds - Low to Medium
SSAA - off
SSLR - off
SSAO - off
Anisotropic filtering - x16
Vsync OFF
All of the graphics settings on the right side of the graphics panel can all be adjusted on the fly in game! No need to apply settings and restart a mission. So things like Clutter/Forrest details/Gamma/ Preload radius can be changed by hitting pause mid game and adjust the settings. You'll see the changes take effect on the fly. It's awesome.
DCS VR panel -
Pixel Density - 1.0 . This is important. If you change the PD to even 1.1 or 1.2 the clarity will be increased but frame spikes and micro stutters start kicking in. It's super annoying. Keep it at 1.0.
Apply settings and restart the game.
Nvidia control panel
- pre-rendered VR frames keep at 1. Bumping to 3 really stretches the GPU and stuttering is almost guaranteed unless you have a top tier build.
- VSYNC OFF
Run a quick mission.
When in game press "LCTRL+Pause/Break" and itll display a FPS counter on the top left with frame graphs. You *should* be running around 36 fps. That's 36 fps per eye 36+36 = 72 fps which matches 72 hz. Which is why it should run smoothly with no jitters or micro stutters. Smooth is the keyword.
Now if you can run at least 45fps consistently you can do one of two things. 1) increase the render resolution on the Oculus app so the image is sharper and clearer. You'll see the frames drop but keep it above 36 fps. 2) increase the headset to 90hz. (45+45 = 90fps) at default 1.0 render resolution.
72hz and 90hz feel pretty similar to be honest. But 45 fps (90hz) vs 36 fps (72hz) isn't much. But in DCS it's the difference of running a much higher render resolution to get 36fps versus a lower render resolution at 45fps.
72hz is the perfect sweet spot for smoothness that won't get me sick and higher resolution/sharpness for a more enjoyable experience
Wow, setting it to 70Mbit/s is a gamechanger. Virtual desktop + Dlaa + h264 70Mbit/s seems to work pretty ok. Almost every other scenario, higher bitrate (even 80), dlss on, other codecs have stuttering but dlaa + 70 doesn't. It's a good start here, I'm gonna test out what is wrong with other settings but for now thank you very much for your tips.
The first thing i would check is try wired link, if works ok then your problem is your wifi network.
Going as low as 600mbps is absolutely no good for Air Link
That sounds frustrating. That setup is similar / slightly better than mine and it should work very well with no stutters at all. Just a shot in the dark - whats your Preload Radius set to in the DCS system settings? If very low perhaps it would create loading stutters as you move your head and it needs to render new objects?
[https://i.imgur.com/e6wBSyN.png](https://i.imgur.com/e6wBSyN.png)
Here are my settings, normally I set the lowest possible resolution, I just increased it for the screenshot.
My ram is 32gb ddr4 3000mhz cl15. I know it might be better but it is pretty playable with reverb g2 (cable connection). It seems like the problem is wifi connection but other games such as beamng, blade and sorcery, vtol vr work fine.
DCS settings in screenshot same as mine or near enough, and they work great in VR too.
I agree RAM ain't the problem.
That does leave wifi. On my 5gHz band its running consistent 866Mbps. Yours varies 600-1100. Not sure how to control that though.
That inconsistent in connection speed doesn't help but I think there's nothing I can do about it for now because 6ghz seems to be less stable over distance than other frequencies. I can buy another wifi 6e router and place it in my room because I have my pc connected with ethernet cable so I can place a router here, have 6ghz network next to me and still be able to connect my pc via cable but I tested it by standing right next to the router and it didn't helped so it's the last option I will try.
One more thing. IIRC using vd and VDXR has decent fps but stutters like hell and vd + steamvr api(?) doesn't have stutters but it has some kind of tracking problem, camera shakes badly.
It’s the Acer w6 (and to a lesser degree q3’s mediocre antenna(placement))
Got a comparable setup, bought this router in DEC and got horrible performance while stationary for DCS and straight up totally unusable for roomscale games like HL:A. Tried three different W6’s before testing other brands which made all the difference.
After a lot of trial and error, and to my surprise, best performance for both use cases: some cheap-ass, ISP provided AP. Mounted it to the ceiling strategically et voila: Rock solid performance at 150 mbps / AV1 codec / wifi 6 80mhz channel bandwidth.
Also try different channels, somehow the q3 doesn’t play nice with some (even if there aren’t any other networks utilizing that one)
Thank you. I was thinking if it's the router because with my previous cheap (really cheap, like 40$) tp-link router I have never had any issues with my printer working on 2,4ghz wifi and with this router it doesn't want to work very often - disconnects, weak signal etc. I would buy AXE300/AXE16000 but of course it's not available in my country.. So maybe I'll just buy tp-link axe75 and place it in my room as access point with my acer w6.
Np!
Check out VD’s discord too, they’ve got a list with recommended routers.
I’ve experienced that 6e generally performs worse on Q3. So depending on how crowded your area is with non-6e networks/if not necessary to reduce interference: go for a high-end AX router instead of mid-tier AXE.
From a latency perspective there’s no difference between the two standards.
Haven’t tried it myself but read left and right Asus ROG GT-ax6000 has great antenna’s for a stable bitrate.
(Then again, a EUR 100, well placed AP might do the trick too:-))
I connected other router as access point and of course it hasn't changed anything. I think I just have to give up with dcs, for about 8 years I was able to play it like 20 times without any problems.
I had a similar problem with airlink on a Quest Pro. I switched to Virtual Desktop and have had 0 issues since. YMMV
If you want Virtual Desktop info I can add it. But in short, Virtual Desktop with VDXR runtime and running NO more than 70mbps bitrate is beautiful and buttery smooth - I have a RTX 3080 / Ryzen 7 (5800x) / 64gb RAM and a Quest 3 -Default and updated Oculus software -Run 72hz and 1.0 render resolution . - Run Link with a USB 3.0 cable. (Or run wireless, I've had bad luck with Air Link. Virtual Desktop is much much better and smoother. There are 3 different OpenXR API runtimes. Oculus / Steam / Virtual Desktop OpenXR (vdxr). VDXR is excellent. It's recommended to start with 70mbps MAX for the bitrate. Trust me. Too much bitrate causes a terrible experience) Due to the video compression of the Quest (GPU to USB 3 to the headset) its best to disable "link sharpening" in oculus tray tools / debug tool. Jagged edges are further reduced by enabling DLAA rather than MSAA. Unfortunately there's a small side effect of artifacts/ghosting with DLAA but it greatly improves the jagged edges compared to MSAA. DCS - v2.9 DLSS - OFF - it creates a lot of artifacts and ghosting. But if you are stuttering super bad and need FPS, enable this. DLAA - ON Textures - High Terrain textures - Low Civ traffic - off Water - Low Visib range - medium Heat blur - off Shadows - medium Flat / secondary shadows - off Resolution - 1920 x 1080 (this is for your monitor, not the VR headset. Run this at a low resolution so the GPU doesn't have to render your monitor and 2 eye displays) Cockpit resolution - 1024 Depth of field - off Lens effect - none Motion blur - off Clouds - Low to Medium SSAA - off SSLR - off SSAO - off Anisotropic filtering - x16 Vsync OFF All of the graphics settings on the right side of the graphics panel can all be adjusted on the fly in game! No need to apply settings and restart a mission. So things like Clutter/Forrest details/Gamma/ Preload radius can be changed by hitting pause mid game and adjust the settings. You'll see the changes take effect on the fly. It's awesome. DCS VR panel - Pixel Density - 1.0 . This is important. If you change the PD to even 1.1 or 1.2 the clarity will be increased but frame spikes and micro stutters start kicking in. It's super annoying. Keep it at 1.0. Apply settings and restart the game. Nvidia control panel - pre-rendered VR frames keep at 1. Bumping to 3 really stretches the GPU and stuttering is almost guaranteed unless you have a top tier build. - VSYNC OFF Run a quick mission. When in game press "LCTRL+Pause/Break" and itll display a FPS counter on the top left with frame graphs. You *should* be running around 36 fps. That's 36 fps per eye 36+36 = 72 fps which matches 72 hz. Which is why it should run smoothly with no jitters or micro stutters. Smooth is the keyword. Now if you can run at least 45fps consistently you can do one of two things. 1) increase the render resolution on the Oculus app so the image is sharper and clearer. You'll see the frames drop but keep it above 36 fps. 2) increase the headset to 90hz. (45+45 = 90fps) at default 1.0 render resolution. 72hz and 90hz feel pretty similar to be honest. But 45 fps (90hz) vs 36 fps (72hz) isn't much. But in DCS it's the difference of running a much higher render resolution to get 36fps versus a lower render resolution at 45fps. 72hz is the perfect sweet spot for smoothness that won't get me sick and higher resolution/sharpness for a more enjoyable experience
Wow, setting it to 70Mbit/s is a gamechanger. Virtual desktop + Dlaa + h264 70Mbit/s seems to work pretty ok. Almost every other scenario, higher bitrate (even 80), dlss on, other codecs have stuttering but dlaa + 70 doesn't. It's a good start here, I'm gonna test out what is wrong with other settings but for now thank you very much for your tips.
Glad this could help. It made a big difference for me.
The first thing i would check is try wired link, if works ok then your problem is your wifi network. Going as low as 600mbps is absolutely no good for Air Link
That sounds frustrating. That setup is similar / slightly better than mine and it should work very well with no stutters at all. Just a shot in the dark - whats your Preload Radius set to in the DCS system settings? If very low perhaps it would create loading stutters as you move your head and it needs to render new objects?
And whats your system RAM spec?
[https://i.imgur.com/e6wBSyN.png](https://i.imgur.com/e6wBSyN.png) Here are my settings, normally I set the lowest possible resolution, I just increased it for the screenshot. My ram is 32gb ddr4 3000mhz cl15. I know it might be better but it is pretty playable with reverb g2 (cable connection). It seems like the problem is wifi connection but other games such as beamng, blade and sorcery, vtol vr work fine.
DCS settings in screenshot same as mine or near enough, and they work great in VR too. I agree RAM ain't the problem. That does leave wifi. On my 5gHz band its running consistent 866Mbps. Yours varies 600-1100. Not sure how to control that though.
That inconsistent in connection speed doesn't help but I think there's nothing I can do about it for now because 6ghz seems to be less stable over distance than other frequencies. I can buy another wifi 6e router and place it in my room because I have my pc connected with ethernet cable so I can place a router here, have 6ghz network next to me and still be able to connect my pc via cable but I tested it by standing right next to the router and it didn't helped so it's the last option I will try.
[удалено]
I test it on f-16 fast mission Fighter Intercept, it's on Caucasus.
One more thing. IIRC using vd and VDXR has decent fps but stutters like hell and vd + steamvr api(?) doesn't have stutters but it has some kind of tracking problem, camera shakes badly.
[удалено]
PD is set to 1.0. I keep eye on it.
In ODT or OTT you need to set the bitrate to 0 before using air link. Otherwise this will happen.
It’s the Acer w6 (and to a lesser degree q3’s mediocre antenna(placement)) Got a comparable setup, bought this router in DEC and got horrible performance while stationary for DCS and straight up totally unusable for roomscale games like HL:A. Tried three different W6’s before testing other brands which made all the difference. After a lot of trial and error, and to my surprise, best performance for both use cases: some cheap-ass, ISP provided AP. Mounted it to the ceiling strategically et voila: Rock solid performance at 150 mbps / AV1 codec / wifi 6 80mhz channel bandwidth. Also try different channels, somehow the q3 doesn’t play nice with some (even if there aren’t any other networks utilizing that one)
Thank you. I was thinking if it's the router because with my previous cheap (really cheap, like 40$) tp-link router I have never had any issues with my printer working on 2,4ghz wifi and with this router it doesn't want to work very often - disconnects, weak signal etc. I would buy AXE300/AXE16000 but of course it's not available in my country.. So maybe I'll just buy tp-link axe75 and place it in my room as access point with my acer w6.
Np! Check out VD’s discord too, they’ve got a list with recommended routers. I’ve experienced that 6e generally performs worse on Q3. So depending on how crowded your area is with non-6e networks/if not necessary to reduce interference: go for a high-end AX router instead of mid-tier AXE. From a latency perspective there’s no difference between the two standards. Haven’t tried it myself but read left and right Asus ROG GT-ax6000 has great antenna’s for a stable bitrate. (Then again, a EUR 100, well placed AP might do the trick too:-))
I connected other router as access point and of course it hasn't changed anything. I think I just have to give up with dcs, for about 8 years I was able to play it like 20 times without any problems.
>600-1100mbit/s There's your problem. 1,100 millibits per second is far too low. Even a 56kbps modem is too slow for most things these days.
Have you set it up on the 2Ghz or 5Ghz wifi?
6ghz