19.34 has ruined the map experience for me

So I've installed firmware 19.34 on my old Fenix 7X SS and immediately noticed that the map experience has been ruined.

1) Panning the map with touch is borderline impossible now because this darn menu docker keeps popping up every time I swipe from right to left. Has anyone at Garmin actually tried using this new UI when on a trail? 99% of the time, all I need is a maximally easy and efficient way to zoom and pan. It is OK to make it a bit harder to open the menu because that is very infrequently needed. Making that easily available with a touch swipe is a wrong choice because now that stands in a way of what we need 99% of the time!

2) I had a carefully chosen custom map theme to maximize the contrast - that is because the contrast of the original 7X SS is very poor due to the combination of sapphire and solar layer. I made the custom theme by editing the high contrast theme and then further maximizing the use of black and white. What I see now is there is no longer a way to customize map theme and that the high contrast choice is simply gone. There is no such choice in the map layers. I am stuck with the map having a lot of unnecessary visual noice that isn't useful at all when trail running. This proves yet again that Fenix is not a watch for high paced endurance sports and that trail running is never even considered when design choices are made. What special about trail running is that the maps have to be maximally easy to glance at when running fast, when the vision may be a bit blurry and when lighting conditions may be suboptimal when running in a forest on an overcast day. So the map has to be very simple with bold lines and high contrast. What existed before was sub-optimal and what we have now is even worse!

3) Map seems to be even more laggy than before. That's probably because before I had a reduced level of details and a simpler high contrast theme. But now I can no longer select that, so rendering is more complex. Furthermore, I suppose the battery use will be higher because there is more content to redraw.

Seeing this has reinforced my decision to skip Fenix 8 and Enduro 3. Garmin seems to have wrong priorities for me as a user. I don't see trail ultrarunning experience being a priority and influencing the UX design. That is despite Garmin pretending like they do care about trail ultrarunning by choosing the start of UTMB in Chamonix to launch Fenix 8 and Enduro 3. I just don't see these watches being optimized in any way for that! 

  • Ich gebe Ihnen vollkommen Recht,  das ist bei mir leider genauso. 

    Habe aus Verzweiflung die OutdoorMaps+ abonniert, aber die wird noxhnkxht einmal angezeigt. 

    Wirklich traurig, in Verbindung mir den Abstürzen alle 1,5h ist die Uhr für mich gerade wertlos. Und das Dümmste, ich möchte am 12.12. Auf die Kanaren zu bilen.aber die vorbereiten Ttacks sind jetzt ebenfalls wertlos.

    Ich denke wirklich darüber nach,  all meine Garmin Geräte anzustoßen und auf einen anderen Hersteller zu setzen.  

  • I have already switched to Suunto Race S as my primary device but am still deciding what to buy next. Race S doesn't have the battery for mountain 100 milers, but it is almost perfect as a daily driver and training watch. And Suunto's map implementation is beautiful - crisp and responsive, and so much better for my needs than Garmin's laggy and difficult to read map.

    I am still considering Enduro 3, but based on what I see and read in the forums I am ready to give up on Garmin. As I said, Garmin priorities seem to be misaligned with mine. Meanwhile, the bug with the Up Ahead feature not working correctly when doing 100k+ races that I reported at the end of April 2024 still hasn't been fixed. That is another feature important for  ultrarunning that has been ruined.

  • Completely agree with your post. Please garmin, read that.

    I was also thinking on buying an enduro 3. But I think I would reconsider it if garmin keeps doing the same with his updates policy

  • That menu docker (arrow up) is making me so mad...

  • Thanks for warning me.

    When I switched back from  a mapless Enduro to a mapped Enduro 2 after lacking that feature of my former Fenix 6X, my first routine was to check how my self made theme works on Enduro 2 with my own typped map .img. I was pleased with it, just a tiny change it  the .typ file was needed to finetune it, because sapphire of Enduro 2 has a different effect on colouring that gorilla glass of Fenix 6X.

    I am stubbornly insisting on this extra development of mine.  So  even if I wish to get rid of the annoying bugs like Sleep mode reactivation of a manual end, I am defending my watch from any fw releases without map themes.

    It was already a shame that I had to modify one  of the native themes and was not allowed to add a new one like I did with F6X.

    Why does it hurt Garmin if some watch owners are happy with therir extra inventions? Are the fw coded so that they are vulnerable in terms of stability just adding a theme file which contains the very same field names as the factory ones, only the values are different?

  • Are the fw coded so that they are vulnerable in terms of stability just adding a theme file which contains the very same field names as the factory ones, only the values are different?

    I don't think it's that in general,  more that some coders might not be as good as others and might cause problems. And we all know that there are enough problems with the watches for some as it is without giving more ammunition.

  • Did you mean keeping the feature of themes is a sort of “giving more ammunition”?

    If so then any  present feature is in danger, because any of  these “some coders” can easily put a finger on a feature classifying it as an unholy work of the Devil. :-)