I've already setup a Bug Report for some time, which is now completed.
forums.garmin.com/.../bug-reports
Since I haven't received any response, I suppose this has been corrected for future releases of the SDK/Sim. So I look ahead for the next release.
Maybe this is also interesting for you
Investigating a little deeper the problem, seems that time is correct as well as Cadence and HR coming from the FIT files but the distance coming from file is overestimated. This causes troubles in PACE calculation.
Can someone double check ?
I am using 3.1.8 SDK.
Yes, you are right, it's only elapsedDistance that is wrong.
If you run the app directly on a device elapsedDistance is correct.
If you use the option 'Simulate Data' in the sim elapsedDistance is also correct.
But I think elapsedDistance is not stored in the .fit, rather it's calculated from the lat/lon's that are stored.