Multi-body computation is just one specific AWES automation challenge for certain architectures. Weather is another complex challenge. Exception handling of any kind is a huge automation gap. MTBF is accordingly too low for AWES automation.
Self-driving cars currently require a human driver to intervene as necessary, just as a serious AWES requires a Pilot-in-Command (PIC). Despite decades of progress, cars are not fully autonomous yet, which will take more years to happen. The general timeline applies for AWES, with similar challenges.
What is Ampyx MTBF for AP1-2? There have always been Ampyx videos to watch, but no open flight-log data. A sample exception state is how the AWES reacts if a wing or control surface fouls on the tether. There are hundreds of plausible exceptions known, and many unknown. Ampyx has not had enough flight hours (>100khr) to find many hidden exception states.
Another interesting source of computational complexity are the 6DOF oscillations of any body in space. These are effectively quasi-multi-body effects, internal to each body in an AWES, but multiplied by all external multi-body motions, imposing practical intractability for now.
Ampyx needs a lot more money and time for computability and lifecycle survival to mature.