Th3ChosenOn3

PSU recommendations for GPU's are generally high due to them not knowing what else is in your system. 600W is a bit on the low end, but your system doesn't seem to be limited by the power supply from what I can see. I saw your GPU hit a clock speed of 2790MHz, and looking at the internet for videos with a similar card to yours, I found this video with a lower GPU clock speed than what you're hitting (probably due to being a non-oc model), which indicated that your GPU appears to be running at full speed without any issues:

Hi guys, @xoxen and I ran another benchmark to compare the RTX 4080 against the RX 7900 XTX on our similar systems. This time on the Marianas map to put our machines in a more GPU bottlenecked scenario. Xoxen kindly flew the mission, provided the track file and a recording of his system playing the track file to put both system in the same scenario for comparison. I've attached the track file for anybody else that would like to run the same benchmark/track to compare their system. Overall, the RX 7900 XTX seems to be around 10-20% faster across the entire track. I've also gone and done a mild overclock on my card and ran the same track file for comparison, which resulted in another 10% gain over the XTX and around 30% at times faster than the RTX 4080. We used the same settings as before, which is Plazma's 1440p settings. Marianas Benchmark.trk

So I've gone and taken your second run with the updated driver, and ran another test with the track file I sent you to allow for a frame by frame comparison. Considering that our system are slightly different in terms of motherboard, ram, storage, and the fact that the track will have slight variation between runs, it's important to try and average the results and not take the values at face value. Looking at them side by side, I'd say they perform on par with one another. I believe the slightly higher FPS on the RX 7900 XTX is due to my ram/storage configuration being slightly faster than yours, especially since both our system's aren't maxing out the GPU's to 100%. There's a couple of frames where we are at the same FPS and both cards are showing the same GPU percentage. We might have to run another test where the GPU's are being maxed out, instead of being limited to our CPU's. It might also be worthwhile to come back to this test after ED's implementation of multithreading. On the RX 7900 XTX side of things, there's glitchy smoke as seen in the clips. I'm not sure if it's a driver, game setting or issue with the game that may be causing it, but I've only noticed the effect in the benchmark. I also think the RX 7900 XTX uses quite a lot more power compared to the RTX 4080. My card will pull up to 400W on 100% usage in other games, and I don't think the RTX 4080 will pull that high, so may be something to consider if you're in a region with expensive electricity. My card is also pulling a consistent 126W while writing this post, but I believe it'll be fixed with a driver update in the future. Also for VR, it's been mentioned before that the RX 7900 XTX will lose to the RTX 4080 at the moment, due to driver issues. I don't have a VR headset to test with, so I can't say at the moment how the card will perform and it'll be up to someone else to test that scenario. For my conclusion, I'd say if you're not a VR gamer then both cards perform the same and you'd be happy with either but the deciding factor on which to get will depend on price, which card are in stock and if you're willing to deal with the AMD driver problems until they're sorted.

Seems I won't be able to test a resolution above 3440x1440. Unfortunately I can't seem to get the game to behave properly with a resolution of 3840*2160 on my 21:9 aspect ratio monitor. Sorry.

I forgot to save a track file, but I've created another for you to use. I can run the same mission again at 3840*2160 to give a better estimation of GPU performance if it would be helpful? Plazma Torture Map - Level Flight.trk

Wasn't sure which resolution you wanted me to use, so I used my native 3440x1440 resolution with the High Preset. I also didn't really know what to do, so I flew around for a bit. Hope it helps with your comparison. You'll have to setup Benchmark key binds, and then press Begin Recording to have them show up.

Yeah, it would be great to see a benchmark with your 4080, as we have similar systems. If you change your resolution to 2560x1440 and enable fullscreen, the image will get stretch over the entire screen (What happened to me) and you'll be able to do the benchmark with no issues on your ultrawide.

Thank you. I'm on the Windows 10 WHQL drivers. I don't remember experiencing micro stutters while running the benchmark, but I wasn't heavily focused on the screen. I did notice glitchy smoke in the benchmark, and clearing my FXO/Metashaders folders today seems to have gotten rid of them. I've also enabled Adaptive Sync, and had a very smooth experience for the two hours I've been able to play today, but I'm not sure if I should keep it on for the benchmarks as I'm not sure if it would affect FPS. MSI Afterburner with Rivatuner Statistics.

I've done a quick benchmark with the Plazma Torture map using the RX 7900 XTX. I'm getting double the average framerate compared to the GTX 1080, and going from being GPU bottlenecked, to CPU bottlenecked. Overall quite impressed, although I'm not sure how it compares to competing cards. When I get some time tomorrow, I'll do a few more benchmarks as were suggested here. Note: Timestamps added on the video.

Got my card today. Going to take a few hours to get everything setup, so I'll probably post benchmarks tomorrow.

I'll give the AH-64 one a go when I get my card. Don't have the F-16 unfortunately, so can't test that one.

Yep, I was thinking of running the F/A-18C Free Flight Instant Action Mission on Syria as a empty map test, as well as another mission flying at high altitude and a ground test when I get some time today. I've got the 1440p settings saved as a preset to use for benchmarking, but I also want to use my "optimized" game settings for my native resolution of 3440x1440p. 2560x1440p settings from the video (Same settings as shown on Plazma's video):

I ran Plazma's test recommended by @Andrei with my GTX1080 to use for comparison tomorrow or whenever I get my card. Not sure if there's any other statistics I need to add, or if there's another mission to test while I have the 1080 in my system.

Thank you, will give it a go when I get my card, but might be bit CPU bound with a 5800X.

I'll most likely be receiving my XFX RX 7900 XTX tomorrow and plan to try DCS. Don't really have comparable numbers to current gen offerings, as I'm currently GPU bound with GTX 1080 8GB. I'm playing on a monitor (3440x1440), so won't be able to give VR numbers. Are there specific missions/tracks that are used for benchmarks?

Would love for these weapons to be added as well, if there's sufficient data to add them.

Interesting data, thank for posting! I used to also prefer the default TWS/DTT setup for BVR, but a couple of update ago TWS started detecting and showing targets on the radar screen, but they couldn't be locked for a couple of seconds (Normally 5-10 seconds, probably linked to the update rate if I'm looking at your data). Not being able to lock up targets for a couple of seconds after detecting them is a extremely frustrating and a big disadvantage when you're at close ranges after notching. I've noticed that RWS for the most part does not have this behavior, allowing detected targets to be locked up immediately, and so I've preferred it as of late.

RWS, 30 Degrees Azimuth, 4/2 BAR is currently the best for BVR from my experience.

Just came here to say that I finished the first 3 missions yesterday and have been enjoying the campaign a lot so far. I look forward to finishing it this weekend!

I've also noticed a lot of inconsistencies with the current radar performance, especially in TWS.

Great news. Excited to give it a go.

The issue's have been fixed with the latest Open Beta update. Thank you!

When carrying two C-701 A/G Missiles, when the first one is fired, the second seeker used to be turned on and looking at the current SPI, but with a recent update, this behavior was removed. Now when a C-701 is fired, the second seeker is turned off, requiring the "On" button to be pressed. Along with this issue, after the second seeker is turned on, and the lock button is pressed, the seeker is stuck looking at the previous target/area that was fired on with the first C-701. The C-701 Seeker screen also displays "Bug" at the top when it's stuck. To get the second seeker unstuck, you'll have to press the "SLAVE/SP" button twice to get the seeker back to the SPI so you can ground lock and move the seeker with the TDC to another target. Also, switching between profiles or pylons, results in the C-701 Seeker turning off. So you won't be able to turn on the second seeker, since switching between pylons/profiles turns the seekers on both C-701's off. I've attached two track files, showcasing the issue with both the C-701IR and C-701T. Along with this, I've made a quick YouTube video showing and describing the issue: C-701IR Bug.trk C-701T Bug.trk

Disable Zeroizer before repairing. It's labeled "Seat Function" at the back left of the cockpit.