Nathan and I have been going back and forth with problems that I am occuring with BCN 2.5.9 espically having problems with the tracking mode. Wondering if any other members having problems in the tracking mode. Example, when the tracking line refreshes it does not keep up the your movment. I lags behind. And with the further you go the lag time increases. Just wondering anyone else having the same problem.  I know Nathan is trying to figure out the problems that I have email him.

Yes, I am having the same problem. I read your post and was hesitant to upgrade (from 2.5.4) but I did and just got back from taking it for a test. The tracking arrow lags way behind my actual position. It appears that this is because the entire track redraws itself on the screen. As the track gets longer the lag gets worse because of the redraw time??? When I got back from the drive to the parking lot that I started from I waited about 30 seconds for my trip to finish, meaning the nav line reported old readings of bearing and mph. Zooming to a different level as Andye suggested has no affect on the problem. Hope these observations help. (using a dell x51v, win mobile 4 and a navibe bluetooth gps, bcn 2.5.9 is running off of a cf card)

Nathan I know you fing the answers
have a great day
Jerry

On version 2.6.2 I thought I would test the tracking delay issue on my iPaq hx2795 wm5. With tracking at 10 ft 10 sec BCN falls behind at speeds over 5-7 mph. With 30 ft 10 sec set, I could go 15 mph, but 20 mph would overwhelm. No View -> places or waypoints enabled, topo only, multi-resolution enabled but unused at the testing location.

So it is possible for me to adjust accordingly with only some loss of precision. I'm thinking of Mt. Biking or Enduro (moto) riding, for example.

I have never experienced tracking problems without trying like this, and generally use tracking only when hiking, which is pretty much all I've use BCN for. I have other in-car software. I also have a gps/logger, so tracks are exportable at different precisions that way.

The length of the track will have impact. A track of 5 miles may take close to 2 seconds to redraw at each reposition. It is also clear that a tracked 6-mile trail I have developed nearby slows the UI down considerably. With this track visible, whole map reposition/redraws can take more than five seconds, which can seem slow out in the woods. It may be due the complexity of the imported GPX, also. The tracks were created using logging on a gps logger, collecting, bridging multiple tracks, then importing.

no complaints, just feedback. When used naturally and with Log Options adjusted for the task it's not really a problem. Thanks for your efforts!

Andy