Glide

YF-23 test pilots and the history of combat aircraft development. Oldie but a goodie.

As mentioned, restore defaults in the NCP. Also, disable "prefer framerate over latency"; you don't need the boost with a 4090, and latency is smoother than high fps. High textures and AF x16 put a lot of load on that part of the graphics pipeline. Note the forest details settings. You should experiment with setting your G2 to 60hz and enabling Motion Reprojection Best Framerate with either TAA or DLAA. Disable Nvidia Optical Flow as your motion sensors in the G2 are excellent. MR is working fairly well with the F-16 and AH-64 if you stay above 60fps. See my settings below. These settings are all about smooth flying experience. They are not designed for screenshots or low and slow flights. 3080Ti 11700K

Recall in 2.8, if you set the OpenXR custom resolution down low to improve performance, it would introduce some pretty bad screen artifacts that no amount of AA could fix. Well, in 2.9 that has changed. Kudos to the devs for this amazing improvement! With OpenXR at 49% and DLAA I get no artifacts. I still have to test the full range, but this is huge. These shots are with my HP G2 at 60hz. Without MR enabled I was getting a solid 70fps. That makes MR a good option when you can stay above the refresh rate.

I totally get it. The thing to keep in mind is that this is a simulation, and the sim has to be fun. On the one extreme you have missiles that never miss. This is very easy to test, but not very realistic. So, the devs have to add some level of randomness so you and your targets can sometimes defeat the missiles. This add a huge amount of fun, but it's much harder to test. Let's throw up some ideas. Straight and level rear aspect. Straight and level nose on. Approach at 3 and 9 o'clock. Approach into the sun. Approach with the sun at your six. Shooting high. Shooting low. Shooting with conflicting targets nearby. I also find that the 9x is pretty deadly when fired just inside 1.5 miles, but depending on the merge dynamics, this short distance can quickly become a miss. So, add to the above scenarios a variety of launch distances. A good test mission would have a variety of drone targets to demonstrate each scenario, but drones do what their told. After all of that testing there are the Red Flag tests against various AI skill levels. That's why I created that PG Dogfight mashup. It's a ton of fun to fly, and I see all the behaviours of the AI and the missiles. I know my mission is not very scientific.

I have a lot of experience with the 9x in DCS, and I feel it is well balanced. If I am careful and wait for a rear aspect launch, I can almost always get 6 for 6 in the F-16. The missile will loose lock against the sun or if a hot target passes through it's fight path. I believe cold targets like the SU-25 have a better chance of defeating it vs hot targets like the Mig-29S, for example. You might want to try a mission like my PG Dogfight for testing. Fly that a few times and you will see what I mean. Cheers.

There used to be a bug related to this, but it's fixed now. The method for testing was to disable shader cache in the Nvidia Control Panel, then launch into Syria Map at Beirut airport. Immediately after spawn, pan the viewport back and forth. The sim would stutter until the missing shaders were compiled. I called this the Beirut test, and when I want to stress test a release I go to Beirut. I have only needed to delete shaders one time in my entire life. I don't know all the details about DCS shaders, but my understanding is they get signed after an update so they don't mix up with versions. IMHO, in this modern age, developers don't make solutions that require the users to perform a bunch of voodoo steps to get their software to work properly. DCS has always worked out of the box for me, and I really enjoy exploring the changes to the graphics engine after each release by tweaking graphics settings.

You don't need DLSS with that rig. Try DLAA. These are my settings with Motion Reprojection, and they are great IMHO. HAGS off. The key is to lower Forest Details and Visibility sliders.

I never said Normandy looks bad in 2.9; I said my settings for Forest Detail and Visibility might not be to everyone's liking on Normandy. I keep my settings low to ensure all my compute power goes to smooth dogfighting experience. With those settings I posted, I can maintain 45fps through a hot dogfight and the flying experience is incredibly smooth. So, given I can achieve smooth flight at 45fps with DLAA, I don't really need DLSS. Incidentally, I tried the same settings (roughly) on the civilian flight sim, and it could not manage 30 fps. I need DLSS Performance over there to have the same experience. I don't notice the ghosting or bubbling that trails objects in the sim with DLAA or DLSS, but I think this is because of my lower graphic settings (3080TI i7 11700k). I could lower them even further by disabling SSS, but I want to see how that feature plays out. So far, with DLAA and TAA, it's not a big issue as long as I keep my forest details and visibility low. The main point is that Motion Reprojection seems to work very well with DLAA in the F-16. The AH-64D is good too. I have noticed the leading edges of the P-51 wings still dance around. These are called de-occlusion artifacts, and just like the jaggies or shimmering, this is something you can learn to ignore if it's not too bad. BTW, these settings on the PG map at dusk or dawn will shock you. No shimmering lights. That's a first.

Just picked this up for the Halloween sale, and it is wonderful! I love the flight model! Flew a little recon mission up over the Caucasus, and I put it down like butter in a wheat field. As I was climbing up over the mountains my canopy started fogging up. Then the ice started forming. Quick scramble for the icing controls and all's good. Worth every penny.

My experience with the HP G2 and Motion Reprojection is very good with DLAA. These settings work especially well on the PG map. The forest settings look pretty bad on Normandy, so adjust to your liking. Headset at 90hz. Foveated Rendering Performance Wide in OpenXR Toolkit. HAGS off, NCP all defaults.

T-7 gets it's wings. https://www.defensenews.com/air/2023/10/20/heres-when-the-first-t-7-trainer-is-to-fly-to-edwards-air-force-base/

Getting good results with Motion Reprojection and TAA/DLAA.

Try turning down Forest Details and Visibility.

DXDiag reports: Native Mode: 2560 x 1080(p) (144.001Hz) You have 3 screens? or a custom resolution?

I take it with Vsync enabled you have a 180hz monitor. You might want to try Low Latency Mode = Ultra in the NCP, and experiment with HAGS on and off. I have it off right now with my i7 11700k.

Yeah, that's odd. Memory leakage, perhaps? I use the OpenXR Toolkit FPS HUD to monitor vram usages and frame times.

I did some testing on this with my 3080Ti/G2 doing some low flying over Caucasus. With TAA, Shadows High, Secondary Shadows On, Terrain Shadows Default, and Visib Range Extreme as a baseline, I tested the scenery sliders. Forest Details and Forest Visibility at maximum make it very jittery. Both at max or either one at max is jittery. Both off is silky smooth. Clutter/Grass did not seem to be a factor, nor did Scenery Details Factor. I did not zero in the sweet spot, but with Forest Visibility at 40% and Forest Details Factor at 0.24 it's smooth. I maintained 60 fps during all the tests with the F-16.

Nice job with TAA! My favorite so far. BTW, SSS is not available unless Shadows are set to Low-High. Flat or OFF means SSS will be grayed out.

I think it has something to do with the chain link fence and the angle of the sun. I'll take another pass at it. A lot has changed since then. EDIT: Lighting looks perfect there now.

When you try OpenXR, use the multi-thread version (MT) for testing. Enable the Screenshot function in the OpenXR Toolkit Companion. This will allow you to screenshot with CTRL+F12. Also, try Win+PrintSCRN to capture the desktop view. You can take the headset off and just hold it in front of you like it's on your head. I assume you have Position tracking disabled in Mixed Reality > Headset Display and Input Switching set to Manually switch with Windows Logo key + Y under Mixed Reality > Startup and Desktop. Also disable Create Virtual Displays under Mixed Reality > Startup & desktop and disable Open the Desktop view app when a desktop app gains focus on the same settings window.

And the different versions of DLSS are binary compatible. So, there are users over in the MSFS community who are replacing the DLSS executable each time a new version of DLSS comes out. This gives the false impression that they are somehow upgrading their DLSS implementation, when in fact it requires developer work to implement the new features in each successive version of DLSS. So, don't be fooled.

I have mine set to unlimited, but just for the clearing operation, setting it to disabled frees the locked files. Then set it back to unlimited.

One other thing you may already know, but just in case, to clear the Nvidia Shader cache, set Shader Cache to disabled in the NCP, reboot and either run the cleanup util or do it by hand. Shader cache files that are "in use" can't be deleted.

Try one of the canned missions like Hot Start from Batumi in the TF-51D. That would rule out the map and the modules in your test mission.

Try Shader Cache Size Unlimited. Try HAGS on. Try setting maxfps to 60 in your autoexec.cfg (see graphics.readme in Config) Try increasing Virtual Page File size. INCREASE THE VIRTUAL MEMORY (PAGEFILE) ON YOUR SYSTEM In the Windows Search bar, type Advanced system settings and open the Control Panel. Make sure you're on the Advanced tab. Click the Settings button from under the Performance On the Performance Options box, go to the Advanced tab > Performance Click on Settings On the Virtual Memory box, uncheck the Automatically manage paging file size for all drives Click to select the drive on which Windows 10 is installed (by default C:) Click to select the Custom size radio button. In the now-enabled fields, type the minimum and maximum size of the Pagefile in megabytes (MB) according to the physical memory present in your computer. Click Set and then click OK. Restart your computer. Mine is min 5120 max 32768