This started happening several weeks ago.
ECLIPSE (latest). SDK (latest). DEVICE (Edge 1030)
I start the simulator. This happens regardles of the start sequence... hit the "play" arrow then START or the other order.
Maybe 25 to 30% of the time, "elapsedDistance" stays at ZERO. While the other simulated variables, such as "currentSpeed", power, HR, cadence, etc generate a valid value.
My code looks for distance more than a small value > 0, to initiate some actions that occur after the athlete actually starts moving. I can just ignore distance, but this seems to be just a simulator bug, and detecting movement is a valuable trigger for my use.
