jparker36

is there a way to import everything from the previous version of the app?

The reverb is sharper in the sweet spot, 100%. The difference and what people mean by clarity, is that I can be looking directly through the HUD on a jet, and without moving my head glace to my instruments/MFD and read them at exactly the same resolution/clarity as the HUD. The resolution/sharpness isn't G2 sweet spot level, maybe 85% of it, but its across my entire FOV. The G2, to read the instruments or MFD at all I'd have to move my head to center it in the sweet spot. I did get used to doing that so was fairly indifferent, but when I tried the quest pro, I couldn't go back. 72fps native also gave a FPS boost vs trying to keep 90 native on the G2. So I got to turn up the settings, use my eyes more naturally, better color reproduction, local dimming, all in exchange for some loss in peak clarity. To me, well worth it.

DFR works on the quest pro in a few games, MSFS, iracing, and ACC being the biggest ones

Quest Pro if you're ok giving up absolute top end resolution for near-perfect edge to edge clarity.

No mans sky, MSFS, ACC, Skyrim VR. There's 4. DCS will make 5.... and I've not even researched it, just named the games I have that use it.

Don't know if I'm just unlucky, but I can't get quest pro to work well at all. Constant stutters both in and outside of games over quest link cable. Compositor dropping frames left and right even if I lower encode resolution, bitrate, supersampling - doesn't matter. 72hz, 90hz, doesn't matter.

I just alleviated this issue quite a bit by using process lasso and forcing DCS and the oculus encoder onto P cores only. Worth a try since you're on a 13600. I've been screwing with it all day since I got in a quest pro and I didn't have the issue on reverb.

3080 on a g2 is extremely gpu bound.... MT has removed almost all CPU bottleneck, so GPU is the limit. I'm GPU bound now on a 4090 with a g2

Yep, I was waiting until raptor lake reviews to decide what to do CPU wise. Since 5800x3d still dominates ACC and MSFS, I can assume it does in DCS as well. So I wait until Q1 for 7800x3d and that will unlock the 4090 in DCS a bit more I think. If I turn off reprojection and use those same settings, I get 55-70fps. Not worth it for me since it still has judder when low and looking to the side past trees, and I tend to enjoy CAS AH64 and KA50 missions. One interesting thing is that I've found for whatever reason, steamVR with the G2 is actually much much better in reprojection than openxr now. Rotors and props on ww2 jets (mostly the bf109) no longer make the entire screen a wobbly mess, so my optimal right now is actually 45fps settings with shadows on high using steamvr. Rock solid 45fps and minimal reprojection issues. Looks amazing!

@BIGNEWY, any update on if there's a fix in the works for this?

I've been chasing after VR perfection for a long time, and having installed my 4090 last night I can finally say I've got it. 10850k @ 5ghz 32gb ddr4 3600 RTX 3090, now 4090 Reverb G2 using OpenXR Test scenarios I use: BF109 Channel Bomber Intercept Mission BF109 Channel Low Level Hell Mission AH64 Marianas Free Flight F16 Syria Free Flight I can run 100% locked 45fps ASW with all settings maxed other than shadows on low/flat, MSAA 4x. No drops below 45 on any test scenario. Only downside as anyone who uses ASW knows is that BF109/Spitfire props and AH64 and KA50 rotors suuuuuck using reprojection, so I tried to see how I could get to 90fps. Alternatively, I can run 90fps 95% locked on the same settings, but with shadows and cockpit global illumination off and MSAA at 2x. The drops that do occur are CPU bottlenecks. I will be getting the 7800X3D as soon as AMD releases it early next year to resolve the CPU issue. In order to get to this level I had to turn on FSR @75% resolution, 80% sharpness. I don't really notice any quality degradation. If I were to choose, I do prefer the locked 45 reprojection as it felt smoother without the CPU bottlenecks, but I imagine I'll switch full time to 90fps using FSR once I get a new CPU. In either case, the GPU is never at 100%, only drawing ~300 watts, so for sure the 4090 is the first cpu that can actually pull off high resolution HMDs. With the 3090 I had to turn all shadows off, clouds to low, terrain distance to low, FSR on, msaa 2x and was only able to get 45fps with reprojection, which would often drop to 33 in low level flights such as the f16 syria and ah64 marianas above.

Thanks, didn't think about setting a custom curve. That works, so all good.

Hi all - I have a WW Orion F16 throttle and have it turned for AB to line up in game. AB kick in correctly on F16, F5, F18. But, on the Mig where other jets are 100% throttle, its only 90% and i have to push into AB detent to get to 100%. Is there something I"m missing as I thought AB was configured globally in the sim but the 21 seems different. Anyone else seen this/know how to fix?

In case anyone else runs into the issue I had, removing the small (2) deadzone I had put for the collective axis controls eliminated the issue, trim now works correctly.

I've got my special settings set for the recenter stick, but for some reason while my rudder holds trim perfectly when I do force trim, my cyclic does not. It still responds to inputs and just treats the position where I hit force trim at as the new center of the stick. This means when I trim to forward flight, recentering my stick causes the nose to massively pitch up. Is anyone else having this issue?