Simulator Bugs

I'm attempting to collect as many of the simulator bugs as I can right now. We're aware of several issues (intercepting the light button when it shouldn't, font inconsistencies, etc.), but if there are any others you have not already seen reported or discussed here in the forums, please let me know.

Keep in mind that this is a simulator and not an emulator so it's unlikely that we will do much in the short term to address things like simulator speed/performance vs. device hardware.

jim_m_58 over 10 years ago

Not sure if this is a bug or a feature, but when you use FIT data, if you "simulate" data, it seems to run at a normal speed, but if you play back and existing .fit file, it's VERY slow (like new data every 5-10 seconds)

Heading data is always "0 degrees" in both cases, and the quality is always "QUALITY_LAST_KNOWN";

Sforzando over 10 years ago

I've noticed that if you periodically pulse the vibration motor (say once or twice a second), the simulated watch will shake so much that the simulation isn't too responsive to key presses anymore.

travis.vitek over 10 years ago

Not sure if this is a bug or a feature, but when you use FIT data, if you "simulate" data, it seems to run at a normal speed, but if you play back and existing .fit file, it's VERY slow (like new data every 5-10 seconds)

It appears that this is because the smart recording feature was enabled when recording the .fit data you are playing back. If you enable one second recording when making your .fit file, it behaves as expected. Of course the simulator could interpolate the data between each point, but it does not do that currently.

jim_m_58 over 10 years ago

It appears that this is because the smart recording feature was enabled when recording the .fit data you are playing back. If you enable one second recording when making your .fit file, it behaves as expected. Of course the simulator could interpolate the data between each point, but it does not do that currently.

The .fit is from a vivoavtive, and I don't think there is a way to enable 1 second vs smart recording. As it is, playing back a .fit from the vivoactive looks really odd...

rconradharris over 10 years ago

The Forerunner 920XT simulator gives two different results between:

a) The width in pixels of a string
b) The sum of the widths of each character in a string

I don't own a Forerunner, so not sure if this happens on the device or not.

This appears to only affect the Forerunner and not any of the other simulated devices.

Test code

var testString = "When in the course of h";
System.println("width of whole string=" + dc.getTextWidthInPixels(testString, Gfx.FONT_MEDIUM));
var sumOfCharWidths = 0;
var curChar, curCharWidth;
for (var i=0; i < testString.length(); i++) {
    curChar = testString.substring(i, i + 1);
    curCharWidth = dc.getTextWidthInPixels(curChar, Gfx.FONT_MEDIUM);
    sumOfCharWidths += curCharWidth;
} 
System.println("width of sum of chars=" + sumOfCharWidths);

Results:

FONT_MEDIUM
    - fr920xt
        width of whole string=199
        width of sum of chars=177

    - epix
        width of whole string=205
        width of sum of chars=205

    - vivoactive
        width of whole string=205
        width of sum of chars=205

    - fenix3
        width of whole string=221
        width of sum of chars=221

Cross-posted this from another thread I created: https://forums.garmin.com/showthread.php?267192-Fenix3-Simulator-Width-Calculations-Wrong

lightmatter over 10 years ago

The font sizes don't match to actual for FONT_NUMBER_MEDIUM on VA (unless it was fixed in the 1.1 update) and possibly other font issues as well.
-see https://forums.garmin.com/showthread.php?228297-Vivoactive-Built-in-font-problem&highlight=font_number_mild
or https://forums.garmin.com/showthread.php?261584-Epix-vs-simulator-fonts&highlight=font_number_mild

Also, if the simulator is running and you "enter low power" mode, and you start another watch face, it will start with the face in regular power mode, but the settings are still checked as "enter low power" in the simulator menu, and it won't let you re-enter low power mode if it was already checkmarked, so you're forced to have to "exit low power" (which does nothing because that's the mode the sim started in) and then change back again to get back to low power. It should either use the power mode that the previous sim was in, or reset the power mode selection to exit low power like it is when you kill the previous app and start fresh.

Former Member over 10 years ago

The Forerunner 920XT simulator gives two different results between:

a) The width in pixels of a string
b) The sum of the widths of each character in a string

These two values should not be equal except by coincidence. I gave a more detailed response in your thread.

travis.vitek over 10 years ago

This issue reported last month appears to only occur in the simulator.

Travis

Nikeow over 10 years ago

https://apps.garmin.com/en-US/apps/542affcf-e440-43d4-a118-5aa3bba2f14e

if you look at the screenshot of that app, you will not the TOD and the HR data fields are ON TOP / touching the horizontal line on the simulator. On the watch, it works perfectly and there is a couple pixels worth of separation

Brandon.ConnectIQ over 10 years ago

@NIKEOW I think this is probably due to the FONT_NUMBER_SMALL size difference between the sim and the device. This has already been fixed and is under review right now.