Qcumber

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?

Yes. You can use quad view foveated rendering but only in fixed mode. I've used it with rift s, Pico 4 and Quest Pro. It works best with VD so you are already half way there. https://github.com/mbucchia/Quad-Views-Foveated

I just use a generic config file and adjust it as needed for VD or meta. It keeps it simple. I can post it here if that helps.

This happens quite often with me it's usually resolved with a restart of the headset.

Meta released a patch for this a few days ago so no need to stop the update. Just let the headset update to the latest PTC patch.

A 3060ti is borderline for a Q3. Have you tried using quad views foveated rendering in fixed mode? This will give you a massive performance boost. If you keep the centre to about 0.5 x 0.5 then you will reduce GPU load by about 50-70%. It will be more CPU intensity but a 5600x should deal with that. https://github.com/mbucchia/Quad-Views-Foveated

I only thought of this a few days ago when comparing VD and meta again after the update.

OTT is just an interface to access ODT. You can use both. If you change a setting from OTT it will update in ODT. The advantage of OTT is you can set hotkeys and it gives you a lot more control over ASW. However, OTT does not allow you to select the "quality" sharpening setting. I agree. I am using VD all the time these days. It takes a bit more setting up though with a dedicated router etc. I run VD without any AA and it looks pretty good. Sharp and no blurring. Jaggy is some places but not too bad. Looks better than with meta but this might be due to Meta's built in sharpening.

Try running without any AA and see how it looks. I am using that a lot these days. No ghosting or blurring at all. To minimize ghosting with DLSS you need to start with a high resolution. Try adding 1.3 multiplier into OTT. The other thing to try is update to the latest version of DLSS simply by downloading here and then replacing the one in the bin-mt folder. https://www.google.com/amp/s/www.techpowerup.com/download/nvidia-dlss-dll/%3famp You can also use DLSStweaks to change the preset (I find F is the best) and adjust the scaling. https://github.com/emoose/DLSSTweaks

I think it just allows using VDXR through oculus link. What the OP is referring to is using VD through a cable rather than wifi.

DCS runs on open XR. It changed from open VR last year. It's here for good.

This is related to VD so ggodin is the reference rather than mbucchia. I believe the limitation of VD to WiFi vs link cable is a meta issue.

The easy answer is stop using meta link.

If you want help please listen to Phantom711.