This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

I love the new chevrons on the route !!

Former Member
Former Member

Loving the chevrons on the route - was on a ride today (my first group ride after Covid lockdown for 2 years), and the leader was being creative with on the fly adjustments to the route. So we were in and out of the planned route with frequent detours. The location arrow showed me outside of the route but i could see ahead that when we eventually joined the route the direction i had to take. It was very comforting to see the chevrons in the route. The chevrons gave me a very good situational awareness of the map/route, the general direction we were heading.

Pre-Chevron era all u had was the magenta line.

I also didn't lose the original route even though we deviated away because i had disabled re-routing. And when i came back to the route it carried on like normal. 

Screen readibility was excellent also as i had the unit slightly facing down and it was a cloudless sunny day today (It'l suck when the sun is lower in the sky). And when the unit's navigation got a bit wonky i would attribute that to the data in the map data rather than the navigational functions. I wouldn't get easily frustrated and blame the 530 - it's the map. So if the map is mature you should have a decently reliable navigation capability in the 530.

  • Some people like them but there are many situations where they are useless, convey no additional information and just clutter the screen. In the absence of a switch to disable them I have gone back to V7.10 and don't see anything to tempt me to v8

      

  • Yeah, (only) for some courses I like them, but for the majority not. The user should be able to en-/disable this functionality. The developer/engineer should be able to add that during his breakfast session…

  • please Garmin, a different color for the coming chevrons (2 for example)... at crossroads it's sometimes impossible to know where to go

  • Former Member
    0 Former Member over 3 years ago in reply to Volker

    The reality of programming is that Removing and implementing functions / features are very time consuming and takes a lot of resources. It's gonna take more than a breakfast otherwise u risk breaking other things. Took Garmin so many years to finally implement the chevrons - probably inspired by the wahoos. And we still have the useless virtual partner (everyone's favourite pet hate).

  • Really? To add, that the next two chevrons from the current position shall be red is so time consuming and takes a lot of resources?

  • It might do.  It might not.  We don't know how easy it is as no-one outside of Garmin knows how difficult these things are to program.  Having the nearest two chevrons a different colour is harder than having them all one colour as the nearest two chevrons will keep changing as you move so it could well not be trivial.

    You also have to factor in the importance of such requests.  Resource will be allocated depending on what is on the list of things to change.  If there is something more important to work on (such as a bug causing issues) then a nice to have but doesn't really affect functionality such as colouring chevrons will be a low priority and may not happen.  Also, if not enough people ask for a feature it may not happen either.

  • Really? To add, that the next two chevrons from the current position shall be red is so time consuming and takes a lot of resources?

    It certainly would consume some time and some resources. Garmin would have to add it to 4 different devices. 

    It also doesn't add any extra information in many situations.

    It's also a feature that some people won't like. So, to satisfy everybody, Garmin would have to add another menu option for a device some people complain is too complicated to use. It's also another thing to have to support.

  • Former Member
    0 Former Member over 3 years ago in reply to Volker

    Don't mean to burst your bubble but yes - it generally requirtes a lot of resource to add/remove/modify a software - especially if it's more than Programming 101 in 1st year of college. Just like it takes a lot of resources to build a bridge, tall building or an aeroplane that flies.

    And don't u have anough indicators for directions to take ? u already have that nice direction big white arrow. Besides i think the 530 won't have the CPU or battery power to be constantly processing additional metrics that adds another clutter when you should be riding looking out for potholes and pretty girls go by. When you're bombing down the hill you'll be lucky to be able to see the largish white arrow for directions....those additional 2 cute red arrows won't be discernible among the map's clutter.

    I vote your 2 red arrows down - not that it's going to matter to Garmin what I think.

  • I vote your 2 red arrows down - not that it's going to matter to Garmin what I think.

    They are not my red arrows, I just like the suggested idea!Stuck out tongue winking eye