WipeUout

Sound like something is filling up over time. Did you tried various setting for the terrain preload slider? Also consider checking if your GPU is in MSI mode. You may want to check also if you have the same issues with any of the texture settings. Also, where is your DCS installed? having DCS on a separate M2 drive from your Windows could help.

Do not mix QVFR settings and pixel density, or ''render quality'' in Pimax client, these are two different things. Go back to the video and read the bottom comment, you will see that with the 2060, they lower render quality to 0.5 which means 25% of the native resolution. QVFR default settings will keep the focus area to 100% of the set resolution and the peripheral area at 50% of the resolution, that resolution is defined by other settings such as render quality in pimax client and/or pixel density in DCS. There is not doubt that QVFR does a superb job at incresing FPS but reducing the rendering resolution with a 2060 is probably the only way to reach 60 FPS!

If you take into account the rendering resolution drop to 0.5, this is a reduction of 75% of the pixel count. I think it looks plausible but the image quality must suffer a lot.

When a mission has no clouds or preset selected, there are high altitude clouds showing on and off. Whenever I switch from external to cockpit view, the high altitude clouds paterns change and sometimes they go away leaving a perfectly clear sky. Is there a way to stop this random ''high clouds on/off'' behaviour? Is it possible to have a clear sky throughout the mission?

If you mean that you see a border between the inner high resolution portion of the image, and the outer low resolution portion of the image, then yes this is a reported issue. It is more apparent in some modules such as the F-16 (for me) and even sometimes more visible on the left side than the right side. Unfortunately, this is a problem related to DCS, not OXRTK or QVFR.

+1 QVFR is providing even more performance than OXRTK's FFR. Given that VR is demanding so much, this tool should be part of the baseline!

I would like to share my optimization journey for my 8KX. Although not able to use DFR, FFR works quite well with this HMD. I have been using OXRTK FFR and was getting about 1.5ms shredded from my average GPU frametime consistently. First time I tried QVFR, I did not get such a great result with default settings and never thought about playing with settings. I revisited using QVFR a couple of days ago and got incredible results of over 2.5ms improvement with an even better image quality. I have tweeked settings as follow: For the HMD smoothen_focus_view_edges=0.2 sharpen_focus_view=0.8 For DCS turbo_mode=0 peripheral_multiplier=0.4 focus_multiplier=1.4 horizontal_focus_section=0.35 vertical_focus_section=0.45 Horizontal focus may seem small but with the 8KX wide FOV (normal at 140 deg.), I barely notice the blur on the sides and get tremendous performance uplift. Image has never been so clear and crisp and I believe that the 8KX is still not at the limit of what it can do. I use DLSS balanced and the result is amazing. Still some issues with MFDs but overall excellent. Thanks @mbucchia!!

Had awfull stutters and even crashes until I found out that my overclocking software was the cause (intel Xtreme on auto-OC). If you use such OC application, try to suspend/remove and see if it is the cause.

I see similar results when comparing Caucasus and Persian Gulf. DLSS seems to provide a bigger performance boost on busy maps such as flying over Dubai in the Gulf map but also with increased smearing. Flying over Caucasus with DLSS provides very limited performance gain in contrast, but also much less smearing.

I can speak to this coming from a Pimax 5kS up to the 8kX. The increased resolution brings down shimmering to a tolerable level on the 8kX with less impact than using MSAA, at least that was the case for DCS 2.8 and previous. There is still a long ways to go to get to a point where resolution is enough to counter shimmering, which I guess would be around 60 to 70 PPD. Nervetheless, image quality is very personnal. I find that using DLSS is an acceptable compromise to trade some sharpness for an increased performance and almost no shimmering on busy maps.

I have been experiencing major stutters and the sim crashing as soon as I would try to engage DLSS / DLAA / TAA after a few seconds. I tried various combination of PimaxXR/Pimax Client / Quad views on/off etc... Sometimes, the stutters would go away butg after a few minutes woudl intesify. Until I started to stop all overclocking and found out that the Intel Extreme Tuning Utility was the culprit. It was set to automatic OC and it does not play well with DCS 2.9. I have not checked if the OC is set to specific values it would work, but for sure when in auto OC, it does not. Now I am experiencing the most fluid and smooth siming ever. DLSS is a bit blurry but so much smooth that it is worth the compromize for me.

You can also reduce DCS setting gamma to 1.3 and boost your HMD backlit or brightness or both (if applicable). Using also the sunglasses in OXRTK will reduce haze a bit.

@Sr. This looks like a corrupted config file in your "Saved Games\DCS" folder.

The Crystal has two tracking options, internal or lighthouse. Controllers are not required in DCS.

If you go fresh install, follow FR33THY's videos on youtube, very well optimized method for gamers:

Look here:

Did you check your DCS log to see what is happening before the crash to desktop?

Very puzzeling. I guess you already tried to plug your HMD in different display port connector on your GPU? Or tried the HMD on another computer? Or tired with an older GPU? I did have a similar problem with my 8k+ and the cable had to be replaced, but if you tried with two 8kX with same result, the problem has to be computer hardware or software related.

Send your video to Pimax support, you might have a cable problem.

Tracks made in VR must be replayed in VR, there are no way around. Else, re-do your track in 2D and it will be fine on replay (in 2D).

I believe that Valve index does not support OpenXR natively. Have you followed the instructions in the first two posts here:

If you are using Pimax Client 1.16, it might be the problem as 8kX owner are reporting issues. Try rolling back to 1.13.

What version of Pimax Client / PmaxXR / OXKTK are you using? I use Pimax client 1.14, PimaxXR 0.4.0 (Have not tried 0.4.2 yet), OXRTK 1.3.2. It is the most stable combination at 90hz. Also, if you use turbo mode in OXRTK, it may bring instability.

This is already reported and being investigated. Go to the VR bugs section to see progress:

Interesting question. I tested both DCS PD and OXRTK at the exact same super sampling value and they are both performing the same, PD=1.1 in DCS and 10% more resolution in x and y values in OXRTK with a result of average 9.14ms and 9.16ms respectively in GPU frametime in my test track. The only difference is the granularity that OXRTK offers. In DCS with the PD, you are limited to 10% increase in each axis as opposed to OXRTK where you can increase by one pixel at the time. Much more precise but also much more time consuming finding the sweet spot.