Th3ChosenOn3

This is just from memory, so might have some of the details incorrect, but back when this was posted, it was either before MT or early on into MT and before Dual CCD CPU optimizations were coded into DCS. Back then it was possible to "lock" DCS to CCD0 with game bar, but after a update that changed the way DCS uses cores on dual CCD CPU's, the ability to lock DCS to just CCD0 was lost. If you still use the game bar method, it will mostly use CCD0 for important threads, and CCD1 will exclusive run IO operations (Mentioned in the DCS.log file). If you don't use game bar, then it will spread usage between the two CCD's more from what I gather.

What resolution, codec, bitrate and DCS Settings are you running?

No. The fighter to fighter DL used to work between JF-17 and F-16, and you were able to see each other over DL. You were also able to share detected target between each other.

VD, VDXR and AV1 seems to be finally working on the latest release version (1.29.8) for my GPU at least. Haven't flown with it yet, just been sitting in the cockpit looking around for few minutes, but the visuals looks clear and I haven't ran into any issues so far (72hz, 195mbps, AV1 10-bit, Ultra, ASW disabled). Might be worthwhile giving it a go on your GPU again.

Here is what I use, you can see the lowered rendering on the edges a bit looking at menu's but I hardly notice them while flying. settings.cfg

Virtual Desktop 1.29.3 Beta is the only version I can see, and is unfortunately the one that doesn't work with H265/AV1 on the 7900 XTX.

I think you're running into the same issues that I and a few other 7900 XTX owners are experiencing with Virtual Desktop. Virtual Desktop seems to have a bug at the moment when you use VDXR and the H.265/AV1 Codec on DCS World. You can get it working by using H.264 but even at 400 mbps it won't look as good as using the oculus app at the moment. Not sure if they're working on a fix or when it might get resolved, so might be best to try out the oculus app in the meantime. Follow this guide, and you should get to a good starting point with the oculus app:

I noticed changes to DL too. From my experience, It might be that with the recent DL changes introduced in 2.9, that the JF-17 is not connecting to all the Datalink channels/sources anymore. Maybe @uboats can confirm if the JF-17 has received DL changes for 2.9?

Everything Maxed out, with FSR 2 on Ultra Quality (0.77 Scale) with 0.8 Sharpening. I get about 50% more FPS compared to MSAA 4x in the one scene I tested (40 FPS with MSAA 4X, 45 FPS with MSAA 2X and 60 FPS with FSR 2 Ultra Quality), at the tradeoff of a bit of ghosting on small objects and shimmering on very small details like fences. I also tried out TAA and NIS but got a lot more ghosting and shimmering compared to FSR for some reason along with slightly lower performance, so I wouldn't recommend using those at the moment. Here's the FSR Preset scale values, in case anyone wanted them: 1.00 = FSRAA / DLAA equivalent 0.77 = Ultra Quality 0.67 = Quality 0.59 = Balanced 0.50 = Performance 0.33 = Ultra Performance

Just played 5 hours with the latest version of AMD Fluid Motion Frames that came out yesterday, and wow I was blown away! They improved the frame pacing a lot, and it seems to correctly sync with my freesync monitor now as I had no visible tearing. It still turns off when it detects fast movements (like swinging my head around quickly), but for the majority of my flights it remained on and I had a extremely smooth experience. Don't know yet how well it works on 6000 series, but I'd definitely recommend checking the current version of AFMF in DCS if you have a compatible GPU. https://www.amd.com/en/support/kb/release-notes/rn-rad-win-23-30-afmf-tech-preview

Mirage F1 AZ would be amazing.

For testing CPU performance, we ran Plazma's torture map at 1920x1080 resolution, with the high preset to reduce the GPU bottleneck. You will also have to update the frame cap to 400 if you can run the benchmark close to the 180 FPS cap. There's a video earlier in the thread showing how to update it. You can also test GPU performance on Plazma's, like we did in the 4080 vs 7900 XTX thread, but the benchmark is mostly to test and compare CPU performance. You should also look at CapFrameX to gather the statistics, there's a post I made earlier in the thread explaining how to benchmark with it. While benchmarking, having mirrors enabled along with Tacview can reduce average FPS by about 30%, so it's important to check if it's on and keeping it in mind when comparing numbers here.

Just install the tech folder in savedgames, and leave/uninstall the mods folder that's suppose to go in the game directory.