Qcumber

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.

If you use Oculus Tray Tool you can set key bindings to disable auto ASW or to force to 36 fps plus other options. However, if your system cannot sustain 72 fps, and you disable auto FPS, you will get sub 72 fps which is likely to cause stuttering.

I also had this issue but appears to have gone since the last meta update. At least with meta link. I still have issues with VD. I might try disabling hand tracking and retest VD.

Just adding to what I said earlier. I switch between DLSS and no AA quite a bit. See if you can cope without AA. It depends on the situation. For me it looks ok for altitude with fast moving targets. DLSS can have ghosting in these situations. If I am running low and slow then DLSS works quite well.

There are issues with OXRTK and QVFR since the last update. Try disabling all open XR layers except QVFR. MSAAx2 is quite taxing. Have you tried DLSS recently? It is a lot better than after the initial introduction. I use DLSS tweaks to change the preset to F and adust the quality scaling to 0.9. Consider changing clouds to medium. Ultra is quite taxing. I have also had lots of issues with VD since the last update and have been using Oculus link.

Quest Pro is my choice. If you have a mid to low end system it's great. Eye tracking makes a big difference on GPU performance with a moderate CPU. And you can get one for the same price as a Q3 if you look around. I got mine 2nd hand in new condition for £300. We need a Q3 equivalent with eye tracking at a reasonable price.

Thanks. I have tried that option before but did not seem to make much difference. Could be worth trying again though.

I tried the hot start in the F4 on Kola just after the update. It was terrible 25-32 fps. I then noticed some issues with QVFR even after disabling OXRTK etc. the eye tracking did not seem to be working properly. I ended up reinstalling it and ran it again yesterday. 72 fps 90% GPU use. Very smooth. QP with quest link cable meta set to resolution x1.3. QVFR 1.4 centre 0.4 edge, 0.3x0.3. DLSS preset E with 0.9 scaling. Edit: spoke too soon. In more challenging situations everything crashes. I think it might be VRAM overflow.

The scaling is separate from the presets. The presets are described here: https://developer.nvidia.com/blog/nvidia-dlss-updates-for-super-resolution-and-unreal-engine/

It's the level of upscaling applied. 1.0 is no upscaling so is essentially DLAA. 0.5 would upscale the image from 50% using the DLSS (Deep learning super sampling) technology to full resolution. The more upscaling is applied the more the image can degrade but gives you increased performance.

Thanks for the correction.

The default setting for DLSS quality is a scaling of about 0.66 and preset E. With DLSS tweaks you can change the scaling and the preset. Preset F appears to be the best one for DCS. I find that a scaling of 0.9 gives identical quality to DLAA but slightly better performance. You can get away with 0.8 as well.

You already have a 4090 so combined with a 13600 you will not likely see much gain. QVFR works better when you have lots of CPU headroom. I see a big improvement with my setup.

The current advice is not to use OXRTK as it appears to cause a lot of issues for some people.