10 October 2017 | Version 4.3.1
Greatest race app ever. I used it this weekend for the St. George, UT marathon. I set it for a 3:05 with no hope of getting it. For most of the race I was in front of my time until the last couple of miles. Ended up getting a 3:09. Loved using this app. Worked perfect! Thanks
1 October 2017 | Version 4.2.1
Great App. Works perfect on FR 935. Donation will follow. I will use it at Frankfurt Marathon in 4 weeks. Greetings from Switzerland
28 September 2017 | Version 4.2.1
Earlier tested, but used the datafield for real race purposes on Berlin Marathon.
It was absolutely great and the perfect help/solution!
Really loved it all the way long, forgot to push the lap button only once.
And I really needed it to achieve my goal, since my watch (fenix3) unfortunately significantly over measured the distance (43,14K)
The only other solution would have been checking the timer at the marks, which I actually did at 5/10/... but this screen had the added value with realistic numbers for average pace, ahead/behind and required perfect pace for the rest with finish time prediction as well!
I didn't have to change the screen at all, checked only this one along the whole race.
Well done and thanks! I'll need it in Frankfurt as well!
25 September 2017 | Version 4.2.1
I’ve used it during my last race in Paris.
So usefull and accurate.
Finish time prediction allows me to manage my pace perfectly. I’ve reached my objectives thanks to it.
I donate with great pleasur
11 September 2017 | Version 4.1
Fantastic run app! just used it to finally break thru the 1:55 barrier in my half this weekend. Been chasing this for a few years trying to chip away at it and always missed it by a minute or so. This app finally showed me where I was losing a few seconds and allowed me to fix it with enough time to achieve my new PB. The lap corrections on course were brilliant as well fixing my gps which showed me at 5:23 at the 5Km marker. Again at the 10Km, gps showing me at 10.13. Both fixes helped me realize I was behind rather than ahead. The ahead/behind red green screen was the most important piece for me showing me ahead by only 8 seconds with 800M to go finally giving me the push needed to break the 1:55. I think in the past without all this info and correction ability I was simply mentally losing focus, and assume also what I thought was maybe 500-600M left when in fact it was more like 800-900 due to weaving and gps slight errors. Cheers Peter!
6 September 2017 | Version 4.1
Best Garmin App ever
6 September 2017 | Version 4.1
Beware - Doesn't configure easily to Vivoactive HR. After futzing around for 45 mins, I thought I had the configuration right. Turns all I got was TOD and the "like it, donate" screen. Had to reset my watch back to factory settings to get anything to work. Careful. Interesting the developer tells you to read support before posting a "bad" review. Does that mean all issues belong to the user? Further, aren't ease of use and configuration issues worthy of comment to others? Careful. Cheers
7 September 2017, peterdedecker
If you would have read the app info page you would have seen that Peter's (Race) Pacer shows an initial data screen containing the Time Of the Day and Configured Parameters (as that is what people care for before the race starts - Did I configure the correct race goal time? How long is it until the race starts?). (If you want my honest opinion I do think that a large part of your user experience could be defined as user error (as you call it), ie. not reading the (complete) description and being surprised by the initial data screen). Connect IQ data fields can not have menu actions, therefore configuration on the watch is not possible. The only option we have to configure data fields is to do this through application settings: this means you have to configure the field via Garmin Connect Mobile or Garmin Express. I don't know why you had to factory reset your watch, pressing back to go to the main screen, changing your data screen layout contents or deleting the data field via Garmin Express/Garmin Connect Mobile seems like a more appropriate action to me. It is ok to leave negative reviews if you have an unsatisfying experience, but the review system is not meant for support questions. It would be unfair to ask people to READ the support topic, but I do prefer people ASKing support questions in the support topic when they have problems so I can assist them in the best possible way. Cheers, Peter.
22 August 2017 | Version 4.1
6 August 2017 | Version 4.0
Provides everything you need.
Simple to setup and to use.
Easy reading while running.
Worth the donation.
6 August 2017 | Version 4.0
Fantastic app. I'd tried other pacer apps and they all seemed unreliable, this one worked and did what it said it would.
It helped me to my first Half Marathon and also helped me pace at the local 5k run.
It's well worth the donation.
27 July 2017 | Version 3.5.3
Very good, I tried todday running with this data field and was accurate and useful.
12 July 2017 | Version 3.5.2
Excellent app, very easy setup, great functionality. Good to read. Highly recommended.
17 June 2017 | Version 3.5
Excellent app. I used it today to pace a 5K club run and it worked perfectly. The ETA field is so useful and was spot on.
4 June 2017 | Version 3.3
Excellent application, very easy setup, perfect functionality. I love possibility to adjust lap distance during the run. Well done Peter !
26 May 2017 | Version 3.3
Very good app! Useful features and clean interface. Well done, Peter!
18 May 2017 | Version 3.3
Favorite data field!! Invaluable to use during races and training!
27 April 2017 | Version 3.3
Perfect app for my marathon training and race. useful layout, and i like the function how you can adjust the laps during the run. I use it on Forerunner 235, no problems with memory or something else until now. Thx Peter for the good work! Donated it! :-)
24 April 2017 | Version 3.3
Thank you very much for the great Peter (Race) Pacer. Yesterday i run my second Marathon in 3:24:02 and your Data Field was amazing. THANKS THANKS THANKS
22 April 2017 | Version 3.3
Exactly what I was searching for. Took e a long time to find this one.
Happy with the functionality and the optin to record the "time ahead" withthe fenix 5x!
Donaition done! Worth every cent!
19 April 2017 | Version 3.3
Easy setup, perfect functionality. Highly recommended.
8 April 2017 | Version 3.2
I wish it was easier to add custom distance. It takes an added calculation to convert mileage into meters. I can't add in a decimal into the field so my distance isn't accurate. I wish I could put in predicted finish time over pace, again this requires added calculation on my part.
10 April 2017, peterdedecker
Hi Don, thank you for your feedback. Regarding custom distance to be entered in meters: the Peter's (Race) Pacer field is really pushing the maximum out of the available memory, when I would allow the custom distance to be entered in something else than meters then internally the field would need extra lines of code to convert this figure into meters and extra code (unfortunately) take extra memory (which is simply not available). Regarding the meters-value to be non decimal: I concur I would prefer a decimal value in here and in fact in version 1.2.5 this was a decimal value, but inconsistent behaviour between Garmin Connect Mobile and Garmin Express in transfers of float values by the API made me choose to opt for stability by choosing an integer value, when in the future float transfers become consistent and reliable I'll change it back. Regarding the ability to put in predicted finish time over pace: this is already possible for high memory devices (you can choose between the options Target Pace/Target Speed/Target Finish Time), for the older low memory devices (the connect IQ 1 compatible devices) you only have the option to specify the target pace as there's simply no memory to allow for the choice (eg on Fenix 3 device the data field is having a peak memory usage of 15.7k out of the available 16k). If you have an older device and you do want this choice then you might want to check out the app ( https://apps.garmin.com/en-US/apps/ea97af1f-1e5d-4541-820c-9bd994080d4c ) where I have more memory to play with and can enable all high memory logic also for low memory devices. Amongst others you will then have the choice to set a target finish time. Cheers, Peter.
12 March 2017 | Version 3.1.1
Annoying "like it-donate" on display.
13 March 2017, peterdedecker
I think I have been very generous by giving away all functionality in the program for free for everyone to enjoy. If you dislike the small donation encouragment message, that's easy to fix, you know...
Hint: read the encouragment message. ;)
5 February 2017 | Version 1.3.3
Using version 1.3.3 on a Forerunner 235, it crashed at mile 12, displaying a blank screen with just "IQ!" on it, leaving me flying blind a critical time. Later at home I looked in the "apps/logs/ciq_log.txt" file and found there was out of memory error. I was able to salvage the run by switching to a second screen which still had accurate data fields.
It's a very useful and well-designed data field when it's not crashing, but if you are going to use version 1.3.3 on a Forerunner 235, uninstall all your other CIQ add-ons for best results, make sure to keep useful stats on your second screen as a backup.
If I could rely on this data field not to crash during a race, I would give it 5 stars.
There's less likely to be a problem on the Forerunner 735XT, which has more memory.
6 February 2017, peterdedecker
Hi Mark, congrats on the personal best you achieved, way to go!
Please use the forum thread for future support topics. The out of memory error you see in the logfile is not from my data field, but from the "superb" watch face you're using. The "invalid value" error that made the data field crash (sorry about that) is coming from the connect iq framework itself and is unfortunately not something which is under my control, for details check the forum topîc I referred to. It could be that using another connect iq field (you're using it in combination with Runner Window) data field on another data screen enhances the chance of this error to occur. For the best stability don't use another connect iq data field in combination with this field. It's a wise thing to have a second screen as a backup, personally I use as a second screen native distance/speed/time/heart rate combo.
It's stable for me this way in this setup: past saturday I did a 6 hour training run with the field and it performed beautifully.
2 February 2017 | Version 1.3.3
Great lay out. Very good support.Its perfect for the forerunner 235 for using as a pacer.
30 January 2017 | Version 1.3
Great layout, and I love how you can adjust the laps during a race. Well done.
30 January 2017, peterdedecker
Thanks! Enjoy the field! Cheers, Peter