f14billy

If you want to enable ultra shadows without having to change the config file every time try this: In the file \DCSWorld\MissionEditor\modules\Options\optionsDb.lua add the ultra option as shown below. graphics('shadows') :setValue(2) :combo({Name(_('OFF')) :Value(0), Name(_('FLAT ONLY')):Value(1), Name(_('LOW')) :Value(2), Name(_('MEDIUM')) :Value(3), Name(_('HIGH')) :Value(4), Name(_('ULTRA')) :Value(5) }):low(1):medium(1):high(4):VR(3) This adds the ultra option in the shadows menu in the options tab. Not sure if this will break the Integrity Check in multiplayer. It works perfectly in my PC in single player open beta 2.9. @BIGNEWY could this simple change be added to the code? Thank you

I haven't quantified it but in a dogfighting scenario in the Caucasus map it allows me to consistently hit 90hz for 1 v 1 encounters with a central resolution set to 1.2%. Very sharp and clear. Without it I would not be able to hit that fps consistently and would cause stutters. When I used a Reverb G2, the only way I could achieve 90hz was to lower the resolution in the OpenXR toolkit, so instead I decided to set it to 60hz and the flickering was evident. I don't think I could ever go back to a headset without eye tracking and dynamic foveated rendering support.

That's unfortunate. With a 4090 and the Pimax Crystal DLAA works great using Quad Views Foveated rendering. DLSS definitely affected quality so I decided to stick with DLAA. I tested spotting and it is definitely better. However that bigger spot looks weird using DLSS.

You may want to try DLAA without DLSS, in my experience it looks way better than MSAA4x with better performance.

In the new open beta there seems to be a gun pipper lead calculation bug. This only happens the first time a mission is run in DCS. After that first mission ends when loading the mission again the bug is not there. Steps to reproduce: 1. Start DCS and load the track attached. The gun pipper lead is off so when placing it in the target the bullets will go in front not hitting it. In order to be able to hit it I had to place the pipper behind the target. (in the track you can see me trying to place it in front first, only when placing it behind it I achieved a hit). 2. In the same DCS session. Load the track attached again. The gun pipper will now show the right lead calculation. (it could also just be a bug in the Y axis of the pipper placement instead of a lead bug). I am also attaching a couple of screenshots, both taken at the same time from the attached track file. The first one shows how the pipper is displayed the first time the mission is run. The second one shows how it is displayed the second time the mission is run. F18 gun pipper bug.trk

F18 v F14 STT.trk Here is another example with the F-18. At the merge I am above the F-14 and the STT lock gets lost constantly, then I proceed below and the track is steady. When doing 1 circle turns with him I position myself above and below to show the difference in STT tracking.

About the STT lock. I just tested the F-18 against a few different aircraft. Against the F-14 and Mig 29 the only way to keep a consistent lock was to keep them above the horizon. Against the Su27 the look down lock was more consistent. Is the look down penalty that big in STT? or does this still need to be tweaked? It was not like that before the radar overhaul. I also tested the F-16 against F-14 and same behavior.

I've noticed something similar with the F18 radar. After some testing it seems that if the target is below the horizon the radar has a hard time keeping lock (ground clutter maybe?). I wonder if this change was intended and if we now need to try to stay below the target to get a better continuous lock in a dogfight?

Looks like my flap lever wasn't mapped correctly and it was not engaging the flaps past 50%. That is why it was not engaging.

In windows 11 when flaps are down and throttle isn't MIL pressing the DLC/Countermeasures button won't engage the DLC, instead it deploys countermeasures. Gear up or down does not make a difference. In a windows 10 install it works as expected. EDIT: not a bug, flaps were not being lowered 100% due to an error in the axis assignment in the controls.