The ES-30 is very clearly unfinished, overhead panel lighting is bugged, “ON” inscriptions don’t properly illuminate, or don’t illuminate bright enough to differentiate them from switches in the off position. The HDG and ALT select knobs on the autopilot panel are swapped (HDG knob controls alt selection, ALT knob controls heading), There is no altimeter baro correction control, and there is no avionics dimmer control, this is especially irritating at night, when the EFIS screens are excessively bright. Funny enough, the screens also appear too dim during the day. These bugs although annoying don’t completely break the aircraft, but there is a problem that does make this aircraft completely unflyable, and that is the engines. The engines on the ES-30 are completely bugged, on the ground, when the throttles are advanced to takeoff power, the engines are limited to around 1200 RPM and fail to produce sufficient thrust and the aircraft accelerates remarkably slowly. I have yet to successfully get the aircraft off the ground before colliding with an object at the end of the runway. On that note, the aircraft gets trapped in a perpetual respawn cycle after you crash, because the simulator respawns the aircraft at an airspeed of 280 knots IAS, which is 30 knots over Vne, and causes the aircraft to overspeed within 5 seconds. It is possible to pitch up enough to bleed off the speed quickly enough to save the aircraft, but your timing has to be almost perfect. Back to the engines, another behavior I have observed is a failure of the constant speed function for the propellers. When power is reduced to flight idle, the engines appear to remain in a high power output state and propeller RPM increases to around 5000 RPM. It’s almost comical, if not frustrating how broken this aircraft is. I personally am very disappointed in the state in which this aircraft was released, the ES-30 was one of the aircraft I personally was really looking forward to flying in the new sim, but you can’t even get it off the ground.
UPDATE/EDIT
I was able to get the ES-30 flying, the issue with takeoff power seems to be intermittent, but there are still bugs with the throttles/engines. I had almost completed a flight from KMSP to KCWA, when on final, the electric engines gave out and stopped producing torque. My first indication of failure was the flaps failing to extend and the aircraft beginning to slip under the glidepath. No biggie, I increased my set airspeed to allow the passive auto throttle to kick in and I prepared to conduct a no-flap landing. It was at this point that I realized that the throttles were firewalled and I was still losing airspeed. I checked the torque indications and engines 2 and 3 read 0. I realized now that my flaps had failed because the aircraft batteries were likely dead. Despite both of the turboprops being at full power, those itty bitty PT6s just don’t have enough horsepower to keep this thing airborne on a 3 degree glidepath, much less straight and level. I attempted to ditch in a field short of the runway at CWA but crashed into a tree line. I was then respawned at 280 knots and paused then ended the flight before the aircraft suffered an overspeed failure. Long story short, there is definitely a problem with the batteries draining too quickly and a lack of redundancy for emergencies. Furthermore, there is a serious lack of functionality and proper indication of system parameters from the ES-30’s G5000 avionics suite. The PFD image is slightly cropped off of the right edge of the screen, I noticed this by looking at my aircraft ident in the top right corner of the PFD and observing that it was cropped off the edge of the screen. The MFD map range also cannot be adjusted currently.