Qcumber

I use a 4070 with hevc so I would say yes.

With your setup I would suggest using QVFR. Slughead's high end setup does not need it but you might see a noticeable improvement.

I would advise posting your log file in a new thread in VR bugs. Then DCS devs can review it.

Here are my settings. QVFR config: # common settings for all headsets (unless overriden below). smoothen_focus_view_edges=0.1 sharpen_focus_view=0.3 horizontal_focus_section=0.3 vertical_focus_section=0.3 peripheral_multiplier=0.4 focus_multiplier=1.6 debug_eye_gaze=0 debug_focus_view=0 turbo_mode=0 # Fixed Foveated rendering settings for fallback when eye tracker is not available. horizontal_fixed_section=0.5 vertical_fixed_section=0.5 DCS settings: null I have just seen that you have a 4090 so I don't think you will get much from QVFR. I think you would need a more powerful CPU. The 5800x3d gives me lots of headroom with a 4070.

Just fly for a while and enjoy the experience. Then you can tweak things a bit more once you get a better feel for things.

I can get pretty clear cockpit visuals with VR. Not 4k but pretty crisp. The acid test is lean forward. The cockpit should match flat screen at close range.

I'll post my settings later.

Setting for VR is a very long trip. Be prepared for frequent tweaking. My experience over the last couple of years is that the DCS VR experience is getting better. But every update requires some retuning.

Good point. Should be 1.3 but the final resolution is the same.

OK. You have VD set to Ultra. Try Godlike. Make sure bitrate is set to automatic as it can lead to stuttering if it's higher than your router/setup can manage. Don't limit the frame rate in OXRTK. In fact for now don't use OXRTK at all. It still has some uses but not many and will just make for more complications. There are no magic settings with NVIDIA control panel. Start with everything at default for now. In VD your game latency is a bit high. Aim for something below 10. You haven't shown your DCS settings.

Good point. There are a couple of ways of working this out. The first manually. Check what the resolution slider is set to in meta link software. It looks like the image below Make sure the slider is set to the right so 1.5 resolution for a total of 2704x2896. VD godlike is 3072x3216 so you need additional supersampling with meta. You can do this using oculus debug tool (ODT) or oculus tray tool (OTT; Google them for instructions). If you multiply the resolution by about 1.15 you will end up with Godlike. With my Quest Pro I use quad view foveated rendering (QVFR) to SS rather than ODT. I set the centre resolution to about 1.5 which gives me the equivalent of about 4000x4000 pixels but only over an area of 0.3x0.3 of the screens. The periphery is set to 0.4 so about 1150x1150 pixels for the whole frame. Setting the centre to high supersampling negates the need for any antialiasing (at least it works that way for me). PS: Don't use 90Hz. Stick to 72. I borrowed the image as I am not at my computer.

That's probably because your resolution setting is higher through steam. For a real comparison you need to make sure that the output resolutions are the same.

I have the same spec PC as you and used to run a Pico 4 using virtual desktop. I now have a Quest Pro. My advice would be to first keep your set up as simple as possible. Use meta cable link and push the resolution slider far to the right max resolution. Don't use anything else at this stage. Set most DCS settings to medium and see what the quality and performance are like. Don't use any AA yet either. I think you will get about 72 fps high up but will need to use ASW when near the ground. If the quality still looks poor then use Oculus Debug Tool or Oculus Tray Tool to supersample in stages, starting at 1.1. each increment will reduce performance. This is where you can try to get the balance between quality and performance. I would suggest using QVFR in fixed mode for a big performance boost.

If your CPU is half decent and you have a mid range GPU then QVFR is better. I did a quick comparison today. With QVFR the GPU load was about 70-80%. FPS steady at 72 fps. The same scenario with OXRTK foveated rendering the GPU load was about 85-100 with frequent flips to ASW 36 FPS. Scenario F-16 free flight Syria. I can post my settings if needed. They were the same for each test.

I don't think that AMD GPUs are supported for OXRTK foveated rendering. You would need to use Quad Views Foveated.

You need to make sure your meta output resolution matches VD on godlike otherwise it's not a fair comparison. QVFR works with meta open XR. You don't need VDXR. There is a setup guide on the QVFR website.

That is not officially supported by VD and does not work with all headsets. I used to use it with my Pico 4 and it was very stable, but it does not work with Quest Pro.

QVFR works very well with meta link cable. Performance is the same. Quality is almost identical, although there are subtle differences. Meta has a slight edge if you can push the bitrate over 500mbps. I can get mine up to the max of 960mbps.

I have got it working now but thanks for the help.

I used to run a Pico 4 which has similar resolution to a Q3. With your specs you will need to use fixed foveated rendering to get a decent performance. I can run a Quest Pro with a similar spec pc to you. It runs very well. 72fps and about 70-80% GPU use in most situations. You could try buying a QP instead. They are a bargain used or even new on eBay. I got mine for £300.

VR settings can be a pain but they are much easier these days. Keep it simple and start clean. Disable OXRTK and just use QVFR for supersampling and sharpening. You can edit the config file for settings or use this tool. https://www.digitalcombatsimulator.com/en/files/3332882/ I set my centre resolution to 1.3 with size 0.4x0.3. periphery set to 0.4.

Make sure you follow all the setup tasks in the guide. There is an additional step to enable eye tracking with meta. https://github.com/mbucchia/Quad-Views-Foveated

Unfortunately no eye tracking or display port.

Reports of a revamped Pico 4 for launch late 2024 or early 2025. https://www.techradar.com/computing/virtual-reality-augmented-reality/this-leaked-meta-quest-3-rival-is-more-powerful-but-it-needs-one-thing-to-truly-beat-metas-vr-headset

H274+. I have a Quest Pro