Qcumber

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

Your bitrate will ultimately be limited by the quality of your WiFi signal. The setup options often discussed on VD discord are: 1) Make sure you use a dedicated router with a dedicated channel. 2) Check your local WiFi signals to make sure none of your neighbours are using the same channel. 3) If you can't find a good clean channel then try building a makeshift Faraday cage with a cardboard box and aluminium foil. It just needs to protect your router antennas against the source of the interfering signal. The best I can get is about 350 Mbps. However I find that h264+ at 200-300 or HEVC 10 bit at 150 Mbps are very good.

Sorry. My mistake. I must read things properly. Thought we were discussing meta. Didn't mean to cause confusion.

OTT is just an interface to access most of the tools in ODT. It's a bit easier to change things. OTT has some useful custom keybind settings so I use this more. I only really use ODT to change sharpening to quality as there is no option for this in ODT.

All you are doing here is increasing resolution with one setting and decreasing width another. I would advise working out what your final resolution is and then applying a single modifier. Just to clarify how are you changing your HMD resolution? In the meta app or with OTT/ODT? I presume this is referring to QVFR? For my Pico 4 this was earlier this year and I used the same pc specs as listed below. With QVFR you can leave all SS settings at 1 and use the QVFR config file or quad views companion app to adjust central SS. For example, I have the centre set at x1.4 and the periphery at x0.4.

Use a single source of supersampling rather than multiple sources. OTT or ODT to set the overall Res. Leave PD in DCS at 1. Increasing SS will reduce the need for AA. It's just finding the right balance of performance Vs quality. I have a quest Pro and find that if I SS the centre resolution to 1.4 (over Godlike in VD) I don't need to use MSAA and it looks a lot better than DLAA. If you have not already tried then QVFR could be a good way of optimising your performance. On a Q2 this would be fixed only but I used to run FFR on my P4 and it worked very well.

You can still use OXRTK to override the resolution and set it as you want. Or supersample with Oculus Tray Tool or Oculus Debug Tool.

QVFR is superior to the DFR in OXRTK. If you have enough CPU capacity QVFR can increase performance significantly more than DFR in OXRTK.

Sorry for the delay settings.cfg

@Maddaawg Sorry for the delay. This pesky work gets in the way. This is for my Quest Pro so applies to DFR. I can set up a similar one for fixed if needed. settings.cfg

I'll post my config file later.

I would have thought your i9 10th gen would have enough room for QVFR. According to CPU benchmark it's comparable with my 5800x3d. What QVFR settings have you used?

It does hit your CPU hard. Have you tried foveated rendering in OXRTK?