captainHelmet

If you look at the first image in Goa's original post that is what I am referring to. If steamVR is active press the small button to the right of the windows button to bring up the steamVR portal or whatever it is called. In the bottom left of the little interface that pops up you will see a button that when you hover over it says something like "Windows Mixed Reality For SteamVR Settings" It looks like goggles if I remember correctly, I don't have my headset plugged in. That will bring up the dialog box in the first image of Goa's post. It can be very confusing.

Like Vulcan said, the WMR setting of auto will ignore the steamVR reprojection setting. If you really want to lock your frame rate to 45fps and use reprojection either set WMR to "Motion Vector", which will force it on for everything, or set WMR to "SteamVr per-app setting" and then set DCS's steamVR video settings to "Force Always-On". Using Auto will allow your frame rates to bounce around and it will only use reprojection when it needs it. If you want to see this in action, enable the reprojection status indicator in the developer tab of the WMR settings. It's a handy little tool.

Unfortunately it takes some math to figure out what resolution you are actually using. Streamvr has its global setting, which then gets multiplied by the per app setting for dcs, then dcs has the pixel density slider in the vr tab. Assuming your global setting is 100%, the per ap setting is 100% and your pixel density is 1.0 you should be getting the full 140% super sample that hp has deemed necessary for combating the barrel distortion of the headset’s lenses. That said even with everything at 100% I still see a ton of aliasing with medium to far distance objects like you describe. For fun I cranked it up to 200% to see if it looked any better, and it did help but the effect was still there. Its especially bad when sitting on the tarmac and looking out the side of the cockpit. Im assuming the problem is magnified because in stereo the aliasing will be slightly different in each eye. I think the only real fix would be a more efficient anti aliasing implementation. I am happy to be wrong if some one else has found a way to minimize the shimmering.

If you would like to test the feature I believe you can paste that line into your autoexec.cfg if it isn't already there.

Some people report a large sweet spot and others a small one with the G2. The jury is out on whether or not some of lenses are defective or there is just a lot of variance in them. It is starting to sound like the different experiences that people have with the headset have a lot to do with head shape and how their eyes line up with the lenses. All headsets have some amount of sharpness fall off and barrel distortion. I think it is more noticeable in the g2 because the center is so razor sharp that the difference between the center and the edges is more dramatic than other headsets. With other headsets you may not notice the image going from slightly blurry to more blurry. Not super sampling and setting the panel resolution to "50%" in streamVR really exaggerates this effect. Being able to properly super sample helps broaden the sweet spot. Even if you can't go up to a full 100%, I saw a big improvement at 80% if your system can do it.