Qcumber

Fair point. But just offering my personal opinion based on my own experience. You also don't need to spend huge amounts to play DCS in VR. The P4 is quite a lot cheaper than the Q3.

I thought Reshade had performance impact.

The main reason I used OXRTK is for easy sharpening and for the brightness/contrast/colour settings etc. It still has a place but it seems to cause problems for me since the last DCS update.

Turbo mode can cause issues with meta link. It messes up with my setup anyway. It works well with Virtual Desktop though.

I have used both the QP and P4 and they are both good headsets. The reason I ended up preferring the QP is eye tracking. I used the P4 with fixed QVFR and it's pretty good. If you can find a QP for the same price as a P4 then get that. Otherwise try a P4.

I think this can make a big difference for full resolution across the whole FOV. However, with QVFR reducing the FOV has no noticeable effect as the peripheral resolution is so low.

I have tried this and it really messes up QVFR with eye tracking.

Do you mean the Pixel Density slider in DCS? If so, leave this at 1. Try to keep any supersampling in one place otherwise you can get very lost in settings. For example, with my Quest Pro I keep PD at 1 and use QVFR to increase the centre resolution to about 1.6.

It's working ok for me in VR. What is your setup?

I'm using the latest meta ptc. It works ok for me with hand tracking enabled for meta link but with VD it kept freezing. I disabled it today and VD now works ok. There are so many changes it could if course be coincidence. Now I need to re-enable hand tracking and try VD again!

@Phantom711 So I tried disabling hand tracking and VD now works flawlessly! Back to using VD all the time again.

Glad it's working for you. Hopefully it will stay that way.

I love flying the K4. It's my favourite DCS plane.

No

Are you saying that Q3 is the better standalone headset over the QP? That might be true but for someone with a mid tier PC the QP wins for me when it comes to DCS.

I have had issues with OXRTK and no longer use it. It would be worth trying running without it. Just to clarify open XR is the API not the runtime. The runtime is Oculus link or steam VR.

I would agree with VR Flight Guy in PJ Pants. Oculus link and VD are comparable with oculus having a slight edge, but not major difference. My only experience with DP connection is with my rift s. Obviously the quest Pro has better visuals due to higher PD. I don't notice any compression artefacts with QP Vs rift S.

Are you using any open XR layers such as Open XR toolkit or XR necksafer? If so then disable them all as there have been issues with these since the last update. This is a useful too to monitor which layers are active. https://github.com/fredemmott/OpenXR-API-Layers-GUI

I am not sure what you mean by this as DCS uses open XR as the API even through steam VR. Do you mean that you are using steam link rather than meta link?

QVFR in DCS does not just affect spot size. The low res area also impacts on shadow quality so there is often annoying flickering when quickly moving your eyes. I think the two are related. I've just learned to put up with it but am hoping that it will be better with future developments.

Yes. This is a pain. I think it is because DCS tries to assign dot sizes according to resolution rather than a fixed size. There is a lot of discussion on the bug section. @BIGNEWY Sorry for the ping but is this issue something that the devs are specifically addressing? I suppose the immersion could be that it mimics seeing something out of the corner of your eye.

I think @mrsylvestre advice is good. I used to use a powered ethernet adapter close to my pc and a long usb cable. Very good and consistent bitrate with VD. @ShermanTank In terms of AA there are a few ways to approach this. The first is reduced resolution and use MSAA. The second is to push the res higher and use DLSS. The third is to use higher Res and no AA at all. Try QVFR in fixed mode but push the centre Res up to an equivalent of about 4000 pixels (Godlike x1.2) at 0.4x0.4 centre size. Periphery at Godlike x0.5 That will help reduce centre aliasing and will look better with DLSS. I alternate between no AA (altitude and fast action) and DLSS (low and slow). This is because DLSS can induce blurring and smearing with fast moving objects.

What settings have you tried so far? Are you using Pico connect?

You can set a maximum FPS in DCS but I have personally not found this useful. I aim for 72 FPS and toggle auto on and off depending on my needs, sometimes down to 36 with reprojection (ASW).

I used to cave a Pico 4. My setup was to use Virtual Desktop set at "Godlike". For VD you need a dedicated router with a direct ethernet connection to your computer. Pico connect did not used to be very good but there are some recent reports saying the last update is much better. To best help it would be useful to post your pc setup.