Highwayman-Ed

Pretty sure there is one for the 737 in the base installation.

3rd

Stand alone DCS through Link

Does the Orion support the Warthog grip via the adapter same as the Super Libra? I asked WinWing a week ago, but they haven’t given me the courtesy of answering my emails…

I've stopped chasing ghosts in the Oculus Tray Tool and the Oculus Debug tool, I spent more hours than I care to remember tweaking and fiddling with settings over the years, and as my wife pointed out to me a while ago, I spend more time messing around with things for DCS than actually flying it! With one final pieced of advice I'll pass on my settings. My settings may work for me, but there is a very good chance that they will not work well for you. Be it in terms of frame rate, stutters, whatever it may be the subtle variations in CPU, RAM, GPU, Link cable, other programs installed on your PC, and also the aircraft and situation that you fly in, as well as the lucky 8 ball shake that seems to occur every time you start DCS, results may vary, so don't get hung up on it! So, with Oculus Desktop software version 30, and Quest software version 29, my settings are: I do not use Oculus Tray Tool (any more) I do not use Oculus Debug Tool (any more) Oculus Desktop settings: I use this as my unofficial Link cable, and it gives me unlimited play charging the battery faster than it drains: Which yields the following test scores: However, be warned that it will draw 5 Amps from your USB port, and one of my friends had issues with his Quest dropping out because his motherboard couldn't reliably supply that amount of power over his USB C 3.1 ports. After he changed to a USB A 3.1 cable that only drew 3 Amps, his issues went away. DCS Settings (note that I've upped the Pixel Density to 1.2 since the photo through the lens, but it's not much clearer than at 1.0, I use it as it helps with aliasing of the terrain which only became much more of an issue for me since flying the Hind low level) The important settings in here to note are MSAA on x2 and Anisotropic Filtering on x16, the Pixel Density of 1.2 also helps but is not as critical as the first two. With these set, they are aliasing the edges and eliminating most of the absolute shit show of shimmering that I experience when close to the ground, which is a complete and utter deal breaker for me (See Wag's Video of ATGM's in the Hind, when he looks through the sight, that's what I'm talking about). All 3 of these settings however have only a little effect on the readability of the MFD's, I'm using them now because I'm flying the Hind close to the ground. As a result, my frame rates are nowhere near as good as they could be and I'm well aware of that, but this is the balance that I have come to achieve with my rig. As such, I maintain around 40fps with DCS right now in the Hind, but things like multiplayer, the Super Carrier and others will drag it down to almost half of that on occasion, so I generally avoid these for the time being. If I'm whirly birding, I'll use what you see above, If I'm flying high in a Tomcat or the Hornet, I'll drop the PD down to 1.0 to give me a few more frames when I'm on or near the carrier. The only other advice? Clear your shader caches often i9-9900KF @5.2GHz 32GB DDR4 MSI RTX 2080Ti Gaming X-Trio (Nvidia 466.77 driver) DCS on Samsung EVO 970 SSD Good Luck!

+1, it seems to over compensate for where the trim is set.

+1 for an option for this, but I'm actually fine with it how it is... There's simulation, then there's just busy work, and I'd class this as the latter. What I would like to see as others have stated is the option of inserting your own images as per the kneeboard here so they're not so cluttered with short distances between waypoints, or flight legs that write the time and distance notes over one another. Most definitely need key bindings for the etch'a'sketch as well as it's painful to adjust this in VR

No joystick mapping available for close canopy (LCTRL + C) either

Agreed, I'd like to see this implemented too.

Here's a through the lens photo of what I get in my Quest 2 via a link cable with DCS VR presets and standard PD setting of 1.0

That setting is in settings in the headset when linked to desktop, but I believe that it's only for the Desktop GUI, not anything that renders directly like a game.

Pushing either of the encoding values up when using v29 and 120Hz causes occasional audio stutters for me. if you want to push those higher, drop your refresh rate back down to 90Hz.

I finally managed to fly DCS this morning without significant cloud jitter, but the method of doing so is undesirable. 1. started Oculus Desktop Client and set the refresh rate to 72Hz (lowest) 2. Start Oculus Debug tool and force ASW on thereby forcing 36Hz 3. Start DCS and select the Low preset. 4. Disable shadows entirely (both regular and terrain) 5. When DCS restarts after the settings have changed, start a quick start mission with clouds. The clouds on the horizon still move a little, but nothing remotely close to how much they did before. This is the only way with my i9-9900KF and 2080Ti that I could achieve a constant stable frame rate that matched the refresh rate of my headset. I then tweaked settings gradually up (and not that much unfortunately) until I reached the point where DCS couldn’t maintain a stable FPS and the jitter became apparent as the FPS dropped below the 36fps threshold. Not trying to provide any workaround or suggest that FPS is the underlying issue, but thought others may find it interesting.

Same. Also little details like the mic and headset cord are sometimes only rendered in one eye too

I’m going to say yes, and yes, but let me clarify. instruments, there are always some that won’t be crystal clear, but I can read all of the MFDs without leaning in, in the Hornet (except with the map on the centre MFD) Targets, I can spot them well enough, and realistically, you would never be able to spot a fighter 10 miles out with the naked eye, but I can spot Hornet sized targets without zooming or labels around 5 miles. I don’t claim that these settings are the best, nor will they suit everyone, they’re an example of how regular medium settings work for me without having to tweak the hell out of everything. best of luck! - updated to add a screenshot through the lens from my phone. Sorry the edges are out, but I find it really tricky to hold the phone stable and in the right position to capture an image, but hopefully it gives you an idea of what the Quest 2 looks like for me. Even then, these images hardly do it justice...

Not enough to count unfortunately. As ED have said in the past, the majority of their users fly single player with a flat screen. They probably only fly in the Caucuses map in the Free SU-25T as well and have never purchased a module

No, tweaked and fiddled with every setting possible for hours and nothing made a difference for me

Same issue with Hornets and Tomcats for me too.

Same here, much clearer in 2.5.6 than 2.7 Quest 2, 2080Ti, exact same settings in DCS (other than the new ones) as with 2.5.6

I've been running the Quest 2 after grabbing one as a stop gap whilst waiting for Pimax to return my 5th RMA, and have found it a much better experience than the 5K XR or the newer 8K Plus headsets that I had purchased. I did tinker around with the settings in the Debug tool, and even with SideQuest for a while after reading a bunch of forum posts and watching some YouTube reviewers claim that they had discovered the holy grail, but never really saw any significant gains without compromises, and in some cases only saw performance drops. I'm currently running the v28 bundle of the Oculus Desktop software and v28 of the Quest 2 software with 120Hz enabled, although link doesn't recognize this yet and despite the Oculus guide saying it should be available, there is no AirLink showing in my beta tab of the desktop software, but I much prefer Link over Virtual Desktop anyway, so I don't expect this to change my mind and use it instead. I'm running link via this cable from Amazon which keeps the headset at about the same charge level whilst I use it, so I can fly for hours and hours with no problems plugged into the USB C 3.1 port on my MSI z390 Gaming Carbon Pro motherboard. I will add here however that this cable will draw a lot of power from your system and a friend of mine that got the same one to use with his quest suffered from connection drops with link as it was drawing too much in combination with his other devices over his motherboards USB header. He downgraded to a USB A cable that only drew 3A instead of 5, and the problems went away. I've added my settings below, and other than the Clouds making me want to throw up if I fly with them for more than 15 minutes, I've got the smoothest experience in DCS I've had in a long time. Running an i7-9900KF@5GHz, MSI Gaming X-Trio 2080Ti, 32GB RAM and Windows as well as DCS on SSDs of course. I performed a full clean of my DCS and Saved Games folder before the update and deleted the mandatory FXO and shaders folders, but other than what you see in the images attached, all other settings (NVidia) are stock defaults. The only thing I've ever done with my Quest 2 itself is add the Elite Strap and a silicone face cover for workouts which positioned the quest a little further from my eyes, but that alone gave it the largest sweet spot I've experienced in any of the VR headsets that I've used (Rift CV1, Vive, Index, Pimax 5K Plus, Pimax 5K XR, Pimax Vision 8K Plus, Pimax 8K X). At this point however, I've returned my Pimax headset for a refund (after the 6th one had a fault with the lenses), and only borrowed the Index for a extended trial, so the Quest 2 is the only headset I have without going backwards and until the next gen is out, I'm more than happy with it. Final note to add, I pretty much fly the Hornet exclusively, so haven't spent much if any time in any other aircraft whilst I wait for the patch to fix the clouds.

Interesting thing I noted this afternoon, the cloud shaking for me at least seems to be directly linked to minute movements of the headset. I had my Quest 2 on my desk this afternoon after tinkering with a few settings to try and get them stable as some YouTubers have commented that they do not experience any shaking in VR and saw that on the desktop, the clouds didn't shake in the reprojection. I took my phone and attempted to compare the view through the lens to that on the desktop and noticed that they were not shaking on the image on my phone either and thought I'd struck lucky with some tweak I'd made. I put the headset back on, and they were shaking... I took the headset off then, removed the head strap and effectively clamped it to the edge of my desk. Moved my eyes up to the lenses and no Shaking! Now I'm off to the hardware store to get some really strong glue to fix my head in place so it can't move and I too can enjoy the clouds in VR in DCS with no wobble

i have this exact issue too, Oculus Quest 2 via Link. I can notice it occasionally with objects, especially shadows, but the Deck crew mention is what really nailed it for me. It’s just some little details that are different between my two eyes.

Same results here, the bouncing clouds can only be tolerated for so long before nausea starts to sneak up on you, and it doesn't seem to matter what the quality for the clouds is in the settings, they look 'too soft' in VR and no different whichever the setting. They look much better on my monitor if I fire up DCS without VR enabled.

Do you have winds in the mission by chance? AI seem to be ‘blown off’ formations by the relative wind and have been for quite a while now. Fly the same mission with no wind, and you’ll find they get right into position without any problems. you can test it by flying as you are here, into the wind, then turn 180 with a tail wind and watch them move too far forward.

hey @Mustang You're a god as far as all these shaders and textures go in my book Any chance you know how to get DCS to use a single shadow LOD? For example, when flying in close formation with a wingman, their shadow under their wings, keeps switching between the high and next level down LOD, over and over and over and it really breaks the immersion. The same thing is true when you're flying close to the ground, I often see half of my helicopters shadow in a high LOD, and the other half in a low LOD, sometimes only half a shadow! Thanks for all your hard work!