BMCha

It looks to me like pretty much all the pictures on the site are renders from the CAD models. If you want to see the real thing you have to look at their videos (or photos that they've posted in various places, possibly including this thread). There's certainly plenty in the "Photos" section of the facebook group -- too many for me to repost easily. Here's the full size versions of the images in my earlier screenshot. Also, the question "When will extensions be available to order?" was replied to with "soon".

I've taken a screenshot of the FB comments for those without an account.

Looking at the diagrams in the OP (side view and the tiny bits in between the blur) and comparing to DCS I have to say I like what I'm seeing.

I am not sure whether the connectors in the throttle are all the same, but I do know for sure that the connector in the right throttle for the slew control is a Molex PicoBlade connector (which has a 1.25mm spacing), and it's likely that they've used the same connectors throughout the product.

Mine has this too. I've also always wondered whether it was normal or not.

Unlike most (or is it all?) of the other optical headtracking solutions, TrackIR does the point tracking in hardware and just sends that data to the PC to be turned into position and orientation, so the CPU usage on your end is minimal.

The other night I was running clean at 35,000 feet and managed to get it up to mach 2.2 (groundspeed 1200 knots, IAS in the 700s) after a good minute or two of level acceleration. It was still accelerating but I had just overshot my destination and so I terminated the experiment. It's definitely achievable though. A clean config and higher altitudes are the key here, as that reduces drag and also the speed of sound.

I've only skimmed over the thread and I know you've already ordered everything, but I'm running an LG 34UM95 (flat 3440x1440) on 2 Gigabyte 970s in SLI (and only a 4.5 GHz 2500K) and while I haven't had all that much time for DCS and the like recently, I remember performance being good. Enjoy your new setup.

There were some ingame screenshots in his screenshots folder too. (thumbnailed of course, but it looked the same as in that icon)

"топливо" = "fuel", so Mustang is correct.

I was able to rearm successfully at mission start without my engines on. Just had to open the side door (which DCS seems to see in the same way as the Ka-50's door or the A-10C's canopy; the cockpit windows don't seem to affect anything other than the visuals).

-snip-

Is your rotor brake off?

Playing the first mission I could never get it to advance past the landing at Tskhinvali. After a few attempts to make sure I wasn't doing something wrong, I opened the mission in the editor to check the trigger conditions. The problem appears to be with the altitude condition, which is currently set to "lower than 905m". The problem is that there are two 4-pad FARP objects at Tskhinvali, but the northernmost one is slightly higher up than the other. The trigger's <905m condition is only satisfied if you land at the lower FARP (PosTshinval2), while the upper one (PosTshinval1) is slightly too high for the trigger to activate. Its altitude condition needs to be raised by a few meters. Also, due to what I assume is the usage of two FARP objects, there are two entries in the ATC radio menu. This doesn't seem to interfere with the mission, but it is somewhat confusing having multiple "Shpora" entries in the menu. EDIT: I use imperial units in my F2 view, but converted into meters the landed altitude at the upper FARP is 906m while the lower's is 904m. So the altitude condition for PosTshinval1 should probably be raised to 907m or so.