To build motion cueing rigs, the vehicles proper accelerations are needed to feed to the motion cueing algorithm. Also to derive correct aircraft performance charts from flight data recordings or write custom autopilot routines as well as custom flight control laws, these proper accelerations in all axises are needed.
In simple terms: The accelerations that your smartphone would measure if it were mounted to the aircraft!
Asobo have to a certain degree acknowledged that by implementing a variable called SEMIBODY LOADFACTOR X …Y …Z in FS2020’s Simconnect interface. To the best of my knowledge this variable was neither present in P3D nor FSX nor any previous version.
Unfortunately only SEMIBODY LOADFACTOR Y (vertical acceleration aka G-load) is implemented thus far. SEMIBODY LOADFACTOR X and Z (lateral and longitudinal) are not supported. They send only zeros.
I am writing this, to raise awareness that these variables are at the very core of any add-on that deals with the flight dynamics of the aircraft and need to be implemented for 3rd parties to access.
Especially in the light of there being one of them implemented correctly already and the others at least having been set up for (hopefully) future use I am wondering why those X and Z variables were not supported from the start. Here’s an excerpt from the SDK documentation.
Can anyone from Asobo comment as to whether/when these variables will be supported?