Roosterfeet

I have a Quest 3 and I don't use Openxr tool kit. It causes DCS to crash when I remove the headset. OpenXR turbo mode helps with stutters while using ASW and I use Quadviews for that when I like. Quadviews and I aren't getting along at the moment.

To be clear, it's supposed to run at half headset refresh rate with ASW enabled. I'm able to tell the difference between ASW and half refresh rate without ASW because panning around my view is much smoother with ASW enabled. Also, I can see ASW flicker when I pan around my aircraft in external view. At 36 fps without ASW, I can also see rapid jittering that looks like a high speed vibration or blur on nearby ground objects when I look out to the side at low level. Can you see any of those differences when you swap between modes (ctrl-num2 and ctrl-num3)?

Unfortunately, DCS crashed when I remove my headset if I have turbo mode enabled through OXRTK. No clue why it's fine in quadviews but crashes with OXRTool Kit.

Some progress... The settings.cfg file is clearly the way to go for non-eye tracking headsets. Any idea how to enable turbo mode only without enabling the foviated rendering at all?

I noticed that even with pretty low peripheral resolution, I don't get any frame rate improvement with quadviews enabled. My frame rate isn't capped, and there is no question that the edges of my view are blurred. Anyone else run into this?null

+1

I had the exact same experience. I did find that lowering my PD from 1.3 to 1.0 offset the performance loss somewhat while still maintaining clarity. The ghosting on other aircraft was a deal breaker for me though.

In W11 I think it's Settings - System - Display - Graphics - Chang default settings

The ghosting on other aircraft is a deal breaker for me too. I went back to the stock DLSS 3.7 dll and it's certainly not as crisp without increasing the PD but the ghosting is much less noticeable.

I noticed a substantial performance hit using both preset J and K but I also noticed something else which is subjective and I wonder if other people will have the same experience. Prior to DLSS 4, I have been using pixel density to 1.3 to achieve the image clarity I want, but when I rolled the pixel density back to 1.0 with preset K enabled using DLSS 4, I had comparable image clarity and performance to DLSS 3 at 1.3 pixel density. I was using the Quality setting in both scenarios.

Make sure hardware GPU scheduling is disabled. That eliminated the stuttering with ASW enabled for me. 2.9 GB/s should be plenty.

I'm having a really hard time getting IR mavericks to track the correct target in Mission 9. Kind of an age old problem using them anywhere other than a big open field. I Point track my assigned target with the flir, hit cage and uncage on the maverick, it looks like it's tracking in the right spot but hard to tell in such a crowded area. Maverick seeker is lined up with the diamond in the hud, everything looks pretty good. Fire one at about 5 nm do it again and launch the second at about 2 nm and they hit a nearby building or a street light etc. Anyone have any tips?

I see something similar with quadviews enabled. I adjusted my quadviews setting to minimize it. If you are using quadviews, dry disabling in DCS and see if the transparent bars are still there.

Here's my best guess, so take it with a grain of salt. As you probably know, the headset is going to display 72 frames per second no matter what. With ASW on, your GPU gets limited to 36 FPS and feeds that to the headset; the headset takes two of those frames at a time (creating a tiny bit of latency) and does AI voodoo magic to generate in-between frames. The net result being you get 72 frames that are perfectly synced to the headset's refresh rate. With "half refresh ASW Off" the headset gets 36 frames and then has to display them 72 times. My guess is that it displays 2 identical frames then jumps to the next frame to maintain 72 hz and the effect is that any object moving across your filed of view will look doubled like you have bad astigmatism. Objects in front of you don't move very fast relative to your field of view so you don't notice it. Object's our your side view move faster and thus, blursville. Objects closer to you look worse than object's far away because close objects move across your field of view more quickly.

I've been using the Quest 3 and I've found that the best results are to either maintain 72 FPS or have 36 FPS with ASW enabled. Leaving ASW in Auto accomplishes both depending on the demands of DCS on your GPU. Don't bother with OTT. Use shortcuts to enable ASW. Ctrl numpad 4 = ASW Auto (recommended) Ctrl numpad 1 = ASW Off Ctrl numpad 2 = half refresh ASW Off Ctrl numpad 3 = ASW On Make sure hardware accelerated GPU scheduling is off in Windows settings. Ideally, with ASW in auto, the frame counter should display 72 or 36 fps and never anything in between. I had to turn hardware GPU scheduling off or I would get a lot of inconsistent frame rate between 36 and 72 which caused stuttering. I don't like leaving ASW on all the time because there are fewer graphics artifacts when my system is able to maintain 72 FPS. For instance, ASW produces artifacting when looking at a clear, blue sky which is also when I am most able to maintain 72 FPS so it works out well most of the time. Also, using turbo mode in Quadviews is essential for preventing stutters with ASW enabled.

Spotting aside (that's a super complicated topic), I find Track IR to be superior for dogfighting because it's much easier to keep your target in your field of view (unrealistically so). It's like being able to turn your head 180 degrees behind you. I prefer to fly with VR though because I don't do anything competitive and you just can't beat that level of immersion. Also, you can really hurt your neck trying to look behind you in VR so be careful.

I tried Open XR Toolkit recently because it let me enable turbo mode without turning on any foviation. Unfortunately, that caused DCS to crash every time I removed the headset. As you said, it's not supported any more. Quadviews does not cause a crash if the headset is removed so that's what I'm using now, it just took some tweaking to move the blurred area to the very edge of my field of view.

For what it's worth, I've completed the first 5 missions by seat switching instead of using George to target and fire weapons. It's probably harder that way but it works. It's a very good campaign.

Not sure what you're seeing but you could try enabling Turbo in quadviews if you haven't already. I've found that turbo mode eliminates stutter under a lot of conditions with my Quest 3.

I just wanted turbo enabled and I've found it a lot easier to use openxr tool kit instead of QVFR.

According to the thread linked above, it probably has something to do with late activation units in George's field of view. I was thinking about trying this campaign this weekend since the Apache is so much nicer to fly now. I might try with spotting dots on and do all the CPG work myself.

You can get pretty sharp cockpit gauges by using MSAA instead of DLAA or DLSS. The tradeoff is pretty severe aliasing everywhere you look outside the cockpit. I suspect MSAA in DCS is partially broken at the moment.

I'm running windows 10 on a 5800X3D with a 4070 and 32gb RAM. I've been messing around with a Quest 3 in DCS. Anyone think I would see a benefit to moving to windows 11 or should I just wait for the end of support in October?

So I'm still running Windows 10 on a 5800x3D with, a 4070 and 32 gb RAM driving a Quest 3. Do you think I would see a performance benefit if I moved to Windows 11?

I see thin black lines bordering the foviated area when using quadviews. Not a deal breaker but I would certainly prefer not to have them. Has anyone else encountered that? Here are my quadviews settings: turbo_mode=1 smoothen_focus_view_edges=0.2 sharpen_focus_view=0 peripheral_multiplier=0.5 focus_multiplier=1 horizontal_fixed_section=0.45 vertical_fixed_section=0.9 vertical_fixed_offset=0