Garmin is aware of this due to beta test reports, but I was curious to know if anyone else noticed the floor counter is giving credit for about 6 foot increments rather than 10 feet? I am in a hilly area, and have been scaling the Empire State Building daily according to my F5. Really I am not, but 110 floors is a bit much. Otherwise the elevation meter has been working very nicely with a faster response time than it used to, and hopefully that doesn't revert to fix the floor counter.
Anyone note that abnormally high floor count yet? It is likely why it wasn't officially released I am guessing. I just haven't seen anyone else pick up on this problem yet, and why I am asking to see if it just my unit. Thanks,
about the floor count, I also observed an abnormal floor count, but only when counted during activities (my floor count during the day seems normal). I noticed that for the 2 runing and trail activities I did since v12.00, my floor count showed almost two times more than should be (I'm using meter units, so I do not make easy translation to you feet counts...) notice that I have a stock watch (12.00 firmware since last Saturday, 6.20 Sensor hub, never installed any beta). My floor counts during activities before 12.00 and/or 6.20 sensor hub seemed fine.
I see the same issue regarding floor count being abnormally high. Im on fw12.0 but senhub 6.20. Floor count during non-activities seems spot on, but during outdoor running or walking activities it seems to double or triple what I would have previously seen. This is not an issue using indoor based activities ie elliptical or rowing so that leads me to think it is gps based inside fw12.0 that is causing these issues. just a guess though.
