Quest Pro with Ethernet | How-to

[sleighzy]

8 hours ago, Simo said:

Even on the main menu (hangar) screen

You should use the no hanger mod from Rapierach to get rid of the hanger. It'll save you VRAM, the hanger is still present even in the F10 map.

[Simo]

8 minutes ago, sleighzy said:

You should use the no hanger mod from Rapierach to get rid of the hanger. It'll save you VRAM, the hanger is still present even in the F10 map.

Will give that a go, thanks. On a 4090, so not sure VRAM is the issue, but worth a try.

[nikoel]

You're not limiting your FPS in any way? I run mine with no cap. From memory you can set them in OpenXR Toolkit, Nvidaa Settings and within DCS itself

Also you may benefit from Turbo mode

[Panzerlang]

4 hours ago, Simo said:

Will give that a go, thanks. On a 4090, so not sure VRAM is the issue, but worth a try.

It's not, made not a jot of difference on my rig.

[Simo]

9 hours ago, nikoel said:

You're not limiting your FPS in any way? I run mine with no cap. From memory you can set them in OpenXR Toolkit, Nvidaa Settings and within DCS itself

Also you may benefit from Turbo mode

No, checked FPS limit is off in NVCP, OXRTK and DCS settings. Tried capping in and uncapping in all three, but makes no difference.

Am using Turbo mode though - this is the only way I can get smooth frame times on Link, but it seems less effective on VD (but still better than with TM off).

Looking at the performance overlay in VD there is some slight fluctuation in network latency, so am wondering if that's the cause.

 

Edited January 24 by Simo

[nikoel]

9 hours ago, Simo said:

No, checked FPS limit is off in NVCP, OXRTK and DCS settings. Tried capping in and uncapping in all three, but makes no difference.

Am using Turbo mode though - this is the only way I can get smooth frame times on Link, but it seems less effective on VD (but still better than with TM off).

Looking at the performance overlay in VD there is some slight fluctuation in network latency, so am wondering if that's the cause.

 

There is a recommendation from Virtual Desktop to use a specific version of Nvidia Drivers. I can not recall what they are, but it's plastered all over their Discord. Maybe try them and see if you're affected

[Qcumber]

On 12/29/2024 at 3:38 AM, nikoel said:

What is this?

A guide on how to connect your quest pro to your router via ethernet instead of WiFi for use with Virtual Desktop

Why do I want this?

Depending on your router, location, speed etc... a cable connection can result in fewer artifacts, an ability to push higher bandwidth, a more stable connection with fewer micro stutters and tears and much faster eye tracking. The user may have more money to spend on DCS modules as they no longer need to purchase a WiFi 6/e router

(I have a WiFi 6e Router - for me no improvements in bandwidth and overall image quality - but I have fewer artifacts, rock solid frame stability and much faster eye tracking)

What do I need?

• A Quest Pro
• Data USB Cable to connect the Quest Pro to your Computer
• A fast Ethernet cable from your computer to the router, an equally fast Ethernet cable from your router to your Quest Pro
• A Router with DHCP
• A Ethernet to USB-C adapter - I used https://www.unitek-products.com/products/usb-c-to-gigabit-ethernet-5gbps-aluminium-adapter
• Virtual Desktop
• Recommended: A high quality USB-C Female/Male *data* extension cable so you can leave the ethernet adapter on the desk and just run one cable to the headset

Guide

In short, Meta have disabled ethernet by default. To enable it you need to input a command into your headset via something that is called ADB (Android Debug Bridge). To do this you are required to have Developer Mode turned on and the headset connected to your computer to input this command

Disconnect QuestPro from computer

Put your headset into developer mode (inside the phone app and headset settings). It's actually very simple. Screenshot flow on how to do this is here: https://help.arborxr.com/en/articles/6333136-developer-mode-on-meta-quest-devices

Plug the headset into your computer via any *DATA* USB cable.

Next, put the headset over your head and inside the headset allow the incoming connection (a Virtual Reality popup will appear as soon as the USB connection is being made)

Install Android Studio

Navigate to the folder ADB is installed. For me it was in Users/~Username~/AppData/Local/Android/Sdk/platform-tools. AppData folder may be hidden - make sure to view hidden folders in explorer

Right click anywhere inside the folder (but not on any of the files) - Open in Terminal

 

Then run the following command to double check that everything is good to go

.\adb devices

Your quest pro should come up as some bunch of numbers and characters. It should tell you if it's authorised (aka if you performed the above steps correctly)

Then run the following command

.\adb shell setprop debug.usb.ethernet.enabled 1

Disconnect your quest pro USB cable. Plug in ethernet adapter. Into the ethernet adapter connect PD power source and ethernet cable. Connect the other end of the ethernet cable to the router. (If you, like me forgot to order your USB extension cable, your quest pro should now look like this):

Inside your headset settings turn off wifi. If you still have interwebs then she is working gud. The ethernet lights should also be flashing

Documentation on ADB within Meta ecosystem: https://developers.meta.com/horizon/documentation/native/android/ts-adb/

Closing Concerns

This is not officially supported by Virtual Desktop. I believe this is because Meta could theoretically remove this feature at any time, leaving us at their mercy if they decide to alter the code or delete the feature. (I’ve disabled updates until other guinea pigs update their headsets first and confirm it’s safe.) Nonetheless, it’s not really a risk, since Meta seems hell-bent on bricking everyone’s devices with updates regardless of which features are installed.

Frequent User Errors

• Not using a data delivery USB cable (i.e. the default cable used for charging only)
• Only enabling the developer mode inside the headset or inside the iPhone/Android App. Both are required
• Not putting on the headset and accepting the connection inside VR when connecting QuestPro to PC
• Not providing power to the ethernet adapter
• Plugging the ethernet cable directly from computer to the headset. Need a router with DHCP

How do you disable this? With this line? "debug.usb.ethernet.disabled 0"?

[nikoel]

2 minutes ago, Qcumber said:

How do you disable this? With this line? "debug.usb.ethernet.disabled 0"?

adb shell setprop debug.usb.ethernet.enabled 0

Reboot. Then run the following:

adb shell getprop debug.usb.ethernet.enabled

It should return a 0 or N/A etc... to tell you that it's off

P.S. I just saw your eye tracking thread. I am sorry to see it. I have seen a thread months ago where a gentleman had a similar issue, one of the comments said that the condensation from sweat etc... got into the eye tracking circuit and wrecked havoc. One way to check is to take a photo and you should see the Quest Pro eye tracking stack light up. I hope it's just software related

[Qcumber]

2 minutes ago, nikoel said:

One way to check is to take a photo and you should see the Quest Pro eye tracking stack light up. I hope it's just software related

Thanks. I'll give that a go.

[nikoel]

<profanity> photo. But you get the idea

[Qcumber]

My lights are showing so it must be software. 

26 minutes ago, nikoel said:

<profanity> photo. But you get the idea

What version of meta os are you using?  

[nikoel]

16 minutes ago, Qcumber said:

My lights are showing so it must be software. 

What version of meta os are you using?  

Version 71. I do have Meta asking me to update. But so far I have not

[Qcumber]

1 minute ago, nikoel said:

Version 71. I do have Meta asking me to update. But so far I have not

I would hold off. I have now managed to set up face tracking. There is an issue with getting the position if the headset right. I'll keep persevering with eye tracking. 

[nikoel]

1 minute ago, Qcumber said:

I would hold off. I have now managed to set up face tracking. There is an issue with getting the position if the headset right. I'll keep persevering with eye tracking. 

Thank you mate. I might take a page out of Ironmexxs book and disable updates via ADB to be extra safe. Glad it's a software bug and nothing to do with your hardware - did the ethernet mod cause the issue or was it just the update?

Edited January 26 by nikoel

[Qcumber]

35 minutes ago, nikoel said:

Thank you mate. I might take a page out of Ironmexxs book and disable updates via ADB to be extra safe. Glad it's a software bug and nothing to do with your hardware - did the ethernet mod cause the issue or was it just the update?

When I did the factory reset the mod is no longer working so I don't think it is that. 

[Qcumber]

Eye tracking is back on line! Solution is in the other thread. 

Unfortunately I am now having issues with ethernet connection. I have activated the settings as per this thread but can now only manage about 130 Mbps when I had 400 Mbps only two days ago. 

[Qcumber]

Any idea how to stop the "useful" reminders that the handsets may not track very well without WiFi?

[Qcumber]

After having to do a factory reset I have redone the steps to activate ethernet. Nothing has changed in terms of hardware but I am now limited to 140Mbps rather than the 400 I had previously. WiFi is off. I have accessed the browser from the headset so can con firm I can access the internet. Any ideas?

[nikoel]

On 2/2/2025 at 10:05 PM, Qcumber said:

After having to do a factory reset I have redone the steps to activate ethernet. Nothing has changed in terms of hardware but I am now limited to 140Mbps rather than the 400 I had previously. WiFi is off. I have accessed the browser from the headset so can con firm I can access the internet. Any ideas?

Well crap. I've tried the 2x supersample with ASW with Link from the thread next door and now I have the same thing. It's obviously network related, but I literally changed nothing

Have you figured it out?

[Qcumber]

1 minute ago, nikoel said:

Well crap. I've tried the 2x supersample with ASW with Link from the thread next door and now I have the same thing. It's obviously network related, but I literally changed nothing

Have you figured it out?

No. It's bloody annoying. Curiously the limit is 140Mbps which is my network speed. Maybe a router setting!? 

[VR Flight Guy in PJ Pants]

Newcomer here, so I have a small router intended for WiFi connect with QPro over VD. If I go with the Ethernet route, so the router connection originally the internet now goes to QPro, while the other connection from the router to PC remains then. Am I correct?

[nikoel]

3 minutes ago, VR Flight Guy in PJ Pants said:

Newcomer here, so I have a small router intended for WiFi connect with QPro over VD. If I go with the Ethernet route, so the router connection originally the internet now goes to QPro, while the other connection from the router to PC remains then. Am I correct?

Basically nothing really changes; you want to run ethernet cable from whichever router you connected via WiFi with Virtual Desktop

What you want to avoid is double NAT, or connecting to the upstream router which will then send signal to the downstream router which will then send the signal to the PC. The fewer links between your PC to the headset the better

[VR Flight Guy in PJ Pants]

Thanks, the problem is, the router only has 2 ports, one to the WAN/internet and the other to the PC, so one has to go...

[diamond26]

Very strange as I'm moving between Link and VD all the time (especially now with testing for new DLSS) for 2 different computers and haven't seen this problem!

[nikoel]

35 minutes ago, VR Flight Guy in PJ Pants said:

Thanks, the problem is, the router only has 2 ports, one to the WAN/internet and the other to the PC, so one has to go...

yeah exactly, then it makes the middle one redundant