Qcumber

I had not seen that. Good call. Does it work now and does it negate the need for DLSSTweaks? Edit: just looked at the NVIDIA brief and it looks very promising.

@Hippo Is it worth renaming this topic to "NVIDIA 5000 series and DLSS4 for VR" or similar for a wider discussion?

Does anyone know if the new "AI texture compression" will work with DCS or is this more marketing bull? "Still worried RTX 5000 GPUs don’t have enough VRAM? Nvidia’s secret weapon is powerful AI texture compression, and it’s calmed some of my fears | TechRadar https://search.app/uXGFMf9XbA2H3psn6"

Not immediately but I think you can still manually install it. No frame generation though.

I now don’t use any AA at all. I push the resolution up a bit in the centre (QVFR) and minimal sharpening and it looks pretty good. Yes, there is some shImmering low down but even DLSS does not remove this. I find that sharpening makes any artefacts look worse.

I will of course give it a go as soon as it is out.

Yes. A 13900k is likely to have plenty of headroom alongside a 4090 so not surprising that QVFR works well for you. The 5800x3d is a good CPU but not as good as the 13900k.

Not with a 4090 and a 5800x3d. It's better to use DFR/FFR from OXRTK with that setup.

With your setup you will not get any benefit from QVFR. It shifts a lot of the workload to your CPU. I have the same CPU but a 4070 so I see a big improvement. With a 4090 you will just get a CPU bottleneck.

Is there anything else using the network channel? One trick is to make a Faraday cage from foil and screen out everything other than direct line to your headset. I have recently been using an ethernet link to the headset which requires an Android edit but gives me a very stable connection at 400mbps. Not sure if that is possible for the Q3. If you have not already done so it might be worth asking for help on the VD Discord channel.

What is your video encoding and Bitrate? It would be worth posting a screenshot of your in game overlay. Are you using reprojection?

I normally use sharpening in OXRTK. This allows me to change it on the fly. I found that if I set sharpening to zero the ghosting is less. However, I find it a bit too blurry.

Not sure if you have tried this but turn off Cockpit Global Illumination and Anisotropic Filtering, set Terrain Object Shadows to flat and set Water to Medium.

I have used it with my Pico 4 in fixed mode and it works very well. Give it a try. You can push the central resolution up quite high and also get a decent performance boost.

DLAA/DLSS is great for sightseeing low over cities but crap for close dogfighting. Too much smearing and ghosting. Even with 3.8.10 and preset E/F.

Have you tried using Quad Views Foveated Rendering? It should give you a big performance boost.

I don't use any AA either. Much better performance. Even compared with DLSS.

I use very little sharpening. Just a small amount of CAS in OXRTK.

I think you are misquoting this. It refers to the "unadvertise" function. "unadvertise is a value 0 or 1, where 1 will disable quad views. This option is meant to be used within an [app:] or [exe:] section. Note that this option does not work with DCS World." Turbo mode is identical to the one in OXRTK and can be enabled in QVFR and in OXRTK. It works fine in DCS. I use QVFR and OXRTK for easy adjustments of sharpening, toggling turbo mode on/off and to add post processing adjustments.

I use both. Overall there is very little difference between the two. I find that image quality is slightly better with meta link cable. Eye tracking might be very slightly better with VD. VD has some slight lag when moving your head quickly; you can see black edges which I don't see with meta link. VD reprojection is inferior to ASW. Although VD has more video encoding options, I find that h264+ gives me the best performance/quality. With wifi I can only manage a stable performance at 200mbps. With the ethernet cable I can max out at 400mbps. With meta link I can max out at 960mbps. I had hoped that QVFR would be incorporated into VD but it looks like this is not going to happen now. I prefer using meta link but I keep up to date with VD as there are sometimes issues with meta updates. Edit: I have retested this and am now erring towards VD with ethernet over meta link. The performance is so much better at 400mbps and very stable. The VRAM usage is also significantly less than with meta link.

Some maps are better optimised than others. For example, the Normandy 2 map runs very well for me, similar to Caucasus. The Channel map, however, is a real performance hog, despite the same terrain. It might be the trees but I'm not sure. I tried reducing the tree quality and draw distance to minimum but it didn't make any difference for me. Over the large islands FPS is the worst. Over the sea it's great. I am hoping that Marianas will receive some performance improvements with the WW2 update.

If the FPS is below the refresh rate you will always get stutter. I would advise not attempting 90Hz and try for 72Hz. As ischicopter says, if you use ASW it is better to control this via meta. I use OTT to set keybinds for the various ASW settings.

I would advise starting simple. Set PD in game to 1. Turn of all AA settings. In oculus link set the scaling to x1 and 72 Hz. 90 Hz is too much. Use either oculus debug tool or oculus tray tool to supersample to about 1.5 and see how the resolution looks. As has been mentioned above you can use QVFR to reduce the peripheral resolution. Default settings should be ok to start with. Once you have a good balance between quality and performance you can start playing with sharpening and AA. I have a Quest Pro and a 4070 and get very crisp views in the spitfire N2 free flight alongside the B17 with steady 72 fps and about 70% GPU utilisation. You should be able to get the same.

The "./" one worked for me. When I tried before I couldn't get it to connect to the headset. Your instructions are very good so a lot easier. It took me less than 5 minutes to get up and running.

Got it working and eye tracking is definitely better. I am also getting 400mbps with a very smooth experience. One step I did not see on your list though is that I had to confirm connection on the headset before I could run the code.