Virtual Desktop - is it really a must?

[Qcumber]

1 hour ago, nachinus said:

It turns out ASW was already disabled in the Debug Tool, but it seems that ODT settings are being ignored, they just don't work. I had already noticed that the Pixel Override didn't work because I could only notice better resolution when increasing the Quest Link slider, but I just tried to lower FOV multipier all the way to 50;50 and didn't notice any change. It seems pretty obvious that the tool isn't working. I don't know if I missed something, any previous step that I should've done to make the Debug Tool work.

You will need to restart DCS after each change. 

Another option is Oculus Tray Tool. It accesses all the same settings as ODT but you can use it from your desktop so its a bit easier. 

https://www.guru3d.com/download/oculus-traytool-download/

 

[nachinus]

hace 3 horas, Qcumber dijo:

You will need to restart DCS after each change. 

Another option is Oculus Tray Tool. It accesses all the same settings as ODT but you can use it from your desktop so its a bit easier. 

https://www.guru3d.com/download/oculus-traytool-download/

 

Yes, I restart DCS and the Meta Quest Link Service after each change. I don't know why it isn't doing anything. I'll try to reinstall everything and see what happens.

[Qcumber]

1 hour ago, nachinus said:

Yes, I restart DCS and the Meta Quest Link Service after each change. I don't know why it isn't doing anything. I'll try to reinstall everything and see what happens.

Try OTT

[KLXTwn]

I am also a huge fan of VD until this happened ;

 

A few months back I build a new computer just for DCS :

9800X3D

4080 SUPER

64Gb RAM 6400

4Tb SSD 990PRO

MSI X870 Tomahawk

1250 MAG PSU

Quest 3

Windows 11; stripped down, fully debloated, no Defender, no Edge and no updating.

 

All this running via VD at 80FPS native ( no SSW ), 200Mbps bit rate, Godlike

and the experience was beautiful. DCS 80 FPS in the green, GPU bound.

Super smooth flight with incredibly crisp and clear image, never got any stuttering.

 

Come end of March I noticed when getting into DCS there was random “ static / cracking noise “

from launching into the main screen all the way into flights.

Each time there is this “ noise spike “ it comes with a stuttering, like a frame freeze and they

seem to be matched one noise means one frame stutter. Over these few days it has become

worse exponentially, now the noise keeps cracking and the image is one big stutter rendering

the whole sim impossible to play. 

Nothing looks wrong with the frames, even during the stutters the frame rate stays a stable 80Fps !

 

Nothing comes to mind what could have changed to either hardware or software, every piece

is still exactly the same. Nothing has been updated, added or removed.

 

Getting a bit frustrated hunting down the cause, checked all the hardware. Running tests without

any USB controllers connected, VD tuned down to a potato, lowered all settings, tried all Codec

and fps combinations ... the cracking and stutters are still there ...

 

Finished a clean install of windows and DCS ... and ... still cracking and stuttering ... so frustrating !

 

Out of ideas I tried the USB-Link but it just is no good, image just looks bad and

whenever looking closely down to the ground in flight there are ever so small stutters breaking

any immersion. Which was why I basically turned to VD two years ago.

 

Any ideas or maybe you experienced the same “ magic “ ?

[nachinus]

En 8/4/2025 a las 21:35, Qcumber dijo:

Try OTT

Now THAT worked!! It was a big improvement, thanks! Right now I'm playing with FOV multipliers to squeeze a little bit of extra smoothness.

[gdx65]

On 4/9/2025 at 3:26 PM, KLXTwn said:

I am also a huge fan of VD until this happened ;

 

A few months back I build a new computer just for DCS :

9800X3D

4080 SUPER

64Gb RAM 6400

4Tb SSD 990PRO

MSI X870 Tomahawk

1250 MAG PSU

Quest 3

Windows 11; stripped down, fully debloated, no Defender, no Edge and no updating.

 

All this running via VD at 80FPS native ( no SSW ), 200Mbps bit rate, Godlike

and the experience was beautiful. DCS 80 FPS in the green, GPU bound.

Super smooth flight with incredibly crisp and clear image, never got any stuttering.

 

Come end of March I noticed when getting into DCS there was random “ static / cracking noise “

from launching into the main screen all the way into flights.

Each time there is this “ noise spike “ it comes with a stuttering, like a frame freeze and they

seem to be matched one noise means one frame stutter. Over these few days it has become

worse exponentially, now the noise keeps cracking and the image is one big stutter rendering

the whole sim impossible to play. 

Nothing looks wrong with the frames, even during the stutters the frame rate stays a stable 80Fps !

 

Nothing comes to mind what could have changed to either hardware or software, every piece

is still exactly the same. Nothing has been updated, added or removed.

 

Getting a bit frustrated hunting down the cause, checked all the hardware. Running tests without

any USB controllers connected, VD tuned down to a potato, lowered all settings, tried all Codec

and fps combinations ... the cracking and stutters are still there ...

 

Finished a clean install of windows and DCS ... and ... still cracking and stuttering ... so frustrating !

 

Out of ideas I tried the USB-Link but it just is no good, image just looks bad and

whenever looking closely down to the ground in flight there are ever so small stutters breaking

any immersion. Which was why I basically turned to VD two years ago.

 

Any ideas or maybe you experienced the same “ magic “ ?

Same happened to me end of March. Meta Quest 3. Talking to meta support was useless as they always send you the same check list to do. Then last week doing trial and errors I solved the problem.

In the Meta Debug tool I had the bitrate set to 500. When I set it to zero then everything is working fine.

Has something changed in with some later upgrades?

 

Now I run the ASUS drivers with default

settings and meta Debug tool. Nothing else. I have the OpenXr disabled, I used it with my previous GPU RTX 4070 Dual OC

 

For reference my PC has a Ryzen 7 7800X3D, 64GD RAM DDR6000 2 X 2TB SSD Crucial and Nvidia RTX4090FE

[Qcumber]

3 minutes ago, gdx65 said:

In the Meta Debug tool I had the bitrate set to 500. When I set it to zero then everything is working fine.

Are you using link cable? If so then the max bitrate is 960 mbps. Try increasing to this and see if it works OK on your system. I think setting to 0 is default but I can't remember what that is. 

4 minutes ago, gdx65 said:

I have the OpenXr disabled

I presume that you mean Open XR Toolkit? Open XR is the API through which DCS and the Meta app communicate.  

[KLXTwn]

On 4/12/2025 at 8:03 PM, gdx65 said:

Same happened to me end of March. Meta Quest 3. Talking to meta support was useless as they always send you the same check list to do. Then last week doing trial and errors I solved the problem.

In the Meta Debug tool I had the bitrate set to 500. When I set it to zero then everything is working fine.

Has something changed in with some later upgrades?

 

Now I run the ASUS drivers with default

settings and meta Debug tool. Nothing else. I have the OpenXr disabled, I used it with my previous GPU RTX 4070 Dual OC

 

For reference my PC has a Ryzen 7 7800X3D, 64GD RAM DDR6000 2 X 2TB SSD Crucial and Nvidia RTX4090FE

I found the problem and have the solution ;

Problem : the access point that the Quest3 was connecting to was unable the keep the bitrate high enough, it was at 5GHz with too many other clients randomly connecting

Solution : now using a dedicated 6GHz access point with only the Quest3 and DCS computer connected to and all is smooth as butter 

[gdx65]

On 5/14/2025 at 3:49 PM, KLXTwn said:

I found the problem and have the solution ;

Problem : the access point that the Quest3 was connecting to was unable the keep the bitrate high enough, it was at 5GHz with too many other clients randomly connecting

Solution : now using a dedicated 6GHz access point with only the Quest3 and DCS computer connected to and all is smooth as butter 

I read similar solutions in other forms, if one uses WiFi best to have a dedicated WiFi access point. I only use the wired solution via USB, the cable does not bother me. Got a new USB powered cable and works great now. In the meantime I have upgraded my GPU to an RTX4090 found second hand and works great. 

Edited May 16 by gdx65

[Qcumber]

I am getting very good results with VD since the last update. Very smooth and sharp. Good latencies. But I have noticed a slightly annoying moire. It's not always noticeable, only really when my eyes are close-focussed on a very flat, dark background such as the sea. Has anyone seen this? 

I am using an Ethernet to USB connection rather than WiFi. 

[DD_Crash]

If it means not buying a router, can I use this instead?

https://www.amazon.co.uk/Ethernet-Adapter-Gigabit-Network-1000Mbps-Gray/dp/B0C7Z9FHJN/ref=sr_1_2_sspa?crid=3LKWKG5KQFWBO&dib=eyJ2IjoiMSJ9.flP7eut-xH1BMFFeV0vScpFyNPEOftHnqD7oKVXagQMzwWrV4DMBE6b9tGeSIbyQ-BxoNLH2ttiO6a-tXYutrUcwXxMbhOJmKvUvuywcFGZ0q3fZ0echs-fJ4u4G__f0xEHtQi0TkiL_4zfsHJ8oE9Lz3n4ePXm1Silj1TVeAhlSNiQS_XXmza2W_ZiNv3LlsFd0aYOPs5CYGSb2x3FDZz8uCctkplB1uS65eGnK3N0.19t2-5D1BYr2LIn3PrBEBe9hDuBUcuniKz1KXxWQBeQ&dib_tag=se&keywords=ethernet%2Bto%2Busb&qid=1747488742&sprefix=ethernet%2Bto%2Busb%2Caps%2C97&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&th=1

Is it hard to set up?

[KLXTwn]

On 5/17/2025 at 3:38 AM, Qcumber said:

I am getting very good results with VD since the last update. Very smooth and sharp. Good latencies. But I have noticed a slightly annoying moire. It's not always noticeable, only really when my eyes are close-focussed on a very flat, dark background such as the sea. Has anyone seen this? 

I am using an Ethernet to USB connection rather than WiFi. 

I haven't noticed any moire and I fly a lot on the Syria map ( Cyprus ) at different times of the day from first to last light. Unless there are more conditions that need to be met to have the effect visible ?

I noticed in your footer you also fly the new Germany map, I don't want to hijack this thread but a few days ago I posted about something I noticed with this map. There are quite some views but no comments so I'm wondering maybe few people fly VR on Germany or the problem is only with me ( which I kind of doubt ). I'm curious if you have this mysterious effect, the post is here ; 

 

[Qcumber]

58 minutes ago, KLXTwn said:

I haven't noticed any moire and I fly a lot on the Syria map ( Cyprus ) at different times of the day from first to last light. Unless there are more conditions that need to be met to have the effect visible ?

I only really noticed it against certain backgrounds such as low over the sea and only when I use an ethernet-usb link to my headset. I wonder if it is cable interference. I will try a shielded ethernet cable to see if that helps.

1 hour ago, KLXTwn said:

I noticed in your footer you also fly the new Germany map, I don't want to hijack this thread but a few days ago I posted about something I noticed with this map. There are quite some views but no comments so I'm wondering maybe few people fly VR on Germ any or the problem is only with me ( which I kind of doubt ). I'm curious if you have this mysterious effect, the post is here

I have not noticed this but have not really flown on the map enough yet. 

[mrsylvestre]

On 5/17/2025 at 3:34 PM, DD_Crash said:

If it means not buying a router, can I use this instead?

(USB-Ethernet adapter link)

Is it hard to set up?

It is not hard at all to set up. You just plug the usb-c end in the VR headset and an ethernet cable from your router to the other end. I have a Pico 4 and there is no software setup of any sort required, the headset just appears on the network as if it was connected by wifi. I see no reason for it not be the same with the Quest 2 or 3. It is that simple, really. EDIT: Well, it is that simple, really... if you have a Pico 4 headset. On the Quests, it seems that Meta thought it was a good idea not to enable ethernet by default and you have to jump through a few hoops to get it running, see the instructions linked in the next post (thanks to Qcumber for pointing out that).

It is important to find the right USB-Ethernet dongle and cables for comfort. Prefer a dongle with an extra input for a power adapter, to which you can connect the charger for your headset so it is being charged while gaming. I also don't like to have the dongle hanging on the side of the headset (that is an accident waiting to happen for the fragile usb port), so I bought a 2 metres usb-c extension cable like this one, with an usb-c female connector at one end (to connect the dongle to) and an angled usb-c male connector at the other. The cable is secured to the side of the head strap so that if one pulls on it, the force is not applied to the headset port, and the dongle stays to my side, on my desk.

Edited May 18 by mrsylvestre

[Qcumber]

15 minutes ago, mrsylvestre said:

It is not hard at all to set up. You just plug the usb-c end in the VR headset and an ethernet cable from your router to the other end. I have a Pico 4 and there is no software setup of any sort required, the headset just appears on the network as if it was connected by wifi. I see no reason for it not be the same with the Quest 2 or 3. It is that simple, really.

It is important to find the right USB-Ethernet dongle and cables for comfort. Prefer a dongle with an extra input for a power adapter, to which you can connect the charger for your headset so it is being charged while gaming. I also don't like to have the dongle hanging on the side of the headset (that is an accident waiting to happen for the fragile usb port), so I bought a 2 metres usb-c extension cable like this one, with an usb-c female connector at one end (to connect the dongle to) and an angled usb-c male connector at the other. The cable is secured to the side of the head strap so that if one pulls on it, the force is not applied to the headset port, and the dongle stays to my side, on my desk.

I'm not sure if this works with the Q3. With the QP you need to make a change to the headset android settings before it will work. 

 

 

Edited May 18 by Qcumber