Re: Virtual Desktop V1.3 VR Download
Sanora Ngueyn
I'll add some pointers to get started. If you installed the previous "standalone beta 0.6.0", you should uninstall it from Add or remove programs first. Instead grab the latest Virtual Desktop from your app store (1.29.7.).
VDXR should be compatible with all my other OpenXR mods (such as OpenXR Toolkit and Quad View Foveated). If you are having issues, just do the usual: try Safe Mode, resetting settings, or disabling any mod.
Does this add any value for stand alone (Quest) users? Or merely for Steam(Vr) users?
As a Quest2 + non-Steam user, I can ditch any Quest-link already, and solely depend on VD alone. So I'm not sure what this would improve for me.
Hey there using a Meta Quest 3 and for some reason when installing VD Beta and starting DCS MT my headset turns black. I hear music from VD and on PC DCS is opened but not streamed to my headset. Do i still need to have steam vr or oculus to launch the game? I deinstalled steam vr to see if this will work but it didnt iam a little confused how to make this work. I lhope some of you can help me out.
In order to make it work on my end, I have to execute DCS from the streamer app on the PC. So right click the little streamer app logo on the task bar, and chose execute... select the DCS shortcut from the desktop and you should be on your way.
DCS running on VD has always been a stutter fest for me, whether it's Oculus runtime, or this VDXR iteration. Does any one know what's up? Everything with Airlink and Link cable works fine with no stutter.
Network and everything is running well according to VD's debug dialog - except for game part is reporting on 28ms of lag with yellow text. I have a 5800x3d/4090 system, so it's not from lack of horsepower, and as mentioned before, Airlink and Link cable works just fine.
Stutter can mean a couple of things, but in my case it was AWS not working (correctly). Set the streamer to a 90hz output, but lock the FPS in your NVidea DCS settings to 45 FPS. After that, force AWS to always enabled in VD. On my end, VD started to nicely fill in the blanks frames, while my GPU has an easy life while being locked at 45 FPS.
But you mentioned you uninstalled steamVr to see if it would work, why did you even had steamVr installed with the stand alone version + a Quest headset? Afaik, you don't need steamVr at all. Or am I missing something?
First i installed VD non beta but it wouldnt launch dcs world on headset without steam vr. Then i installed steam VR too and i could play in VR. Then i started to search for ways tweaking settings and read about that OpenXR could give better performance so i installed OpenXR Toolkit Companion App and added --force_enable_VR --force_OpenXR to the DCS Desktop shortcut path.
Strange I dont have all that. I bought a Quest2 2 weeks back, installed VD on the headset, the streamer on the PC and was underway. I dont have the toolkit nor any force option in the DCS shortcut. I don't have the oculus client running when I run VD, nor link or airlink enabled, just the service. I don't even dare to touch steamVr with a ten foot pole
Oh, one tip, I used fraps to see what happened. SSW did half my FPS, but the result was not smooth. Basically, I didn't see a difference between auto and always enabled, I had to do that myself with the nvidia settings. Auto caused all kind of lag, stutters and anomalies I don't like. I rather have it constantly doing its thing, than going yolo as it sees fit. So with the FPS locked at 45 AND SSW enebled, its buttery smooth.
Really? I tried VD a week ago. I wasn't impressed. Sparklies that seemed to track eye movement. Probably other issues too. Stutters perhaps. Link just works for me. I'm on a Quest Pro. I'd be interested to hear what other Quest Pro users think.
Oh, one tip, I used fraps to see what happened. SSW did not half my FPS somehow. As I didn't see a difference between auto and always enabled, I had to do that myself with the nvidia settings. Auto caused all kind of lag, stutters and anomalies I don't like. I rather have it constantly doing its thing, than going yolo as it sees fit.
Does the preferred Codec option in desktop streamer somehow play a role? I choose AV1 10bit as my GPU is a amd 7800xt and as far as i know it supports this codec on the other hand how can this be the source for the problem as it seems to work fine when steam vr runs too. I feel like iam in a Maze trying to find the solution.
Well, my VD streamer did hang a couple of times yesterday, causing a freezed image in the headset, while the game happily jogged on. Since I switched to one of the faster codecs, not anymore. Not sure if its really a fix, but I keep it where it is for now since it performce nicely.
I've been flying about on Marianna's in the warbirds on a steady 45 fps. I noticed the mozzy didn't keep it at 35, an F16 dropped it to 40, so I'm not there yet. But coming from a CV1, this is a breath of fresh air.
The headset turns black, music from VD is played the game on desktop opens up. I have to close VD from Meta desktop because i cant open the VD menu, when i restart VD itll be stuck in dark with no menu but music playing.
I then have to end desktop streamer on pc and via taskmanager manually close all virtual desktop related tasks as they dont seem to close by themselves when closing on pc and headset. After all that done i can enter virtual desktop again.
I changed Codec to 264+, disabled Use optimal resolution and increased streaming bitrate to 300 something, SSW always enabled, Snapdragon Game super Resolution enabled. One of these changes caused the game now to be streamed to headset i guess it must be the codec and therefore the higher possible streamingbitrate.
At least i can launch it now but i still encounter some awkward problems when flying. When i move my head fast while flying i get kind of big black artifacts and it takes a few seconds for the picture to return to normal, when moving the head slowly its kind of ok. My latency is quite high in the 60s sometimes higher and the ingame latency jumps all over from 27 to 100 randomly.
Can someone more familiar with VD explain how this works so well. Like everyone else I have been spending days tweaking my settings to try and find something I like. I literally fired up this new VD beta, set it to Godlike and ramped all the sliders right and I open DCS to find comparitively crystal clear visuals compared to link cable, silky smooth frames and almost no visual artifacts that I can discern so far.
Worth noting that I previously had reset everything to baseline and was running my Quest 3 with a 1.3PD in DCS itself on a 4090. I intentionally turned the PD back to a baseline of 1.0 before starting VD and it is an order of magnitude better already.
Those artefacts seem to be the areas out of view that aren't rendered, but need to be rendered when you turn your head. So the higher the latency your wireless contection is suffering from the bigger those artifacts are. I see them as well, but I really have to start a horizontal headbang in order to make them obvious. I'm sitting right infront of a dedicated WiFi6 access point with only one cient, my Quest2 headset.
7fc3f7cf58