Was the [MS] tag fixed?

@russellcresser i think i figured it out. Its seem refreshing rate is close to 1/10 of a sec…but before it print to your watch there is a few milliseconds lag. So it becomes e.g

101 ,202 ,103 ,105
And so on.

Instead of exactly 101,201,301…

That why u see it like in my video. Its somewhat looks random but its due to lag time.

With a 2ms lag…it will take close to 1 sec to see the change of 0.010

I tested it on my console program with 1/10 sec refresh rate. The behavior is as such.

For wfs preview…i think its slower like 1/20 sec.

That my testing and current findings

P.s lags are unavoidable but can be optimise code to reduce it

@matze_styles4you and @russellcresser

By the way i made a mistake in my floor formula previously, it should have been

((Floor([MSEC]/100))*100)

Or

For sec_msec

((Floor([SEC_MSEC]*10))/10)

2 Likes