Qcumber

For me fps goes up over cities irrespective of whether QVFR is enabled or not. It might be a relatively higher increase than with no QVFR enabled. However, if I fly at full headset resolution across the whole frame(s) I am stuck to 36 fps if I am lucky.

This thread is useful.

That's because you gave a 4090. I have a 4070 and a 5800x3d so have much more CPU headroom than GPU. QVFR utilises more CPU use and therefore takes some of the pressure off the GPU. I can maintain 72 fps in most situations with about 60-70% GPU use. Most of my CPU cores are running at about 60-70 too. With a 4090 OXRTK DFR will give better FPS. If you paired it with a 15900K maybe QVFR would be the better option

I don't have any issues with the most recent Nvidia drivers.

It very much depends on your hardware. For my setup QVFR is far superior to OXRTK DFR. I can keep 72 fps most of the time over Cairo with QVFR. With OXRTK DFR I struggle to get 50 FPS. With no FR I am lucky to get 36fps.

DId it OXRTK FFR work for your current system before you tried QVFR? QVFR shouldn't have a visible rectangle if it's working properly. Do you mean that there is a harsh transition between low and high Res areas? If so you could try increasing the border size. This gives a graduated transition. Also make the centre high Res area larger then you don't really notice the periphery.

It still works for me. I don't remember having any issues with DCS updates. Maybe something else you changed about the same time?

Is this compared to meta link? As per my post above VD is a great app but you cannot directly compare the two unless you have used the same super sampling etc. If you have not already done so, try using meta link with open XR toolkit SS to 1.5 and bitrate to 960 mbps. I use both on a regular basis and at the moment I think that meta has the slight edge. Next month might flip back to VD. The difference is that close.

Overall they are very similar but to compare them properly you need to make sure you are comparing like for like. For example Godlike gives you supersampling to about 3300 pixels. Link cable/air gives you a max output of about 2700. You can use Oculus tray tool to set the SS to about 1.5 to give you a similar meta resolution to VD godlike. If you do this though I would advise setting the supersampling in the meta app to x1 so that you can more easily keep track of the scaling. I hope this all makes sense. With VD you will need to play with the codec a bit and optional mise the Bitrate to keep your latencies down.

By Meta Virtual Desktop, do you mean this app? https://www.vrdesktop.net/ If so then you can toggle between the virtual space and DCS VR by double pressing the left control button (3 lines). I would advise following all the set up advice on the VD discord for best performance. https://discord.gg/VPXjh9SJ

I use JoytoKey to enable HOTAS binds to centre and offset the cursor then I can easily look anywhere in the cockpit. I have a "finger mouse" strapped to my joystick so that I can easily interact with switches etc without needing to take my hand off the stick to reach the mouse.

What do your latencies look like with a reduced Bitrate?

Yes. East Anglia, Netherlands, Belgium and Western Germany. The US planes are ready there for that. I would like to see a P-38 though. Good for WW2 PTO too.

In addition to WW2 Marianas map, F4U and Hellcat, I would like to see a K4 refresh. If a Balkans map is coming I would love a WW2 version too. More wishful thinking would be a WW2 Sicily map covering Southern Italy and coastal Tunisia. A similar size to Syria or Sinai with about 70% sea.

Nnnnnno!

I have seen this a few times. For me it seems to be related to having ASW enabled. If I take the headset off and turn ASW off it seems to resolve.

@johnbowzer I would agree with slughead. It sounds like latency issues, probably the decode latency. Please can you post a screenshot of the VD overlay?

Have you tried XR necksafer? https://gitlab.com/NobiWan/xrnecksafer

The aim of these changes is first to see the best clarity of objects (as per op question), then to optimize for performance. DLSS is not a good option for clarity of objects. You need to find the right balance of SS, AA, refresh rate and game settings that works for you.

Try pushing SS higher. Turn off any antialiasing. Are you using any sharpening?

2024 has been a good vintage. A fine, acquired taste, which might not be for everyone. I'm looking forward to the 2025 harvest (although my wallet isn't; it's already hiding away somewhere).

You are really pushing the limits on your system. The decoding latency is very high. You want to keep it below 12 ms. Try using h264+ at 200. You could also reduce refresh rate to 72 Hz that would then allow you to increase the supersampling to 1.3 or higher. Then see how distant objects look. What AA are you using?

Thanks for the F5 update. It's my favourite jet. When you fly in VR the cockpit is not great so any improvement is greatly appreciated. Can I please ask that you do the same for the K4? It's my favourite prop plane. Even better, give us a 109 G6.

Looks amazing!

Spotting dots?