Jump to content

Recommended Posts

Posted (edited)

Any other virtual desktop users getting a wicked micro-stutter since the last DCS update? I’ve always been very pleased with the “smooth” experience provided by virtual desktop, but man, it’s really stuttery at the moment.

I don’t seem to get the same problem with the link cable right now. 

I’m using a Quest 3 with the latest nvidia drivers. I also tried rolling the drivers back to 552.44 to no avail. 

Has anyone tried rolling DCS back to 2.9.5? Did that work?


System specs: Ryzen 7950x, 4090, 64G DDR5

Edited by davidrbarnette
  • 5 months later...
Posted

I know this is an old post, but did either of you figure out a solution to this? Tried Virtual Desktop today for the first time in a while and the judder was pretty bad... I don't get that with the link cable. It's a rock solid 72 fps (Quest 3), but if I roll the jet or move my head quickly there is like a weird micro-stutter.

Posted

following, i have it  as well as same issue here just switching over to VD smooth and gorgeous other than one intermittent hang/stutter,  don't have it on the link cable...

I7 4770k @ 4.6, sli 980 evga oc edition, ssdx2, Sony 55 inch edid hack nvidia 3dvision. Volair sim pit, DK2 Oculus Rift.

Posted
12 hours ago, av8orDave said:

I know this is an old post, but did either of you figure out a solution to this? Tried Virtual Desktop today for the first time in a while and the judder was pretty bad... I don't get that with the link cable. It's a rock solid 72 fps (Quest 3), but if I roll the jet or move my head quickly there is like a weird micro-stutter.

What is your video encoding and Bitrate? It would be worth posting a screenshot of your in game overlay. Are you using reprojection?

  • Like 1

9800x3d - rtx5080 FE - 64Gb RAM 6000MHz - 2Tb NVME - Quest Pro (previous rift s and Pico 4). Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. BF-109 - FW-190 A8 - F4 - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

_A644840 (2).jpg

Posted
22 hours ago, av8orDave said:

I know this is an old post, but did either of you figure out a solution to this? Tried Virtual Desktop today for the first time in a while and the judder was pretty bad... I don't get that with the link cable. It's a rock solid 72 fps (Quest 3), but if I roll the jet or move my head quickly there is like a weird micro-stutter.

Check these:

- is your Quest updated to the V72 firmware?

- Do you have turbo mode enabled in OXRTK?

- Do you have enough performance headroom?

 

Posted
14 hours ago, Qcumber said:

What is your video encoding and Bitrate? It would be worth posting a screenshot of your in game overlay. Are you using reprojection?

I've tried with pretty much all of the encoders, at least H264+, HEVC10 Bit, AV1. I've tried running at bitrates as low as 100 with all. My in-game overlay shows a solid 72 fps, latency around 40, and a solid network connection with low network latency (I'm on a dedicated 6G router, 2400bps).

3 hours ago, ischicopter said:

Check these:

- is your Quest updated to the V72 firmware?

- Do you have turbo mode enabled in OXRTK?

- Do you have enough performance headroom?

 

Yes, I'm on the V72 firmware. I don't use OpenXR Toolkit (it is antiquated and no longer necessary, no?). I get great performance with the link cable, but get a wild micro-stutter with Virtual Desktop. System is a Ryzen 9 7950X, 4090, 64G DDR4.

Posted
8 hours ago, av8orDave said:

solid network connection with low network latency (I'm on a dedicated 6G router, 2400bps)

Is there anything else using the network channel? One trick is to make a Faraday cage from foil and screen out everything other than direct line to your headset. 

I have recently been using an ethernet link to the headset which requires an Android edit but gives me a very stable connection at 400mbps. Not sure if that is possible for the Q3. 

If you have not already done so it might be worth asking for help on the VD Discord channel. 

9800x3d - rtx5080 FE - 64Gb RAM 6000MHz - 2Tb NVME - Quest Pro (previous rift s and Pico 4). Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. BF-109 - FW-190 A8 - F4 - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

_A644840 (2).jpg

Posted (edited)
9 hours ago, av8orDave said:

I've tried with pretty much all of the encoders, at least H264+, HEVC10 Bit, AV1. I've tried running at bitrates as low as 100 with all. My in-game overlay shows a solid 72 fps, latency around 40, and a solid network connection with low network latency (I'm on a dedicated 6G router, 2400bps).

Yes, I'm on the V72 firmware. I don't use OpenXR Toolkit (it is antiquated and no longer necessary, no?). I get great performance with the link cable, but get a wild micro-stutter with Virtual Desktop. System is a Ryzen 9 7950X, 4090, 64G DDR4.

Give OXRTK a try and enable Turbo mode. I get stutters when I have it in OFF, despite the most vanilla DCS install and lowest possible graphics settings. It´s a DCS / Virtual Desktop thing. Make sure you have VDXR enabled in the VD streamer!

With Turbo ON I get smooth 80fps with reprojection on the Godlike preset (VD), an Medium (DCS) settings. And that´s on a RTX2070!

 

If that didn´t help it´s likely a network issue. Fix your setup or do this for guaranteed success: https://communityforums.atmeta.com/t5/Get-Help/Virtual-Desktop-with-cable-connection/td-p/1163316

I´ve been using it for a couple months pre V72 when Meta broke the Quest 3´s Wifi 

Edited by ischicopter
  • Like 1
  • 4 months later...
Posted

Any fix to this? I just switched from OTT to VD and man. It’s been something. Thought I had it set up good, runs great and has beautiful performance. Then maybe after about 5-10 minutes of flying I get a terrible stutter/buffer that interrupts audio as well every 10 seconds consistently (I timed it and it drove me insane). I switch back to wired and I can fly all day with zero issues. Granted it doesn’t look as good but it works. 

I've tried switching codecs etc.. and no luck. I have an intel i9-9900k, RX 9070xt, DCS on an NVME 2.0 and 64gb ram. Not sure what else to do. At least for VD. Any pointers?

Posted
4 hours ago, Mav said:

Any fix to this? I just switched from OTT to VD and man. It’s been something. Thought I had it set up good, runs great and has beautiful performance. Then maybe after about 5-10 minutes of flying I get a terrible stutter/buffer that interrupts audio as well every 10 seconds consistently (I timed it and it drove me insane). I switch back to wired and I can fly all day with zero issues. Granted it doesn’t look as good but it works. 

I've tried switching codecs etc.. and no luck. I have an intel i9-9900k, RX 9070xt, DCS on an NVME 2.0 and 64gb ram. Not sure what else to do. At least for VD. Any pointers?

It might be some external electromagnetic interference. Look for sources nearby that might interfere. Keep the router away from your PC and monitor. You could also try using foil coated panels or a box around the router as a Faraday cage (with a gap so you have line of sight to the headset). Another option is using a usb-ethernet link instead of WiFi. 

9800x3d - rtx5080 FE - 64Gb RAM 6000MHz - 2Tb NVME - Quest Pro (previous rift s and Pico 4). Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. BF-109 - FW-190 A8 - F4 - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

_A644840 (2).jpg

Posted
7 hours ago, Qcumber said:

It might be some external electromagnetic interference. Look for sources nearby that might interfere. Keep the router away from your PC and monitor. You could also try using foil coated panels or a box around the router as a Faraday cage (with a gap so you have line of sight to the headset). Another option is using a usb-ethernet link instead of WiFi. 

As in a usb to Ethernet adapter? Just curious, what does that offer differently that hard wiring straight into the motherboard Ethernet slot doesn’t? Thank you!

Posted (edited)
2 hours ago, Mav said:

As in a usb to Ethernet adapter? Just curious, what does that offer differently that hard wiring straight into the motherboard Ethernet slot doesn’t? Thank you!

Sorry. I meant using an ethernet cable to link directly to the headset. I think the Q3 supports this natively but the QP needs an android tweak to enable it. You connect the Ethernet cable to the headset via a USB adapter then to the router. Then connect the router to the PC with another Ethernet cable. This bypasses the need for WiFi and gives you a more stable signal. 

 

 

Edited by Qcumber

9800x3d - rtx5080 FE - 64Gb RAM 6000MHz - 2Tb NVME - Quest Pro (previous rift s and Pico 4). Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. BF-109 - FW-190 A8 - F4 - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

_A644840 (2).jpg

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...