Funky GPS tracks on first MTB ride, what settings are you using that work best?

As the title states, I wore the watch on it's first mountain bike ride today and the GPS track appears horrid. I've been running with the watch for months (results not stellar but not anything like this). The track appears to only make square/90 degree turns and like it's recording a gps position once every 20 seconds and just drawing a line directly between the pings. My settings were as follows: GPS - only (not glonass), 1 second recording, 3d speed/distance OFF, lock on road OFF, map detail high, to pause off, auto climb off. I was not using any speed/cadence sensors, just the watch. Not too concerned with how accurate my speed was as I didn't really watch it much, mostly just want a good distance and decent gps track so it translates to Strava for segments well (which not surprisingly it did not).
Is anybody else using any different settings and having any better luck specifically for cycling? The area was relatively wooded with some (but not much) terrain. Not drastically different than where I have had success running in the past.
  • Ya I would say that GPS track looks pretty good. Hopefully my first track the other day was just an anomaly. I purchased the garmin speed sensor so when it comes in I look forward to seeing what it can do for the smoothness of my speed/distance/etc just like the footpod did for my running


    I did notice the distance was off a little compared to the other two devices - something like .2 of a mile. Though I noticed Strava changes the data too - differences with max speed etc, slightly different distance. I guess that is how they both interpret the data stream.

    I'd like a power meter but trying to justify the cost :-)

    Mick,