This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Racing an Activity Problem

Former Member
Former Member
Got my Forerunner 645 a couple of weeks back as an upgrade from my tired FR230. So far, reasonably good. Quite a few crashes during the night which seem to have been down to custom clock faces, so I've had to scrap those, but otherwise stable .

Anyway, I did a race against a previous activity tonight and wondered if I was missing something. I was expecting there to be a time ahead/time behind just like there is with virtual pacer but it only showed ahead/behind and no time. Where I'd expect to see the time, there were a bunch of dashes. Distance counted down as expected, changed to ahead/behind as I sped up/slowed down, but never did I see a time shown.

Am I missing something? I even tried to race against the activity I'd just ran, and that did the same thing. So it wasn't a problem with the original activity that I was racing against .

Thanks
Mike
  • However I'm still wondering, what the small superscripted numbers in front of the total estimated time mean.
    This makes me confused. Does anyone have an idea what they mean ?


    Those are hours.
  • Those are hours.


    Thanks WillNorthYork

    When it is like this, then this issue is definitely not fixed yet.

    I have stored a new run of approximately 30 minutes (already done with firmware 4.0).

    When I wanted to run against this activity, the estimated total time showed something like 1 (hour) 30 (minutes) right after start.

    Sometimes the hours have even further increased within few seconds.

    When I bought the FR 645 Music everything was working well.
    This was BEFORE firmware 3.40 !!

    @Garmin
    @Garmin-Joey

    Now we have gone through firmware 3.40, firmware 3.70 and firmware 4.00 .. and Virtual Racer is still not working well.
    Sorry, but this is a shame, as it was working BEFORE firmware 3.40 !!

    What has happened and how long shall we wait till this feature will work well again ??
    Virtual Racer was a main reason why I have switched from FR 235 to FR 645 Music.

    Garmin is aware of this bug since longer time.

    See also German Forum:
    https://forum.garmin.de/showthread.php?78039-FR-645-M-Virtual-Racer-run-against-a-previous-activity-BUG-in-FW-3-40

    Thanks
  • Thanks WillNorthYork

    When it is like this and these numbers are hours, then this issue is definitely not fixed yet.

    I have stored a new run of approximately 30 minutes (already done with firmware 4.0).

    When I wanted to run against this activity, the estimated total time showed something like 1 (hour) 30 (minutes) right after start.

    Sometimes the hours have even further increased within few seconds.

    When I bought the FR 645 Music everything was working well.
    This was BEFORE firmware 3.40 !!

    @Garmin
    @Garmin-Joey

    Now we have gone through firmware 3.40, firmware 3.70 and firmware 4.00 .. and Virtual Racer is still not working well.
    Sorry, but this is a shame, as it was working BEFORE firmware 3.40 !!

    What has happened and how long shall we wait till this feature will work well again ??
    Virtual Racer was a main reason why I have switched from FR 235 to FR 645 Music.

    Garmin is aware of this bug since longer time.

    See also German Forum:
    https://forum.garmin.de/showthread.php?78039-FR-645-M-Virtual-Racer-run-against-a-previous-activity-BUG-in-FW-3-40

    Thanks
  • Yeah, looks like something is going on with the Race an Activity feature. I have tried to recreate the issue and was able to once, but other activities have worked as expected. We are looking at this to try and determine what has occurred.


    And please report about the status.
    When will this issue be fixed finally ?
    At least the shown total estimated time right after start seems still to be incorrect with firmware 4.0.
  • Those are hours.


    Thanks WillNorthYork

    For me not understandable why Garmin needs so much time to fix this once again.
    As we all know, this was working well before firmware 3.40.
  • Unfortunately, these days it seems like it doesn't pay to be an early adopter of Garmin devices. 935 owners who bought at launch can probably relate to all of these problems. I'd say it took 6 months (or more) for the most egregious bugs to be squashed....
  • Push! Look at the date and what has been done in the meantime !?

    @Garmin-Joey

    Waiting for an answer about current status for fixing this problem. Thanks
  • I tried this again yesterday and it still doesn't work. By my calculations, in another couple of months it will be a year since it broke.

    Is anyone from Garmin able to comment on when we can expect this to be fixed. We haven't had a firmware update for months
  • Also related to this thread ..

    I got a reply from the german support last week that they have checked my reported issue and that they can't detect any difficulties with latest firmware.

    They have referred to the old firmware version 3.40 which I have informed about when I wrote the problem in the thread of the forum several months ago.
    Ok, so far so good. And I also recognized that something has changed between firmware 3.40 and actual firmware 4.20. However I also still noticed a strange behaviour again of this feature which I couldn't explain yet and to be honest, I don't want to try it again and again when I know that something is wrong with it.

    Strange that Garmin can't discover this strange behaviour by themselves.
    So this is probably the reason why nothing is being done for correction.
    Garmin assums that everything is ok :-).
    The fault is the user which has not their latest firmware 4.20 (which is still buggy as we know) :-).

    I have complained it again to the german support and that they shall check all 3 (or meanwhile even 4 threads regarding complaints on strange behaviour with the "running against a stored activity" feature). Let's see if they will change their mind then and if they will give us a bugfix soon. I hope so after waiting many many months meanwhile :-(.
  • This doesn't work for me on a Forerunner 645m, it always states that I am ahead. Bit late I know but did anyone here get it to work?

    Thanks