• You can't have a perfectly smooth windshield on both sides because of the asymmetry;

• Control surfaces are limited: no spoilers overlapping flaps, no end balance tabs attached to main control surfaces, no partly buried flaps, no cut lines perpendicular to hinge line.

The first one is low hanging fruit; the second is much harder but not impossible. Both would make Plane Maker-only aircraft pretty decent to start with.

The biggest limitation to instruments are their single dependency: show if this dataref <=, = or >= to n. Take an idiot-light annunciator, for example: green if tank pump moving fuel; orange if fuel low; red if fuel exhausted; off is tank pump off.

It's possible to include some logic by simple boolean combinations. All that is needed in this case is an additive dependency at the top: Requires Bus1, Bus2, Avionics, AND Pump is On, (AND EFIS page is p, AND… whatever).

1. You can't use the prop disc tech unless your plane has…a prop.

2. Jet fan discs do not suffer the problems that causes all of the prop disc issues:

– Prop discs are translucent geometry outside the plane that interacts with scenery.
– Prop discs can be viewed from the side.

So…most authors just make a separate rotating disc out of an obj for jet discs, and since they are fully inside the engine housing teh Z and translucency issues are not issues.

http://xplanescenery.blogspot.com/2009/01/scripting-line-in-sand.html

Basically the C ABI provides a base level with maximum power/flexibility, and what we need now (from LR or a third party) are layers on top that increase abstraction and simplify ease of use at the expense of some flexibility and performance.