Oldguy

Why not use the last WHQL driver? I've a GTX 970 SC from EVGA and they work without problems (version 358.50). I'm getting anywhere from 75 fps to 120 fps @1920 x 1200 on high quality settings in 1.5, just flying around one of the airports. Seems ok to me.

That's what makes this so much fun: roll-your-own adventures.

Amazing!!

That is sometimes the case; the PayPal account is often different from the business entity itself. Doesn't PayPal guarantee the purchase?

Outstanding!!

Nice troubleshooting; that took lots of effort.

Try CAM by NZXT.

Wild guess: MiG-15 because of the proportionally shorter fuselage and less overhang of vertical stabilizer at jet nozzle, as best I can make out. As for photo realism, I cannot imagine how any airplane could accomplish that, but it is a fun Photoshop if nothing else.

1) You might also check the power-saving settings in W10 under device manager; it is notorious for trying to save every micro-watt. Your system may be going to sleep causing some elements to go into hardware power-saving mode. That would give a black screen. 2) Make sure you are truly in full-screen; DCS runs in frame-less window mode when you choose 'full-screen' under 'options'. LEFT alt-enter forces true full screen. Maybe that will help.

yes, it works on most machines, regardless of hardware, by way of a configurable overlay readout.

I occasionally have micro-stutters in every program if I have a lot of background, hard-drive access. You could look at that, since everything else seems to be ok. You might also check to see if your USB controllers are powering-down; I think the W10 default sets that behavior to 'on' in the power-saving section. That seems a possibility, since only USB devices are causing the problem.

Use NZXT's free overlay utility. Low-drag, high-speed info.

What video card?

Use Hwinfo to see where the choke-point is after you run the program. It's a free utility that records many variables of system performance over time.

Are you sure this is the right mission? I saw an SU-27 shoot down an SU-25 with radar missiles. I stopped watching about 2 minutes after splashdown of the SU-25 corpse.

Everyone's answer is correct. You do not need to speculate, however, since PC systems are so idiosyncratic. Grab a couple of the very useful and free system monitoring utilities readily available. Two that I have encountered as being particularly helpful and of low-impact are Hwinfo and NZXT's CAM. Both are hardware-independent, meaning you do not have to have any particular hardware installed in your machine to make them work. CAM gives you a nice recording instantaneously (you can also use it to monitor your PC from your smartphone), by way of a screen overlay. Hwinfo produces a record for the whole session over time. They also let you assess CPU/GPU % usage performance and temperature, both of which critically affect game play. In simulation settings, high graphics enabled, 1920x1200, I rarely see more than 2.5GB system memory in use. During the same exercise, I saw 2.2 GB video card memory in use. With today's connected community, there are lots of resources available (these are just the two that I have found to be low-impact and flexible) to let you look at how things really are performing. Have fun in the (un)friendly skies of DCS!

I just traded my R9 295x2 for an EVGA GTX 970 SC and couldn't be happier; my problems all stemmed either from AMD driver issues or Crossfire micro-stuttering. On the other hand, I have a nice R9 295X2 and FX9590 for sale!

Have you tried adjusting Gamma in 1.2 to lighten them?

I read in the notes for the upcoming 1.5 that DCS 1.2 uses two separate executables for UI and the actual game world; probably why you see the change in overlay icon when you launch. ED says that 1.5 is a single executable, so if it does, indeed, use two GPUs, then you should be in good order. BTW, I shifted to an aircooled EVGA GTX 970 SC, and the 1.5 open-beta gives wonderful frame-rates. Have you tried it with your R9? (If DCS does actually work with SLI/Crossfire, I may ressurrect that video card.) AMD drivers are my problem: other game programs tap both R9 cores, but they don't like the AMD Crossfire, which results in lots of micro-stutters; all of which are gone with my Nvidia card.

Well, I just retired my XFX R9 295X2 because of AMD driver weaknesses, so I have some experience with the card; what power supply do you have running it? How does that PS compare to your overall system needs, all PC equipment included in your calculations? Perhaps the system is simply throttling the second GPU when the power demand is too great. I ran mine, with an FX9590, using a 1200W PCP&C PS, and I had no issues with it, neither with power or cooling. But I am selling them both off, actually. What frame-rate do you get with just one core running?

Hmmm, since I have all but the campaign, how about that one, please?

the wonder of things both large and small Thanks for sharing this perspective...

Just like real life, lol!

I think that the consensus is pretty much on-point: HP was a really good maker of corporation-style computers a while ago. They have not done so well of late. If you are not comfortable with building one, then check out some of the smaller custom build shops, to see if they can screw one together for you within your budget. Websites like GPUBOSS and its affiliated CPUBOSS, give you some great info about the relative strength of these two major components. Then take a look at generalist websites, like Tom's Hardware and Anandtech, for reviews about all sorts of other PC components for their performance value. For DCS, it is important to get a CPU with a strong single-core performance coupled with a decent GPU to back it up. For instance, if the CPU you are looking at is the i7-4790K; it's pretty potent; the GPU, on the other hand, is pretty anemic. Not a particularly good combo. That info I found on Tom's and GPUBOSS. You can do the same; it's lots of fun, actually...I've built many in my day. Enjoy the journey!!

Two polite suggestions, because I liked the video compilation and the music: 1) try to find a way to use your cockpit panning more smoothly; the jerkiness reduces the immersion. Are you using keyboard? 2) for me, moving forward and backward in the timelines is a bit jarring, theatrically; it's hard to be involved in a takeoff roll and then switch back to an in-cockpit moment where the aircraft is just beginning to taxi away from parking. I have a quick question though: how many times did you have to try that belly tank drop before it did not hit the filming aircraft? Just kidding (a little). Otherwise, I like the variety of scenarios, even if I can tell it is a compilation, not a singular experience. You're doing great; my comments are from the vantage point of a movie goer, not a movie maker.