Qcumber

Thanks. Just wondered if I had missed any recent changes. You know how rapidly VR develops and new "tweaks" come along. I revisited DLSS recently after some time without any AA and have found that there is now minimal smearing with moving aircraft. The cockpit is as sharp as it can get. It all looks very good (preset F, quality scaling set 0.9).

I am getting an issue with QP since the last meta update and DCS update which sounds like it us the same as yours. As these were about the same time I am not sure if it relates to one or both. I get random periods when the headset loses tracking for 1-2 seconds and the image freezes. It happens with both VD and meta link. I disabled OXRTK and XRNS which seems to reduce the frequency of it happening, so I wonder if this is an open XR layer issue. I need to do some more experimenting. The first thing I will try is reordering the open XR layer. Then removing some of them completely. Are you using QVFR?

Is it necessary to edit the .ini file when DLSS tweaks allows you to change the presets and scaling from within the config tool? I have mine set to preset F.

Try adjusting the DLSS scaling in DLSStweaks. I use 0.9 and get good results.

It will shift some of the processing to the CPU so if you have enough CPU overhead QVFR will increase performance. If you are CPU limited it can make performance worse. In such a case the foveated rendering in OXRTK will be a better option. My post above links to mbucchia's guide for QVFR which is worth a read.

If you have not already done so then I suggest reading this thread on how to use QVFR and mbucchia's guide notes. https://github.com/mbucchia/Quad-Views-Foveated The recent changes in DCS just lets you toggle the QVFR openxr layer on or off in DCS and likewise the headset eye tracking (if available).

If you change sharpening in ODT to quality it will show as blank in OTT. All OTT does is edit the same files as ODT does. It's just a bit more user friendly and has other options. You can use both at the same time. I do. Thinking about this a bit more it does sound like your bitrate is variable for some reason. Try setting the bitrate to about 150 in OTT and see if it still happens. Also check your cable still has a decent bitrate. I had done issues with a cable which started to go bad.

Is it getting pixelated across the whole frame? What does the DCS fps/frametime chart look like? Is there any change in GPU usage as it happens? Are you seeing it in all missions or just some? Not sure if this will help but try resetting distortion curvature to default. You could also reduce the encode resolution as I don't think you need it that high for a Q2. You could disable the encode bitrate and set it manually. I have mine at 960 on the QP. It might although be worth checking your link cable to see if there are any issues with this. You can check this via the desktop app. Unrelated but have you tried setting sharpening to "quality" in Oculus Debug Tool? I find the normal sharpening a bit too harsh.

Duxford BoB? I missed that one unfortunately but I'm going to the end is season one this weekend. Nice shot of the Dragon Rapide cockpit. You must have been sat right at the front.

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.