Sr.

was reading through the changelog, seems the name has been changed to "over-prediction."

Reverb G2

1.30 I believe https://mbucchia.github.io/OpenXR-Toolkit/ Not to be confused with OpenXR Tools For Windows Mixed Reality

I run it about 70%

I wouldn't know without tearing one open but, to be honest it wouldn't be a bad idea for protection against corrosion on some of the more fragile connectors considering the amount some people sweat while wearing one on their head for hours. Again, this is just a guess. If it is in fact dialectric grease, maybe the assembler used more than necessary. Might be worth a look.

Only thing I can think of is, dielectric grease seeping out.

You need OpenXR toolkit... then enable the shaking reduction. Not a good combo when using motion smoothing though.

I have 2 of these, never had an issue.

I've wondered this myself numerous times.

Changes in v1.3 (Mar 2023 / v1.3.0 -) Add chromatic aberration correction for Varjo Aero (reduces red color depth inconsistency, precludes usage of post-processing like sunglasses) Contributed by Bernhard Berger, thanks! Add foveated rendering support for Quest Pro Warning: there are bugs in the Oculus software that prevent using the eye tracker on PC for some users. If you are experiencing issues, check your OpenXR Toolkit log file for the following error message: Remove resolution override cap on Pico (was limited by SteamVR) Make resolution override use the height instead of width as reference (allows to change FOV on Pimax) Rename “Shaking reduction” to “Over-prediction reduction” and reverted behavior to version 1.1 Some bug fixes related to foveated rendering with Direct3D 12 Some bug fixes related to Turbo Mode Add a command line option to alter the over-prediction reduction value Fix an issue with foveated rendering that caused blocky clouds in iRacing Fix an issue when using OpenComposite with Vive Cosmos Fix an issue when running non-Direct3D applications (OpenXR Toolkit will not be enabled) Add an automatic check for updates in the Companion app

Curious if after switching it ON, you performed a power cycle? Not simply a reboot.

Just so I'm clear... you had to switch hyperthreading to OFF for an 8 core processor?

Did yes... I even cleared the SavedGames shader folders and reset the shader cache on my GPU.

I can't say either way. But what I can report is, yesterday I changed my options from Texture High to Medium, and Terrain Texture from High to Low and saw 0 change in frame rate or fps. Barely noticeable differences visually. Left me wondering if any actually changed.

This all I get

For you guys who like tuning and knowing what's going on with your system, primarily your CPU now that your tuning for MT... Check out Quick CPU. Gives a ton more info than Windows Resource monitor. https://coderbag.com/product/quickcpu On first launch, verify these sliders are at 100%.

I tried using these and get a DLC not authorized message at startup.

flex Damn... cockpit looks awesome in VR.

yep

Last time I looked, mountain object shadows were still broken. Assuming we're talking about the same thing. What I see: In certain scenarios, say sun in the east, mountain between me and the sun as I fly through a valley... shadows cast on the west side of the mountain project horizontally into the air, not on the ground.

I run 60Hz, with the light sunglasses. I no longer see the 60Hz flicker most report.

I will say, while like others I didn't realize much gain on simple missions but, I DO see a great deal of improvement in the more complex campaigns and another carrier based playground I built last year. Back then, I really had to limit the amount of assets on the carrier deck to avoid horrible stutter. Last night, I added several more static aircraft and set an AWACS to taxi and take off. Not a single stutter.

Checked my pancake mode, and the difference is pretty significant. No MT: 130-170 F-16 Free Flight Caucuses W/ MT: 160-190 F-16 Free Flight Caucuses All settings maxed Still nothing to write home about on the VR side. I am curious though... while I usually run VR in 60Hz mode, tonight I was comparison testing with the G2 set at 90Hz. With nothing in OXRTK, AMD Adrenaline Edition or RivaTuner controlling frame rate, the in game counter shows locked at 45 in game, starts out locked at 90 in the menu hangar. Is there some other frame limiter in play now? And I'm not using motion repro.

Follow up: I decided to bypass the OXRToolKit and remove the --force_OpenXR option and try a few flights using only the DCS native. Since to OXRYK counters are also no available I went simply by perception and "feel", but I think it actually runs better in native mode. However; there is a strange hitch in my right lens, kind of link a random blink/flash.. mostly at the main menu. Almost like it's trying to fake some sort of motion smoothing.

Should it matter that only 6.3GB of 16GB VRAM is being utilized? As reported by OXRToolkit.