Sr.

Just submitted pre order... arriving May4th Will come back with review.

I'm playing around with Process Lasso... is there a magic number of cores I should assign to DCS.exe on a Ryzen 5600X 6 core?

Could even be a blob of solder flux paste, misplaced during assembly. Considering the heat inside there...

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.

Noted the date/time for the P-51 Free Flight over Poti (where I first noticed it.) 1/6/2011 09:00:00 After failing to find it in a few other aircraft/maps, I tested other maps and set their date/time to 1/6/2011 Turns out... it's the moon. P51 free flight over Poti.trk options.lua

Turned on occlusion and flare. Still there just harder to see. Maybe the sim engine adjusting for daylight saving time

I don't use flare, occlusion etc. Will try it on.

flex Damn... cockpit looks awesome in VR.

Noticed this earlier while flying the P-51 around Caucuses.