Jump to content

DCS won't launch with Quest 3 link cable after installing virtual desktop


Recommended Posts

So my VR woes continue since the last DCS update. I finally gave in and purchased virtual desktop since I was experiencing so many issues connecting with Air Link. The good news is virtual desktop connects my Quest 3 to DCS perfectly. The bad news is it's micro stutter city to the point that it's unplayable even though I'm getting a solid 60-70 FPS. I've tried every graphical setting possible. I've tried lowering the bitrate. I made sure all of my cores were unparked on my CPU. I tried different Codecs and every setting imaginable and found no joy.

So finally I said screw it, I'll just abandon my wireless ambitions and go back to the link cable. The only problem is now DCS immediately crashes when I try using the link cable. I thought maybe the VD Streamer was causing a conflict but even if I shut that down, DCS world will not launch in any form- MT nor ST. Anyone know a solution to this issue?

Link to comment
Share on other sites

6 hours ago, Maddaawg said:

What is your WiFi situation and settings in VD?

I also seemed to find a fix for the stutter. Oddly enough, INCREASING the resolution and turning on ASW eliminated my stuttering issue almost completely. What's even more odd is OXR Toolkit reports my FPS at a solid 37 FPS while VD reports my average FPS around 60 (which is what I have locked). Not sure which one is accurate but it's buttery smooth with very little stutter now so I'm not going to complain about it. But honestly I think my success is more to do with ASW than the higher resolution because I was playing around with the resolution a bit afterwards and it didn't seem to impact my FPS one way or another so I'm not sure OXR toolkit resolution is even working properly. But I know it absolutely impacted my stuttering issue because I did notice a positive impact by increasing it before I turned on ASW. Very strange. 

Link to comment
Share on other sites

vor 1 Stunde schrieb killerquagmire:

What's even more odd is OXR Toolkit reports my FPS at a solid 37 FPS while VD reports my average FPS around 60 (which is what I have locked).

No. This is not odd.

Since with QuestLink you have activated ASW and you don‘t achieve the 72FPS that would equal your HMDs 72Hz refresh rate, it starts to utilise half-rate motion reprojection at ~36FPS.

Now since activating ASW has zero effect on VD, this still shows you your actual FPS. VD has an SSW option, which is their motion reprojection method.

Only question I have, is why you have „locked“ 60FPS somewhere? If at all, lock it to 72FPS (assuming you are running at 72Hz refresh rate).

Interesting read regarding FPS and refresh rate:

https://paulbakaus.com/the-illusion-of-motion/

 

 vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

image.png

Link to comment
Share on other sites

Posted (edited)
39 minutes ago, Phantom711 said:

No. This is not odd.

Since with QuestLink you have activated ASW and you don‘t achieve the 72FPS that would equal your HMDs 72Hz refresh rate, it starts to utilise half-rate motion reprojection at ~36FPS.

Now since activating ASW has zero effect on VD, this still shows you your actual FPS. VD has an SSW option, which is their motion reprojection method.

Only question I have, is why you have „locked“ 60FPS somewhere? If at all, lock it to 72FPS (assuming you are running at 72Hz refresh rate).

Interesting read regarding FPS and refresh rate:

https://paulbakaus.com/the-illusion-of-motion/

 

My apologies, I misspoke. I have SSW enabled in VD not ASW. The reason I locked the fps at 60 is because I couldn't get to 72 fps so I locked it at 60 in an attempt to fix the stuttering issue. It had no impact but increasing resolution and turning on SSW did the trick so I may go back and set it back to 72 or unlock it all together.


Edited by killerquagmire
Link to comment
Share on other sites

  • Recently Browsing   0 members

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