Hunting for the stutter-free VR experience.

[The_Nephilim]

6 minutes ago, Gryzor said:

I have better graphics quality and performance with VD. Much better than with cable. I don´t tested it.

VD is the program on Steam correct? I just find it hard to believe that would work bertter then the cable..

[darkman222]

On 12/10/2024 at 4:18 PM, Panzerlang said:

I can now more intuitively sense that the dips below 90fps account for the steps in the graphics. But boy, what an improvement! Thank you SK.

This thread is a little difficult to read in terms of what gave you the big improvement. What was it?

I have a comparable system and comparable issues.

Having tried almost all of the mentioned things, its worth looking into LOD switch factor which gives me stutters close to other jets, probably the max render distance also contributes. I am pretty sure some stutters come from data ( mesh, texture) being loaded and unloaded.

[Gryzor]

24 minutes ago, The_Nephilim said:

VD is the program on Steam correct? I just find it hard to believe that would work bertter then the cable..

 

24 minutes ago, The_Nephilim said:

VD is the program on Steam correct? I just find it hard to believe that would work bertter then the cable..

No. VD do not have any relation with Steam. VD === Virtual Desktop. Best performance with god mode.

[The_Nephilim]

6 minutes ago, Gryzor said:

 

No. VD do not have any relation with Steam. VD === Virtual Desktop. Best performance with god mode.

oh ok so where is it just using the Air link I am unsure why it is called Virtual Desktop?? Where do or how do I set God mode?

[Gryzor]

2 minutes ago, The_Nephilim said:

oh ok so where is it just using the Air link I am unsure why it is called Virtual Desktop?? Where do or how do I set God mode?

Home | Virtual Desktop

[The_Nephilim]

9 minutes ago, Gryzor said:

Home | Virtual Desktop

Dude that is the same program from Steam.. so what about God mode is that just setting the encode rate to 960? or is God mode something  differnt.

 

[Gryzor]

Wireles version for Q3 is not the same program, it runs completely independent. Max bitrate 500.

[av8orDave]

I love the thread title. In my experience, "Hunting for the stutter-free VR experience" in DCS is akin to hunting for bigfoot. Sure, you might be able to find some evidence that it exists, but it is scant, poorly documented, sometimes appears doctored, and the overwhelming majority of evidence would incline one to believe it is a myth.

[kksnowbear]

26 minutes ago, av8orDave said:

I love the thread title. In my experience, "Hunting for the stutter-free VR experience" in DCS is akin to hunting for bigfoot. Sure, you might be able to find some evidence that it exists, but it is scant, poorly documented, sometimes appears doctored, and the overwhelming majority of evidence would incline one to believe it is a myth.

ROFLMAO

Holy gumballs, I almost peed myself laughing. 

Ain't it the truth.  TY TY TY

[sleighzy]

2 hours ago, The_Nephilim said:

Dude that is the same program from Steam.. so what about God mode is that just setting the encode rate to 960? or is God mode something  differnt.

 

The one on Steam is years old, and does not support streaming PCVR games. If you’re looking for VD then you need to buy it from the Oculus store in your headset. The VD Streamer app for Windows that this connects to can be downloaded for free from their web site. 

[gonvise]

In my opinion and tests with Quest Pro, VD god mode is far (below) than the best quality which can be achieved via cable link, with x2 supersampling, 960 bitrate.  VD is an excelent application, but even VD god mode can't come close to the cable link connection "on steroids". Yes, if we compare the VD god mode against cable link with the native resolution, the VD may work with a quality similar to that of the cable link, but with a 4090 and a good processor, supersampling at 2 and bitrate at 960 is something that VD simply can't match when streaming. And I say this with knowledge of the facts, I already have a dedicated 6E router and I have tried everything that had to be tried... but I insist, for a default configuration it is a magnificent application. I hope they are able to implement connectivity via cable link someday, although due to manufacturer issues I understand that it will not be possible.

[Panzerlang]

1 hour ago, gonvise said:

In my opinion and tests with Quest Pro, VD god mode is far (below) than the best quality which can be achieved via cable link, with x2 supersampling, 960 bitrate.  VD is an excelent application, but even VD god mode can't come close to the cable link connection "on steroids". Yes, if we compare the VD god mode against cable link with the native resolution, the VD may work with a quality similar to that of the cable link, but with a 4090 and a good processor, supersampling at 2 and bitrate at 960 is something that VD simply can't match when streaming. And I say this with knowledge of the facts, I already have a dedicated 6E router and I have tried everything that had to be tried... but I insist, for a default configuration it is a magnificent application. I hope they are able to implement connectivity via cable link someday, although due to manufacturer issues I understand that it will not be possible.

What makes you think VD won't work on a cable connection? It worked fine that way with my Pico4.

6 hours ago, darkman222 said:

This thread is a little difficult to read in terms of what gave you the big improvement. What was it?

I have a comparable system and comparable issues.

Having tried almost all of the mentioned things, its worth looking into LOD switch factor which gives me stutters close to other jets, probably the max render distance also contributes. I am pretty sure some stutters come from data ( mesh, texture) being loaded and unloaded.

I don't know for sure but I strongly suspect Core Parking was the culprit.

Edited December 11, 2024 by Panzerlang

[Panzerlang]

If you have a very good GPU (a 4090 basically, lol) the issue with DCS is the CPU. Even the most powerful one finds it hard to keep up. The FPS counter in the game has shown only "CPU Bound" messages, mainly on the graphics rendering thread. Today I'll see what settings that involve the CPU can be dialled back and try it out.

[Phantom711]

vor einer Stunde schrieb Panzerlang:

What makes you think VD won't work on a cable connection? It worked fine that way with my Pico4.

Because it doesn‘t with a Quest.

[Panzerlang]

30 minutes ago, Phantom711 said:

Because it doesn‘t with a Quest.

It didn't with the Pico4 until I'd messed around with Network settings. I persisted only because of the YT videos that clearly showed it should/could/would. Lol.

[Dangerzone]

3 hours ago, Panzerlang said:

What makes you think VD won't work on a cable connection? It worked fine that way with my Pico4.

I don't know for sure but I strongly suspect Core Parking was the culprit.

I can confirm core parking was a major player in my instance as well. Definitely one to be on the first list of things to check/disable. 

Additionally - I have found it turned on automatically again at times. Not sure if a windows update does this or not - but worth keeping in mind if the stutters ever return.

[Panzerlang]

Taking absolute GPU liberties.

Ignore the resolution, I opened in 2D for greater ease of taking a screenie.

The only setting that affects the VR stutter is having the view distance at Extreme. There's a huge free-flight area on the Caucasus map where you can see for miles. Panning the view around that causes lots of spikes but once everything has loaded it becomes smooth again. But the loading is ongoing, so it's all a bit spikey. On High the spiking goes away.

This is on a 4090 and i9 13900k at 5.5ghz, 32GB RAM and clearly shows how the CPU is the limitation. There are zero GPU messages in the FPS window, it's just a yellow "CPU Bound, Rendering Thread". With View Distance on High my DCS runs 95% smooth, with the 5% being the occasional jerk. 

With a lesser GPU these liberties can't be taken but I have no idea where the threshold is at. Anyway, FWIW.

 

[Panzerlang]

The Res of Cockpit displays is wrong, it should be at 1040. I accidentally hit the Low button and missed setting that back.

[Qcumber]

9 hours ago, Panzerlang said:

What makes you think VD won't work on a cable connection? It worked fine that way with my Pico4.

Are you using an ethernet cable via an adaptor? I used to have a Pico 4 and that's how I did it. It's not the same as a usb tether. VD does not support a usb cable connection as Meta won't allow it. I can't get an ethernet connection to work on my QP. Not sure if the Q3 will support it either. 

[gonvise]

10 hours ago, Panzerlang said:

What makes you think VD won't work on a cable connection? It worked fine that way with my Pico4.

 

Unless I'm missing something (hopefully!), VD doesn't work with a manufacturer link cable like the one on the quest pro, but as Qcumber points out, what you've used (likely) is an ethernet cable via an adaptor. With that adaptor you're getting exactly the same thing as with wifi6E. But the image still streams and gets compressed. I insist, I am not criticizing VD, it is an excellent application, I only note that in terms of quality and stability it cannot match, in my case with quest pro, what the link cable gives.

[Panzerlang]

Ah, that's the confusion. Yes, I was talking about an ethernet cable via an adapter.

[Dogmanbird]

I'm hoping VD will give us a link cable version too, even just to reduce controller input latency slightly

it's taken this long, I'm guessing there's something VD don't/can't have access to on the meta side, maybe legal reasons? I think we would have seen it by now.

[Qcumber]

5 minutes ago, Dogmanbird said:

I'm hoping VD will give us a link cable version too, even just to reduce controller input latency slightly

it's taken this long, I'm guessing there's something VD don't/can't have access to on the meta side, maybe legal reasons? I think we would have seen it by now.

According to the VD discord server the lack of cable option is a meta issue. It does not sound like anything will change. 

[Marshallman]

Having just spent £1K on a motherboard and deposit in for a Pimax super, I am seriously frustrated at the one step forward two back VR problems.

Last night on iraq I had CPU on overdrive....then GPU on overdrive (specs below).....

I started to think when was the last time i was happy with VR and it was openXR toolkit. I downloaded it again and now everything is running fine with CPU and GPU at 24 and 45%

Zero bottlenecking and sharp as......just my 2p worth

Was open XR DCS broken?

[gonvise]

6 minutes ago, Marshallman said:

Having just spent £1K on a motherboard and deposit in for a Pimax super, I am seriously frustrated at the one step forward two back VR problems.

Last night on iraq I had CPU on overdrive....then GPU on overdrive (specs below).....

I started to think when was the last time i was happy with VR and it was openXR toolkit. I downloaded it again and now everything is running fine with CPU and GPU at 24 and 45%

Zero bottlenecking and sharp as......just my 2p worth

Was open XR DCS broken?

what options are you using in openXR toolkit?