I rely on the external DLL SDK to drive a motion system. Unfortunately, with the recent update it no longer functions properly.
Note: I don't know if the latest release caused the problem: I didn't run FS2 for a while. The release in question is 22.214.171.124 (by the main exe file info). I have a fairly old backup of 126.96.36.199, and if I run it, everything works fine.
The problem is this:
- The main update function, Aerofly_FS_2_External_DLL_Update(), seems to be called at only 10 Hz instead of every frame (or ~60 Hz). (As an alternative explanation, the first argument, delta_time, may be incorrect: I haven't checked it, but this is less likely).
- Acceleration-related data, namely Aircraft.Acceleration and Aircraft.Gravity, are non-sensical: they contain strange peaks about every second and zero most of the time. At the same time, Aircraft.AngularVelocity is correct.
The latest SDK update is from 2018-08-23, more than half a year old. I had my plug-in compiled with an even older SDK (2017), and now I tried with this new one, and the result is the same. (Anyway, the changes between them are not significant for this task and are (supposedly) non-breaking, and all have TM_DLL_INTERFACE_VERSION = 1).
Are there any unannounced changes, or it's just a bug? Could the developers fix it? One cannot drive motion with broken data like this...