I've decided to run my first half marathon in June. At present I have no suitable running shoes to run outside. That's why I started to run the entire New York and London routes 3 to 4 times in succession with a moderate speed of 12 to 14 km/h (7.46 to 8.7 miles/h).
I've already learned that the speed- and high-knees-tests are basically the same and that there seems to be a limitation of the maximum running speed of 20 km/h (12.43 miles/h). But today I've noticed that there seems to be a limitation of the high-knees detection, too. If a particular, fairly high frequency is exceeded, the detection misses single knee lifts and I eventually get no points for it.
For the evaluation of my progress, the point and timing results are much more important to me than the calorie count.
Can someone confirm my observation?



Reply With Quote
What I find happens though is sometimes the tracking just cuts out completely and it says you're running at 0 mi/h or something daft like 0.6 mi/h. Nothing has changed in my room layout so I don't know why this has started happening. I've recalibrated the Kinect a couple of times too but still it happens. Very annoying at times.



I have found that running position can affect your speed. That is, if I drift to the left or right while running in place my speed, as seen by the game, is affected. Be sure that the arrow in front of you on the screen is in the very center of the running track. For me this means I must position myself slightly to the left of my TV screen.

