FupDuck

Interesting. I have a Pro and a quest 3, and I've noticed its now stuttering only on the Pro. I can play the exact same flight in both headsets, and the Pro stutters while the 3 does not. Strangely the frametimes and framerate are rock solid at 72 fps, but the screen is stuttering/tearing. I'm on the road this week, but I'll look into this as soon as I get home! Thanks! Interesting, I will look into this as well!

I also noticed a lot of sound cuts since the update to v59. I assumed it was something with my connection, but I guess not...

My controllers are fully charged. Just took them out of [off of?] the cradle, which is plugged into the power supply. Sorry, no profit... I have also noticed that the dark screen performance can be improved a lot by adjusting the position of the headset, and the best position is just as you describe it. But that mainly helps with the edge effects, rather than the glare around points of light. Anyways, I've decided to live with it. The mura in the Quest 3 on the other hand is intolerable so it's getting returned.

These have been my two main beefs as well. With everyone raving about the local dimming, I was very shocked by how bad this halo effect was. I have a bunch of night missions that I used to play with my Quest 2, and in that the black levels aren't great, but you can easily see the stars and there's no glare around my instruments, etc. With the Quest Pro, it's a foggy mess. Like it literally looks like one of those London fog nights from Sherlock Holmes. It's the one thing that's making me think about returning it. I bought two, and they both had the same identical problems with the black levels. Everything else besides that is superior to the Quest 3, which I also bought (except maybe the passthrough, but I never use it). The lenses, clarity, colours, build quality, brightness, FOV, etc are all better on the Pro. Just not the black levels. Oh and my left controller is constantly randomly floating away into space. Anything I can do about that? I already tried cranking up the lighting, didn't help much...

I think your settings are just too high. I don't think there's any computer that can run the settings you have smoothly in VR. I suggest setting the Oculus slider to 72Hz, 1.0x resolution (default), and see how it looks, then if its smooth, work your way up. Bitrate doesn't really have that much of an effect on your FPS unless it's way too high. I recently bumped mine from 400 to 700 with no difference in smoothness (via cable, I find VD gives lots of stuttering compared to link, all else being the same). Also, MSAA is not your best bet these days for anti aliasing, given the new options available. In general, your DCS settings will affect performance way more than bitrate. I really don't think this is a problem with your headset. You just need to start low with all your settings and work your way up. This is the way of VR .

Hmm, this is the first time I've heard this. @mbucchia, are you able to confirm?

Why not? Get a few cheap cables on Amazon, and keep the ones that work best. By far the cheapest and easiest option!

I am experiencing the same thing. Quest Pro, 3090, 5800x3d.

Wait, I'm confused. Is the shimmering better or worse with MSAA?

I tried setting all the other supersampling techniques to default and only using the QVFR config. It did not make any difference for me in terms of frametime or smoothness. I also tried setting the desktop resolution to minimum in the OTT profile, and this also made no difference in terms of VR performance. All it did was mess up all my icons when I got out of VR! These are my experiences, can't speak for anyone else.

FWIW, I use a three year old cable that I got on Amazon for $13, the same one I've been using with my quest 2 for three years. It works great. You may just have had a bum cable, it's happened to me. Might be worthwhile trying something cheaper to see if it works while your can still return the official cable.

Interesting. I was always using the same "benchmark" file that I always use, which is in an F16 over Persian Gulf. Maybe I'll try some different scenarios and see if that makes a difference. Thanks for the insight and sorry that you never got it working right (and sorry for your "poor 5800x3d/4090" )

Thanks for the reply. My specs are in my signature at the bottom of my post (3090, 5800x3d, 64 GB of ram). My settings are very similar to yours. I have already tried using only the Oculus slider to maximize the resolution, with all others at 1.0/default (that was my step 3 above, sorry if that wasn't clear). With regards to your other points: - I am using wired link, so it's at least as good as air link. I use both. I don't think this is a factor in the current situation. - My OTT settings are about the same as yours, except my FOV multipliers are much higher, 0.85, 0.95. I've tried making it smaller, but it cuts very noticeably into my FOV. I love the wide FOV of the Pro compared to the Quest 2I had before. That's going to be tough to give up (especially given that I have no problems/stuttering when using FFR). - The desktop resolution in the OTT settings is something I've fiddled with in the past. Setting it to minimum and maximum values made no difference for me in VR, only when playing flatscreen. - I had not heard of OpenXR eye trackers before. This wasn't included in the instructions for QVFR. What does this do? Does it need to be installed before or after QVFR? I would think that it l if it was necessary, @mbucchia would have included this in the instructions. I'll try anything at this point though. I'll give it a shot after writing this post and will let you know if this works. Just out of curiosity, do you have ASW enabled? What framerate do you usually get when flying low? Thanks again for the detailed reply! Hi @recoilfx, I was just wondering, did you ever get dynamic foveated rendering working for you? As in, were you able to eventually get better performance with it running? Your description of the issues you had seem very similar to mine. Thanks!

First of all, thanks to @mbucchia for making this great piece of software. It was when I saw that dynamic foveated rendering was possible in DCS, and the associated performance benefits, that I decided to buy a Quest Pro instead of the Quest 3. Unfortunately, I am among the camp of people where enabling the QVFR causes worse performance than with it disabled. My specs are below in the sig. I've followed the installation instructions to the letter, and I can definitely see it working in DCS, with the sharp area right in front of my pupil, and on a plain background, I can just make out the focus area rectangle if I look for it (it moves with my eye). I've confirmed before enabling QVFR that my system is GPU limited by using both the in game framerate graph and the Oculus application rendering frametime overlay, which consistently showed my GPU frametime to be about 2x the CPU value. So I figured I was a perfect candidate for QVFR. But when its enabled, it stutters significantly, whereas without it enabled, I get very smooth performance and steady frametimes. Prior to installing QVFR I ran FFR in OpenXR with the inner ring at 1x to 78%, and 2nd ring at 1/4x to 91% (so the sharp area is larger than the QVFR default). I have the Oculus software resolution set at 1.0 & 72 Hz, with 1.6x super sampling in OTT, and PD at 1.0 in DCS. With these settings I get steady 72 fps using the Pro in DCS except in very graphically intense situations. I always leave ASW disabled because the artifacts ruin the immersion for me. Here's what I've tried so far, all independently and with no effect: 1. Turned turbo mode off/on 2. Left all OpenXR settings at default while using QVFR 3. Set OpenXR settings to same I used before installing QVFR (except leaving FFR and turbo mode disabled) 3. Used Oculus app to set max resolution and don't use OTT at all, with ODT options all to default 4. Slow repair of DCS and removal of all mods 5. Turned down the rendering resolution factors for both the focus and peripheral regions in QVFR 6. Made the focus region smaller in QVFR As I said, none of the above resulted in a less stuttery performance. Here is my log file: 2023-10-18 17:13:14 -0400: XR_APILAYER_MBUCCHIA_quad_views_foveated layer (v1.1.1) is active 2023-10-18 17:13:14 -0400: Using layer: XR_APILAYER_MBUCCHIA_quad_views_foveated 2023-10-18 17:13:14 -0400: Using layer: XR_APILAYER_MBUCCHIA_toolkit 2023-10-18 17:13:14 -0400: Using layer: XR_APILAYER_FREDEMMOTT_OpenKneeboard 2023-10-18 17:13:14 -0400: Cannot satisfy implicit extension request: XR_EXT_eye_gaze_interaction 2023-10-18 17:13:14 -0400: Requested extension: XR_KHR_D3D11_enable 2023-10-18 17:13:14 -0400: Requested extension: XR_KHR_visibility_mask 2023-10-18 17:13:14 -0400: Requested extension: XR_OCULUS_audio_device_guid 2023-10-18 17:13:14 -0400: Blocking extension: XR_VARJO_quad_views 2023-10-18 17:13:14 -0400: Requesting extension: XR_FB_eye_tracking_social 2023-10-18 17:13:14 -0400: Application: DCS World (DCS.exe) 2023-10-18 17:13:14 -0400: Using OpenXR runtime: Oculus 1.89.0 2023-10-18 17:13:14 -0400: Using OpenXR system: Meta Quest Pro 2023-10-18 17:13:14 -0400: Trying to locate configuration file at 'C:\Program Files\OpenXR-Quad-Views-Foveated\settings.cfg'... 2023-10-18 17:13:14 -0400: Found option 'smoothen_focus_view_edges=0.2' 2023-10-18 17:13:14 -0400: Found option 'sharpen_focus_view=0.7' 2023-10-18 17:13:14 -0400: Found option 'turbo_mode=1' 2023-10-18 17:13:14 -0400: Found option 'horizontal_fixed_section=0.5' 2023-10-18 17:13:14 -0400: Found option 'vertical_fixed_section=0.45' 2023-10-18 17:13:14 -0400: Found option 'peripheral_multiplier=0.4' 2023-10-18 17:13:14 -0400: Found option 'focus_multiplier=1.1' 2023-10-18 17:13:14 -0400: Found option 'horizontal_focus_section=0.5' 2023-10-18 17:13:14 -0400: Found option 'vertical_focus_section=0.5' 2023-10-18 17:13:14 -0400: Trying to locate configuration file at 'C:\Users\sandm\AppData\Local\Quad-Views-Foveated\settings.cfg'... 2023-10-18 17:13:14 -0400: Not found 2023-10-18 17:13:14 -0400: Eye tracking is supported 2023-10-18 17:13:14 -0400: Recommended peripheral resolution: 960x1100 (0.400x density) 2023-10-18 17:13:14 -0400: Recommended focus resolution: 1320x1514 (1.100x density) 2023-10-18 17:13:14 -0400: Stereo pixel count was: 13209600 (2400x2752) 2023-10-18 17:13:14 -0400: Quad views pixel count is: 6108960 2023-10-18 17:13:14 -0400: Savings: -53.8% 2023-10-18 17:13:21 -0400: Session is using quad views 2023-10-18 17:13:21 -0400: Edge smoothing: 0.20 2023-10-18 17:13:21 -0400: Sharpening: 0.70 2023-10-18 17:13:21 -0400: Turbo: Enabled It says I'm saving 53%, so I would expect a significant uplift, but it isn't happening. It performs about the same as it does when I have no FFR enabled in OpenXR (again, with lots of stutters). Attached are the Performance settings in OpenXR that I use when I don't have QVFR enabled, in case thats helpful. Does anyone happen to have any other hints that I could try? I have read the many accounts on here of people with significant gains and with systems similar to mine, and I would really love to be able to take advantage of this great software! Thank you!

Sorry to necro this, but may I ask your PC specs? I'm looking at getting a Quest pro, and I wonder if your settings here would give me similar results. Thanks!

Oooh cool, I would love to see this!

Hi, thanks for doing this mod! When I go to the post you linked, it seems to say it's the 2.3 version from June, rather that 2.5 from August.

Sadly, even with 24GB, it often maxes out...

Thanks for the reply, this is what I ended up doing, and it seemed to have worked. For what it's worth, I didn't see much off an improvement, but maybe it's because my rig is already fairly decent? Thanks for the reply, this is what I ended up doing, and it seemed to have worked. For what it's worth, I didn't see much off an improvement, but maybe it's because my rig is already fairly decent?

I really can't wait to fly this thing, or even have an AI version to fly beside and drool at. There's something about the curves of the air intakes and that high wing design... Somehow simultaneously ugly and sexy AF.

Is this still alive? I went to the discord, but all that's there in the updates channel is some pictures of an F111... Really hope this moves forward!

I am also seeing the "grow lights", not just in Paris though, I see it throughout the map. Good to know it's a bug and not due to my years and years of drug and alcohol abuse.

Ah gotcha, wow, I didn't realize there was 30 GB in total, that's wild! Thanks for the response!

Same here, I don't know if they disabled this, but now when I set shadows to 5, in game it just turns them off. Worked for a while, but not anymore.

This looks great, I can't wait to try it! Quick question, for the "update core" patch files at the end of the first post, do I need to install all of those, or just the most recent? Thanks!