Guided LTHR test gone

Thanks for clarification. This is a major disappointment - not only their estimates seem to work on or off but you can't re-estimate it on demand when you actually need this. Giant step backwards imo :( 

In plus, it is called the Improved Lactate Threshold Measurement Feature 

Well, let's hope they will tune it up little bit soon.

To be honest I'm hoping more for a Coros model that supports map routing, those guys seem to be still passionate about running. I literally upgraded to Fenix7 Pro to have all the running stuff finally working. So now Garmin surprises us with removing features that did work. The watch had a feature called LTHR detection when I bought it. Now it has a feature 'LTHR detection if you are lucky'  Automatic LTHR detection was not working for me for past 2-3 years both on Instinct 2 (it worked maybe 3 times in early firmware) and on Fenix 7 Pro. I used to just do the LTHR guided test before season and mid season to adjust my stuff. Now it detected a very low threshold pace (5:00m/km) with very high HR (180BPM) - sounds ok, I was recovering from covid. But after hammering several runs with 8km with 4:40-4:45 and lower HR - no threshold detection (despite Garmin rating those runs 'threshold' and 'vo2max' - among other symptoms of getting back in shape like FTP going up etc). The VO2max is skyrocketting, but LTHR has to be calculated manually using average HR and table as if I owned Forerunner 55 or a stopwatch.

EDIT: and I did contact support regarding lack of LTHR auto-detection this and got a generic advice like from the manual. You know - just run hard or do the manual test. So I though - ok, I can live with that l ike I live with broken strength excercises that always autoscroll to next workout step so you have to scroll back 50 steps to see previous screen, or voiceover not being disabled for turn-based navigation. Or other stuff they don't care to fix, but push other broken stuff.

I've found the LTHR detection works best if I do a number of hard intervals and then some really, really easy intervals between. However, it's calculated, it seems to work with with a high degree of pace variation.  

Considering how well the max HR detection works (not good at all), I wouldn't be confident in the LTHR detection from sub-threshold runs, especially when that is done based on HR data from a wrist HR sensor. 

For me, the auto detection is the greatest s***t they could do with this previously well working guided test. Before the i bought the Fenix 7 Pro, I owned a forerunner 945 and my threshold was around 151 bpm and 3:50 min/km. Now with the autodetection it says 158 bpm and 3:29 min/km, wich is far away from what I can run for about a hour. And it doesn't matter how often I manually set the max HR to my well known value and manually set the lactate threshold to 150 bpm, the next time it promts me again to run at 158 bpm. Do you think a reset would work?

druidh said:

I thought it still required a chest HRM ?

No, it is no more needed.

Schmolle81 said:

Do you think a reset would work?

I do not know, it is possible, but it can get also worse. I would rather suggest, continuing a few weeks, and hoping the value gets more accurate after it gets the chance to parse more data. In my case it seem to be the case, though I cannot guarantee it works for you too.

Thanks for your reply, I will give it a try and wait some weeks. Even though it is like that for some weeks now. Let's hope.