Virtual Desktop over Link cable (reverse tethering via gnirehtet)

[Jive]

I gave this a test the other day, I didn't spend a lot time with it. The TLDR is that with h264+ I was finding 150-200 to be the max bitrate before latency became an issue. I didn't try any other codecs. A reddit user suggested they often need to restart their PC between uses otherwise latency goes high. YMMV if you're interested enough to try.

Instructions are reasonably clear on https://github.com/Genymobile/gnirehtet I'm not technically inclined enough to offer any troubleshooting but others here may be able to.

Short version of the instructions
Download and isntall Java https://www.oracle.com/java/technologies/downloads/#jdk22-windows
Download gnirehtet (Java, not Rust) https://github.com/Genymobile/gnirehtet/releases/download/v2.5.1/gnirehtet-java-v2.5.1.zip
Download adb platform-tools and extract to your gnirehtet folder https://dl.google.com/android/repository/platform-tools-latest-windows.zip

Double click gnirehtet-run.cmd from your gnirehtet folder. It will open a cmd window on your PC and in the headset you'll see an option to allow a connection request. This is first time only. 

The cmd box from gnirehtet-run.cmd needs to be running, then you can open VirtualDesktop as you would normally (although I had my Quest wifi turned off).
The PC connection will say it isn't on the same network but it will still connect. 

Done

I expected network latency to read zero, it doesn't and it does change with the codec/bitrate. As above I found it to top out at 150ish before latency became an issue with h264+ so it's not super attractive to me at the moment but I thought it might be worth sharing in case anyone with different network circumstances finds it useful. 

 

[nikoel]

Thanks for the post

If you want VDXR over Link Cable, there is a standalone application that has been developed by the  himself

Limitation is that there is no Body/Eye Tracking and you need to use a OpenXR Picker to make sure you select the correct runtime

https://github.com/mbucchia/VirtualDesktop-OpenXR/releases

Edited August 5, 2024 by nikoel

[Qcumber]

2 hours ago, nikoel said:

Thanks for the post

If you want VDXR over Link Cable, there is a standalone application that has been developed by the  himself

Limitation is that there is no Body/Eye Tracking and you need to use a OpenXR Picker to make sure you select the correct runtime

https://github.com/mbucchia/VirtualDesktop-OpenXR/releases

 

I think it just allows using VDXR through oculus link. What the OP is referring to is using VD through a cable rather than wifi. 

[Gryzor]

On 8/5/2024 at 9:01 AM, Qcumber said:

I think it just allows using VDXR through oculus link. What the OP is referring to is using VD through a cable rather than wifi. 

How is the performance using VDXR through oculus link? its the same as VD over wifi? any testes?

[Qcumber]

7 hours ago, Gryzor said:

How is the performance using VDXR through oculus link? its the same as VD over wifi? any testes?

QVFR works very well with meta link cable. Performance is the same. Quality is almost identical, although there are subtle differences. Meta has a slight edge if you can push the bitrate over 500mbps. I can get mine up to the max of 960mbps. 

[Gryzor]

4 hours ago, Qcumber said:

QVFR works very well with meta link cable. Performance is the same. Quality is almost identical, although there are subtle differences. Meta has a slight edge if you can push the bitrate over 500mbps. I can get mine up to the max of 960mbps. 

Many Thanks. QVFR is enabled thorough VDXR Standalone 1.0.3? Is there any tutorial, what are you settings? OTT included. I tried OculusLink (alone) and the performance is not good in comparison with VD on Ultra (with oculus link is about -30% lower at equal resolution).

[actually_fred]

VDXR over link is primarily a development tool, not intended for actual use.

being able to switch between link and VD as the backend helps isolate problems: if a bug only exists with VDXR using VD, it’s likely a VD bug, if exists with both VD and link as the backend it’s probably a VDXR bug.

[Qcumber]

2 hours ago, Gryzor said:

I tried OculusLink (alone) and the performance is not good in comparison with VD on Ultra (with oculus link is about -30% lower at equal resolution).

You need to make sure your meta output resolution matches VD on godlike otherwise it's not a fair comparison. 

 

2 hours ago, Gryzor said:

QVFR is enabled thorough VDXR Standalone 1.0.3? Is there any tutorial, what are you settings?

QVFR works with meta open XR. You don't need VDXR. There is a setup guide on the QVFR website. 

[Gryzor]

1 hour ago, Qcumber said:

You need to make sure your meta output resolution matches VD on godlike otherwise it's not a fair comparison. 

 

QVFR works with meta open XR. You don't need VDXR. There is a setup guide on the QVFR website. 

I cannot find any exact video or guido how settings QVFR for Quest 3 and using Quest Link with DCS World. All guides for QVFR are for varjo or quest pro.

In addition, OpenXR Toolkit is necesary?

And what about using VDXR Standalone 1.0.3 under Quest link? Releases · mbucchia/VirtualDesktop-OpenXR (github.com) Any experience? what is the advantages? I cannot find any info...

Edited August 23, 2024 by Gryzor

[Phantom711]

vor 3 Stunden schrieb Gryzor:

All guides for QVFR are for varjo or quest pro.

You can follow the guide for the QuestPro and simply disregard anything that has to do with eye-tracking.

[Gryzor]

What are the benefits of using QVFR over openxr toolkit options, in terms of graphic performane? Openxr toolkit has options to make a peripheral fov with less detail. This is not the same as using QVFR??

Of course, I´m talking about Quest 3 which not have eye tracking.

[gonvise]

I don't know why, but I have better results with VRS foveated of toolkit. Even after update muy CPU to 7800x3D, the stutters free and fluidity of VRS is better in my case than QVFR. Perhaps is because I use a high resolution multiplier or ASW always enabled... Give It a try!

 

Edited August 23, 2024 by gonvise

[Jive]

On 8/23/2024 at 8:55 PM, Gryzor said:

What are the benefits of using QVFR over openxr toolkit options, in terms of graphic performane? Openxr toolkit has options to make a peripheral fov with less detail. This is not the same as using QVFR??

Of course, I´m talking about Quest 3 which not have eye tracking.

QVFR can offer you more control over your fixed foveated rendering on Q3. You can fully tweak which resolution multiplier you'd like in the outer area and also choose to super sample the inner area if you like. QVFR will however add some load to your CPU.

 

OXRTK has much less ability to customise to your liking but won't add the CPU load that QVFR does. 

[Qcumber]

If your CPU is half decent and you have a mid range GPU then QVFR is better. I did a quick comparison today. With QVFR the GPU load was about 70-80%. FPS steady at 72 fps. The same scenario with OXRTK foveated rendering the GPU load was about 85-100 with frequent flips to ASW 36 FPS. 

Scenario F-16 free flight Syria. I can post my settings if needed. They were the same for each test. 

[Flyingfish]

23 hours ago, Qcumber said:

If your CPU is half decent and you have a mid range GPU then QVFR is better. I did a quick comparison today. With QVFR the GPU load was about 70-80%. FPS steady at 72 fps. The same scenario with OXRTK foveated rendering the GPU load was about 85-100 with frequent flips to ASW 36 FPS. 

Scenario F-16 free flight Syria. I can post my settings if needed. They were the same for each test. 

I'd be interested to see your settings. I sometimes get CPU bound when using QVFR. I've got the same CPU as you but half the ram

[Qcumber]

31 minutes ago, Flyingfish said:

I'd be interested to see your settings. I sometimes get CPU bound when using QVFR. I've got the same CPU as you but half the ram

I'll post my settings later. 

[Qcumber]

Here are my settings.

QVFR config:

# common settings for all headsets (unless overriden below).

smoothen_focus_view_edges=0.1

sharpen_focus_view=0.3

horizontal_focus_section=0.3

vertical_focus_section=0.3

peripheral_multiplier=0.4

focus_multiplier=1.6

debug_eye_gaze=0

debug_focus_view=0

turbo_mode=0

 

# Fixed Foveated rendering settings for fallback when eye tracker is not available.

horizontal_fixed_section=0.5

vertical_fixed_section=0.5

DCS settings:

null

12 hours ago, Flyingfish said:

I'd be interested to see your settings. I sometimes get CPU bound when using QVFR. I've got the same CPU as you but half the ram

I have just seen that you have a 4090 so I don't think you will get much from QVFR. I think you would need a more powerful CPU. The 5800x3d gives me lots of headroom with a 4070. 

[Flyingfish]

Thanks Qcumber. Yeah I wasn't sure if my CPU was performing as it should because I was sometimes getting worse performance with QVFR. Having seen your settings though it looks like my CPU is probably working fine and I'd need to lower some CPU intensive settings for QVFR. Thanks for sharing your settings 

[V0x]

I have a problem with Q3 (v74) and gnirehtet. VD disconnects, shows menu, reconnects again. I keep flying couple minutes and thats happens again. Who is have same?