Bug: Activity.Info.elapsedDistance is way off if playback a .fit file using simulator 3.1.6

Now I've switched the units to miles and made a short run activity. But as you've already mentioned it hasn't any effect to info.elapsedDistance.

Garmin Connect shows my total run distance = 2.67 km .

I've replayed the entire .fit in the sim using System.println(info.elapsedDistance) . At the end of the .fit the sim stops with info.elapsedDistance = 3769.1 m . This is again 39% off.

But the running time from GC coincides very well with info.elapsedTime.

You've said: "... my distances are correct with the fit files I've tested. (some past 5k's etc)"

Please tell me how did you've checked that your info.elapsedDistance is correct? Have you replayed your entire 5K .fit and compared it to info.elapsedDistance = 5000 m at the end?

For example, if you look at the API guide:

elapsedDistance ⇒ Toybox::Lang::Float
The elapsed distance of the current activity in meters (m).

and this is what you need to do to display it:

var actInfo=Activity.getActivityInfo();
var devSet=Sys.getDeviceSettings();
var distVal=0.0;

if(actInfo.elapsedDistance!=null) {
	//elapsedDistance - distance in meters
	distVal=actInfo.elapsedDistance;
	if(devSet.distanceUnits==Sys.UNIT_STATUTE) {
		distVal=distVal* 0.000621371;
	} else {
		distVal=distVal/1000;
	}
}

//display distVal (miles or km)

The data in a .fit is always metric.  When you play it back your app sees metric.  If you want to display statute (based on the setting) you do that conversion in your app.

You can see this by looking at Activity.getActivityInfo() in the API doc.

OK, thanks Jim, I've understand. The settings in the sim are only for testing the settings on the real device. The settings in the sim are only transfered to the app and the sim itself makes no actions regarding the settings. The app can request the settings and control the program flow and calculations of the values depending on this settings.

In summary my DF runs on real device or sim and it doesn't handle the units.

The difference only appears with sim "Playback File".

The thoughts of a conversion error for the units in the sim can't get me out of my head. If the .fit is recorded in miles and the app handles the miles by multiplication with the factor 1.6 to km then there is no error viewable. But if the .fit is recorded in km and there is also (improperly) a multiplication with the factor 1.6 the distance is 60% off. Or the sim uses the earth radius in miles vs. km for calculating the distance increments between the position points or somewhat else in this direction.

Soon I make a test recording my activity in miles and look at the results.

In a CIQ app, you see what that setting is (Sys.getDeviceSettings().distanceUnits for example), and you use that to display statute or metric in your all.  The sim just defines what you see in getDeviceSettings(),  Doing the conversion is all up to you.  This is how a real devices works.

Ad far as my comment, I was assuming that your app did things like pay attention to the GPS accuracy.  In my apps, I don't actually start recording until after there's a gps lock.  So the actual recording doesn't start until a .fit is being played back, even if the app is started before playback..