snackbauer
Well-known member
Finally fixed an annoyance:
◦Changed displayed route times to take layovers into account
◦Changed displayed route times to take layovers into account
Seems Basecamp may well be encouraging flower sniffing to the 10th power!Ok, maybe they didn't quite fix the problem. Or is it just me.
It appears as though in adding layover time to total route time, they've included the time between current time and route planned start time as layover time.
So, if I create a route today to ride to Stagecoach on December 30 (doubt I will attend), Basecamp adds 600 some hours to the total time.
I don't think that is useful.
Maybe something is buggy in this version. I have never had problems planning rallies accurately with a start time/date set for a future date.I was playing around with the date on my pc. If I set it to the day my route starts, everything looks fine.It seems Basecamp doesn't like advance planning.
No, I haven't looked at that, but I will. I'd also like to be able to assign a default layover time for each category ... Gas stops, bonus stops, etc. That would make planning quicker and a bit easier.Hoping for a fix by Spring. Moonshine SS1K will be happening before you know it.
Actually an easy workaround, just set the start time to last year.
Twigg, when you do Rallies, do you organize your waypoints using Categories in Basecamp?
Enter your email address to join: