Th3ChosenOn3

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.

Mine takes about 20 seconds on my ASRock board with two sticks of 32GB DDR5 overclocked to 6200 MHz. Boot times are dependent on the motherboard and the memory configuration and can take up to a minute, but motherboard venders are working to get boot times quicker. Gigabyte boards have the fastest boot times at the moment I think.

I'm still checking it out on Plazma's, but seems for me it didn't do much. Not sure if anyone else with 7950X3D saw any improvement?

If you get time, do a run with the 400 FPS cap along with Tacview and Mirrors Enabled.

I followed this tutorial, just changed it to 400 instead of 300.

If you get some free time, try this at 1920x1080 High Preset. Make sure to specify if mirrors and tacview are on, as it can have significant impact on the outcome. You'll also need to up the max FPS to 400. Also, congrats on the kid.

Thank you. Here is the same benchmark with CCD1 only (V-Cache CCD disabled): The fully enabled 7950X3D with it's V-Cache cores has a 45% higher average and 15% better lows (1%, 0.1%). Here's a chart with all three of them for comparison: CapFrameX-DCS-7950X3D-CCD0-Disabled.json

No worries, I do all of the tests with all the cores enabled, and let game bar handle the scheduling. It would be a bit of a waste to turn off CCD1 on the 7950X3D. You're not showing the 1% and 0.1% lows in the statistics, those are the 1 and 0.1 percentiles in your screenshot. Here is a picture of all of the stats on latest MT patch using 1080p High Preset with Tacview and Mirrors enabled: Same thing, but with CCD1 disabled (7800X3D Simulation): CapFrameX-DCS-7800X3D-Simulation.json CapFrameX-DCS-7950X3D.json

My results earlier in the thread are with a 7950X3D and 7900 XTX, if you want to do a comparison.

You claimed v-cache doesn't give anyone any gains, and now you're saying you don't know if v-cache has a performance improvement or not. It might be beneficial to figure that out first before making such claims, as what you're doing doesn't help anyone. You shouldn't be testing for a CPU bottleneck in a very GPU bound situation like you're doing on Marianas. I'm also hoping you're using an application to capture data to analyze instead of just looking at a hardware monitor and Nvidia's performance overlay.

The 120 average fps run on the non 3D v-cache CCD was first run after getting the system up and running, and noticing that DCS was running on the incorrect CCD and so there were many things unoptimized. I'm just mentioning it as it was the only experience I've had on the non 3D V-Cache CCD, but I never used it in any of my charts or data. After fixing game bar, and seeing DCS run on the 3D v-cache CCD I started gathering data. It's also worth mentioning that my 60-75% uplift claim is from upgrading my 5800X to the 7950X3D.

I've done a run on the Normal CCD of the 7950X3D, and got an average of 120, after I fixed my game bar issue and DCS was running on the 3D V-Cache CCD, my average jumped to 170 pre framecap update, and over 200 after the frame cap update. You should see substantial gains if you're on the 3D V-cache CCD, unless you're being bottlenecked somewhere else.