ShaunX

sounds like you're long sighted as well as short sighted then, or at least you're heading that way. Mine used to be as you describe but gradually deteriorated and now I actually can't focus on anything, at any distance, without lenses. Got so bad that I had a prescription windscreen fitted in my car..but eventually had to have it removed again as my enormous head was scaring other drivers

I used to comute on a motorbike everyday across London, in cold and wet weather visor fogging was a real health hazzard. The old trick was to rub potato skins on the inside of the visor, worked pretty well

It's definately short sighted folk who need lenses for VR as explained by Tapi above. You will note on their website, VR Optician specifically asks for you far distance (short-sighted or myopia) prescription. NOT your reading (long-sighted) one. If you're only short sighted then inserts are perfect because when you lift the headset you'll still be able to focus on your keyboard and screen without having to remove your distance specs. Unfortunately I'm both long and short sighted. I have distance inserts in my G2 which are excellent for DCS but when I lift the headset I'm essentially blind and would need to put my reading glasses on to read my keyboard. As a result I rarely lift my headset and rely on my hotas and voice attack (which, I suppose I could argue, increases the immersion.) I did try wearing my transition lens specs (which are distance at the top and reading at the bottom) but then I couldn't look down in the headset and maintain focus. Other advantages of inserts are that they allow you to bring the headset closer to your eyes than with specs, so you can increase FOV, and also they don't fog up which I found my specs would do. They also protect your headset lenses from scratching as they're always on.

I guess my inital problem was that I thought, from your instructions, that I had to somehow get a finger and thumb on either sde of the sensor to squeeze both tabs when in fact all that is required is a strong press inwards on the nearest tab and the sensor pops out.

According to this article, DLSS 2.0 (and it is version 2.1 that is required for VR) https://www.nvidia.com/en-gb/geforce/news/nvidia-dlss-2-0-a-big-leap-in-ai-rendering/ " One Network For All Games - The original DLSS required training the AI network for each new game. DLSS 2.0 trains using non-game-specific content, delivering a generalised network that works across games. This means faster game integrations, and ultimately more DLSS games " ..suggests maybe not such a big effort for DCS VR.

bugger Ah, so it's fixable. Not entirely sure why we opt for the Beta's anyway

Haven't had a chance to look yet, but could it be because you are opted out of WMR for SteamVR Beta ? Presumably you can revert to the stable SteamVR to get the setting back ?

With regards the SteamVR per application setting, do you think there's a performance difference between setting motion smoothing as "Enabled" vs "Forced" ? Granted there is supposedly a stutter when if flips between 90 to 45, but personally I've never noticed one. I used to set forced but since 2.7 and adopting your revised 2.7 settings I seem to be getting a lot more 90 FPS time so I'm set to enabled now. That said, I can't tell the difference between 45 FPS and 90 FPS anyway so, apart from the bragging rights, I'm not sure I see the point of setting it to enabled over forced ? So I guess what I'm asking is, if I'm flying a mission where the terrain and activity means I can only hope for a fixed 45 FPS, am I better of setting enabled or forced, or doesn't it make any difference ?

...Very glad I persisted with the install. Finished calibration and the new slew sensor is a MASSIVE improvement over the old one. Tracking on all sensors on the DDIs is now highly controlable and accurate and it doesn't even need a dead zone for the depress to function without slewing. Many thanks @Deltaalphalima1 !

@Deltaalphalima1 Received mine. I've taken the side panel off but I don't see any way of getting my fingers in to "push the small plastic clips holding the sensor in place towards the centre of the sensor" as per the instructions. I can just about get my pinky into that space. Is this what everyone sees ?.. EDIT: Scratch that ! Just needed a night's sleep, a little persistance and a few choice swear words and it popped out nicely !

Do you have any pending Windows updates ? I ask because I didn't get the ED VR Mask via SteamVR for a couple of weeks after 2.7, then it suddenly started working immediately following a Windows feature update for version 2004

I have the same problem with my old neck. I assign the snap left and right to 2 hotas buttons then I find if I press one it rotates my view enough to make looking down at the side instruments a lot easier.

I literally never fly without Viacom Pro running and I absolutely love it. I have to say, although I've read a number of times that the Viacom profile has to be top level, mine is configured as the second level profile to all of my aircraft specific profiles and it works perfectly. I configure that way as it means I only need one copy of it and I have VA commands set in the top level aircraft profiles to easily switch between them while I'm in VR. Here's the config from my top level A-10C II profile. I have Viacom (and then a generic DCS world profile) daisy chained in the "include commands" Never had a problem with this config with any Viacom Pro feature.

It's in SteamVR general settings, set SteamVR Home off

Sounds like something is not clearing down VRAM after the mission. Do you have FPSVR installed, that would tell you pretty quickly. I used to get that same issue on my old rig and I think I resolved it by turning off the cliff house in SteamVR (so you just get the native SteamVR construct when you launch SteamVR). No idea why it worked but might be worth a try.

..and another one with eye tracking hardware. Wouldn't it be great to have eye tracking if it would move the mouse cursor in DCS ...I'm just dreaming

My bad..sorry you're absolutely right of course...curse that barrel distortion Either way, 80% is the sweet spot for me.

My understanding is that it relates to the way x570 boards use PCIe 4.0. HP and AMD are apparently working on a BIOS solution. There's a beta BIOS release for it for my ASUS board but the reports I've seen state it's still not fixed. My x570 has 3.0, 3.1 and 3.2 ports and the G2 doesn't like any of them. The G2's native resolution is approx 3168 x 3096 per eye. You'll get this if set overall steamVR SS to 100% I personally run at 80% for DCS in SteamVR application specific settings which is approx 2836x2768 per eye and only notice a tiny difference from 100% which is worth it for the bump in framerate (This is obviously with DCS PD left at 1.0) If you have the rig, it is absolutely worth setting SS to at least 80% for the clarity...and that is what he G2 is all about.

Do you have HAGS (Hardware-accelerated-GPU-scheduling) turned on in Windows settings-graphics settings. From memory I think this screws with the auto motion-reprojection mode. Try turning it off.

The G2 is indeed fantastic, but, will tax even your rig (see my signature). If you haven't already, do yourself a favour and study this thread and apply the optimisations and mods to get the best experience out of it with a 3090.. Also, be aware that many Ryzen 5000 series users (myself included) struggled to get the G2 to work with any of the USB ports on their motherboards (a known problem with certain x570 boards). I had to solve the problem by plugging the G2 into an unpowered USB 3 hub, with that hub plugged into a mobo port which works perfectly.

Isn't this just an approximation of what happens IRL ? Hold a pen up in front of your eyes at arms length and then focus on something past it in the distance. you'll see 2 pens.

it has literally never crashed before on me either mid mission which is why I opted back out of the Beta yesterday. I'll give it another go tomorrow with the new SteamVR beta when I have some time and see if that resolves it. 20H2 - Maybe, I'm still 2004 19041

Likewise, usually WMR first then DCS, just tried DCS with none of the other components already running and still launches with no issue. I always launch that way anyway and actually seemed to have no issues when I did benchmark testing against the new WMR beta this morning. However, then I played some missions and all was fine until about 20-30 minutes in, then SteamVR crashes mid mission every time.

Your best bet as I found myself, is to just opt out of the beta version of WMR for SteamVR. It does seem to be that beta update that is causing the problems. That fixed my issues immediately and I'm getting the same performance on the stable version.

I reverted to the stable WMR for SteamVR and DCS no longer crashes in missions. I also reran my benchmark and don't see any difference between beta and stable versions. I note the new SteamVR beta has a bunch of new features which require WMR for SteamVR beta for them to work so I guess I won't be trying those for now