Gordy

What setting are people using for the VR Pixel density inside the DCS settings? I had been wondering why my images inside VR on my aero were less crisp than on my 2560x1600 monitor despite the VR screens being better... then dialed up the in-dcs VR pixel density setting by a factor of 1.2 or 1.4, and OH MY GOD IT LOOKS SO MUCH BETTER. And I thought it was good before. However, there is significant distortion - it feels over-zoomed, as if I had the VR zoom constantly on... I'm "too close" to the virtual screen, and turning my head has that everything-is-curled-around-me feeling. It also feels like the IPD is now wrong. The cross-eye correction tool doesn't seem to help. I want the upgraded sharpness, but without the warped image. Actually... now that I say this, I'm going back to tap the VR zoom and see what happens If I'm being an idiot and should just tell openxr to render at a resolution 1.2x or 1.4x instead... great. ...running the latest Varjo base 3.6.1.8, and via OpenXR, ftr.

I dunno, once I got the Aero working, I'm practically living in it. The immersion is awesome. Nothing else was good enough to use in DCS, so I was using TrackIR, which was always a struggle to orient my head to see the right switches, and look up/behind in a furball, etc. With Varjo Base 3.6.0.8, I'm mostly seeing a slightly softer display, nothing dramatic, so it's not bothering me. Which actually raises a question - I'm using the OpenXR toolkit and default resolution, which I expect is optimal for image clarity, and gets me 35-60 fps. But with the way VR wraps the image, I am still really confused about what the optimal render resolution should be, so I've been leaving it at the default. Everything looks really good, just a bit weird when I'm on the taxiway with other jets puttering around. Just wondering what other people are using for the resolution and what is supposed to be optimal (hopefully that's the default). If I'm not seeing a big difference with Varjo Base 3.6.0.8, maybe I didn't have it dialed in as much as I thought. Other things that have popped up with Varjo Base 3.6.0.8 and the firmware update - my headset briefly popped up an overheat warning(!), but it went away almost immediately and was otherwise fine, and at one point it would black out for a few seconds at a time... always seemed to be when trying to land a helo, of course.... but a reboot has fixed that <knock wood>.

@VentiPaco, my Varjo Aero has always had issues connecting; I actually have to unplug/replug it and restart Varjo Base many times before I get a good connection with the displays working. My success rate is 10-20%... but after working with the Varjo guys, I figured out that I just need to keep at it, it ultimately connects and will stay online for weeks. They sent me a replacement early on, but it behaved the same. It might have something to do with the rest of my hardware, but I'm content once I get it online. Sometimes I get a green LED on the headset and Varjo Base seems fine, but the displays are black... unplug/replug the headset to reboot, try again. Varjo Base 3.6.x seems to have a better success rate, but it's not 100% yet.

Thanks very much for posting the guide! I would probably never have found the DLL replacement and openxr toolkit on my own. I'm getting 51-60 fps now using openxr (up from 30-40 under steamvr) and got rid of the double cursor that had been keeping me out of VR, pretty happy with it. I was also getting some stuttering under SteamVR that seems to have resolved with openXR. I noticed that I get *zero* benefit from foveated rendering, which is kind of a bummer. The Visibility Range option in DCS made a surprisingly big difference in my fps... hopefully it applies mostly to ground clutter and it will still prioritize showing me distant bandits on the horizon or on the surface while I'm at 30k-40k feet. I miss having fpsVR help me see where my bottlenecks are, but ultimately I want to play without a persistent fps counter anway, and the openxr toolkit offers some raw numbers, at least.