I mean I'd prefer if they add vo2max display natively anyway since it's almost 2021 and there still can only be two CIQ datafields on all watches
What I am talking about is how firstbeat "performance condition" is calculated after approximately 10 minutes into a run but it's obviously based on the realtime metmax translated into vo2max via metmax/3.5
METmax is an oxygen intake measure, firstbeat's take on vo2max
The problem is the stored long-term vo2max that is shown to the user is not the realtime metmax obviously since PC can surge to +5 or even +9
I believe what is happening is after 10 minutes into the run the watch calculates a new vo2max temporarily from the realtime metmax for that activity, then after the activity the realtime metmax is used to calculate a new vo2max
So an extremely helpful native datafield would be (realtime) "vo2max +/- performance condition"
ie. 55+1
or 50-2
or since it's almost 2021 and even strava now shows single place decimals past few years, how about extending vo2max and performance condition to a single decimal?
ie. 55.1 - 2.1
or at least give users a plain vo2max datafield so a custom display can be made, top vo2max, bottom "performance condition" (or 4 field side by side would solve that too)
Am I mistaken, can CIQ datafields access metmax? In FIT files it's global 140, local 7
TLDR; right now I can only show Performance Condition as a native datafield, ie. +1 -2, etc. but +5 and +9 only tells me there is a new realtime vo2max being used as a baseline that I cannot see so "performance condition" is meaningless