Roosterfeet

Has anyone found the ideal time to kiss off the AI and break? My wingman keeps getting in my way in the groove and we both get waved off. I suspect I'm flying too loose of a pattern but it's hard to troubleshoot what I'm doing when I don't know exactly when to kiss off and when to break for the best timing with the AI.

There's your problem. It's not just you, I have the same issue and it's because my face is a little bit asymmetrical. The best solution I have found is to turn my head a bit and recenter to compensate, as you described. I've messed with trying to adjust the headset so it sits more squarely on my face but it always shifts back to a more natural but off center position after a few minutes use.

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.