MIghtymoo

Awesome news! Perfect for us VR pilots.

I have had issues running Virtual Desktop in VDXR mode without severe stuttering. Had to use SteamVR. With the release of 1.29.8 version all is smooth. Finally got rid of SteamVR

He is playing on floppy discs...

Try a full recalibration of the rudder pedals in the VPC Configuration tool.

Be careful with the QuadViews on the Pico. When comparing foveated rendering in OXRTK with QuadViews, I saw a big increase in CPU frame time with QuadViews (from 6-7 ms to >10 ms in demo track). This is on identical replay tracks (Syria, low flying over city with Apache). My specs below.

I am running with a 1200 Mbps connection to my Pico 4 with a WIFI6e router. Still running 5 Ghz band (not to be confused with 6Ghz band).

Hope the VR performance will be better than South Atlantic map.

This is good news. Pictures looks great!

Then you are running a resolution of 5304x 5304 in the centre and 1248x1248 on the periphery in Quad view. I am running 4000x4000 in the centre and 250x250 in the periphery (outside visible image) with OXRTK foveated. I assume you the run with reprojection at 45fps. I aim for 72fps… A brand new youtube video recommeded VD Medium (2016x2112) and MSAAx4(!) to get 72 fps. Same Pico 4 headset…That recommendation would make no sense with our prefered resolution. See how knowing the resolution makes comparison better and easier

If you want to compare results and quality with others, you need to give us information about your resolution Both PD in DCS and Quadview are multipliers, and makes no sense if we do not know the resolution. I give an example (not my real settings ) I theoretically set resolution to 2160x2160 in SteamVR and PD 1.8. This is a resolution of 3888x3888. I am super happy and share on the forum. If you use resolution 3850x3850 (default for Godlike in Pico 4 in SteamVR), and decide to use my «awesome» PD 1.8, you end up with 6930x6930 and the frame rate and experience will be terrible. ———— Changing multipliers in two (or more) places makes it even more confusing

I can agree with Qcumber here when it comes to AA methods. I do not like DCS Pixel Density(PD) adjustments, as it does not show your real resolution. It works as a multiplier to e.g VD / SteamVR. Makes it harder for others to compare. Better to adjust the absolute resolution in appropriate tool (for me either OXRTK or SteamVR). Also I use foveated rendering via OXRTK, instead of using Quad views (DFR), as I have a powerful GPU. But for any headset with eyetracking Quad views is the way to go!

It is easy to get lost in all the settings... The reason for your poor performance is most likely this: You have both set a resolution of 4200x and and in additon added a PD of 1.5. So effectively you are asking the GPU to render at 6000x(!) You should easily see 72fps with your setup if you use settings in my post and the DFR (eyetracking):

It does, but it will be less and less noticeable the higher the resolution. As with everything, it is a trade off. For example: You will never get as sharp MFDs in DLSS as with TAA. But they are sharp enough for me. I recommend to change the resolution just one application (and not mess with PD as a multiplier)

It depends on the era being depicted in the map. The museum was opened in 1994.

The PD can be confusing as it is a multiplier for whatever resolution is set for DCS elsewhere. It is probably better to set the desired resolution in relevant application (for me either SteamVR or in OpenXR toolkit). I have a Pico 4 headset and for that headset it seems to be optimal to set the resolution to around 3850x3850. Start with default resolution and review the image sharpness. If you think the MFD text is a little blurry, increase resolution 10% and try again (I delete fxo and metashader folder each time since I change resolution). Repeat untill you are happy with sharpness vs performance. When it comes to graphics, there are a few settings that make a major visual impact in VR. 1. Visibility range (High is the best option as on Medium trees and buildings are not drawn/visible until very close). 2. Flat shadows give that extra depth and make the flight «more alive», without the heavy GPU hit of Default (which also does not look as nice due to flickering/artifacts, IMHO). 3. DLSS quality is golden for VR. Tests on a busy Syria map yesterday with the Apache got the following results (averaged): - No AA: 70 fps - MSAAx2: 60 fps - MSAAx4: 40 fps (!) - TAA: 65 fps - DLAA: 60 fps - DLSS Quality: 85fps Other than that I like to have shadow quality to Medium as it gives a very nice effect in the cockpit. Clouds to High. Rest is honestly just minor impact eye-candy that I can not afford to get a stable 72-90 fps. Good luck getting the optimal settings for your setup!

You need a fast CPU to maintain 90 fps across the board. I upgraded from 10600K to 13900K and all my stutters/reduced fps with the Apache disappeared.

1. You can get a new RTX 4090 for around 1800 Euros. 2. Agree that you do not need a 4090 for any VR-headset on 45 fps... For anyone considering entering the world of DCS VR, it's crucial to emphasize that a superior VR headset alone won't guarantee a great experience; a powerful PC-rig is equally essential.

A Varjo Aero with base stations are not that much cheaper that a RTX 4090. And with all due respect an RTX 4090 outclasses an RTX 3080 when it comes to VR performance. My point is, spend money on a good PC-rig before buying high end VR-headsets...Both is the best (if you can afford it).

No one is mentioning Pico 4? Equivalent to Quest 3 and you can get them dirt cheap used. Got mine for 180 Euros and just love it. You get much more out of your VR experience with a RTX4090 and a Pico/Quest3 compared to keep an older GPU and go for a VR-headset with DFR. Basically you need great HW to have a really good VR experience, regardless of headset... Good luck on your VR-adventure.

Turn on the "Advanced FPS" in OpenXRToolkit and check your CPU and GPU frame times. Your CPU is relatively old/slow, so I suspect there may be some CPU issues with the more CPU intensive KA-50 (compared to the F3C Mig-29)

Depends on your GPU. You have a pretty beefy GPU. I am running 3850x3850 and can have both HIGH visibility range and FLAT shadows ans still stay comfortably above 72-80 fps flying low over a big city in Syria in the Apache (mission with lots of active AI units). When I go to 4200x4200 I must decrease the visibility range to MEDUIM.

The Apache is a CPU/GPU hog, but very enjoyable in VR.

What resolution are you running?

Very strange. DLSS Quality looks very good if the resolution is high enough. MFDs looks great. I am not able to see noticeable difference from DLAA, but with +15-20fps in bonus. Can read even the small text in the Viggen cockpit

It depends on your headset and how clear you like the picture. You can be more agressive on settings with Fresnel lenses compared to Pancake lenses. Tip how to adjust: Adjust the outer ring first. Resolution set to 1/16. Adjust intill ring is very barely visible on the image. Adjust inner ring by setting resolution to 1/16 (makes it easier to see adjustment). I adjust it about 10% into the frame and when happy change middle resolution to 1/2. You need to decide what you like. I like to set Prefer vertical resolution Example menu below (not my settings):