Change Log:
- Fixed an issue that could cause Track Run workouts to over-report distance.
- Fixed an issue that could prevent Lactate Threshold Heart Rate auto-detection from working correctly.
This update is Live as of March 30th 2:15p Central Time.
Change Log:
This update is Live as of March 30th 2:15p Central Time.
I'm sorry everyone. I think this might all be my fault. A few years ago I was weighing up whether to get a 245 or a 645. I stupidly thought that the 645 was higher up the food chain and would get equal…
100% agree with you , once you workout more than 1 hr the number get smaller & smaller ( hh:mm:ss ) .
Not sure why UX / UI team didn't do anything about this.
Seriously? No short-term/long-term load ratio on the 255? It's honestly getting to the point where I'm going to return my 255 and buy a Coros because I can't stand Garmin price-locking their software features, especially when the software is user data-based. I'd get mapping-related differences or other things to do with storage/hardware, but the fact that they aren't bringing a simple x/y metric to the mid-tier watches is infuriating.
there is load ration on the 255 now. Downloaded the beta just yesterday.
Yes, it is hidden away under acute load on the training status widget. Once again, Garmin's change logs are extremely poor. Let's hope they do not remove the metric in the next update.
What's the difference between load ratio (255) and short/long term load ratio (955)?
When I click the start button, it tells me the following: Load ratio compares your short (acute) and long (chronic) term training load. It's useful for monitoring training load changes.
Agreed, apart from features linked to pre loaded maps and golf courses, they should have the same software.
Pre loaded maps and golf courses is enough justification/incentive for the higher price/larger format for the 955.
They can run the same software across the Fenix 7, 255 and 955, which will mean much less bugs for everyone.
It's not just the hour that is too small. Look at the photo attached. I can read the actual data on both screens but the headers are smaller on the larger screen of the 255 and I can't read what the data is referring to. I could just about read the 645 headers. There is so much white space which is wasted. I've tried memorising what the headers say but I have about 5 pages which I scroll through, each with about 3 or 4 items per page. This means I have to memorise what approx 17 headers say! When you want to just glance at the watch for a quick check it is really difficult.
That is a modern design trend. I would also prefer larger text and less white space, but the designers think it looks old fashioned.
If that's true then this will probably be my last Garmin. It's certainly the last Garmin I will buy before seeing it first. None of the reviews I read pointed this out. The watch is probably fine for most younger people but as I get older I need bigger not smaller fonts. I wouldn't have bought the 255 if I had known how difficult it would be to read. I may cut my losses and sell it but I don't know what to replace it with. I'm still hoping that Garmin will eventually offer the option for users to select font size. I can do that with my Wear OS watch and I can read it fine. It seems such a basic feature and it would be far more useful than the multiplication of metrics that I don't need and will probably never use.
I make some screens with few and important data I need to see, and study the details on my computer screen after I am finished with the workout.
I do that as well but some things I want to see as I'm running. Pace, cadence, power, etc. I've found a great Connect IQ data field which has very large fonts but there is a really annoying limitation that you can only have two of these. It sounds like I don't like Garmin! I do. It's the best there is in so many ways but it could be so much better.