Constant crashes (W10, High DPI monitor)

Besides the fact that garmin basecamp really doesn't play nice with 4K / High DPI monitors... it also crashes as soon as I start calculating a route.

Is there any chance the promised update will solve these issues?
  • While a possible software update has been reported on this forum, it is not entirely clear to me that it will actually occur. In any case, it is a good idea to report your issues to Garmin support - perhaps SUSSAMB can provide a link?

    In the past, BaseCamp has not correctly installed on some computers. This sometimes results in a seemingly functioning program, but it will crash or hang. It might be worthwhile to backup your data, download BaseCamp again, do an uninstall and install it anew.

    With regards to calculating a route causing crashes, what are your settings? Too many restrictions can cause the calculation to fail or appear to hang.

    Anyone out there using a 4k monitor having similar issues?
  • I am using a stock install with the openmtbmap maps for Europe installed.
  • Regarding the installation: Whether it is a server change at Garmin or something else, a seemingly correct download and install will be produce an installation that will open but may have issues performing certain tasks. This is hard to diagnose and the easiest thing to do is download again and reinstall the software.

    The routing issues you see may be due to the use of non-Garmin maps. Some non-Garmin maps and Garmin maps have different classifications for different road types. The avoidance of certain road types for an these non-Garmin maps will cause routing to fail - at least it has in the past. I don't know which one(s) cause the problem. Try removing all Road Type Avoidances (Edit>Options>Activity Profile>Routing tab) and see if Routing works. If it does, add the Avoidances back one at a time until you find the problem then be sure to leave problem types unchecked.

    If you can't get Routing to work at all, I would do the download and reinstall.
  • There is no reinstalling the Garmin connect website and trendline routing that is visible there. (More specific: there are gaps in the garmin maps on perfectly fine trails when using the mountainbike routing on the website. Just 'missing' sections, a few meters, just enough to seriously screw up routing)
  • I'm afraid I don't understand your last post.

    My understanding is that you are using an openmtbmap in BaseCamp and are having trouble creating routes. The openmtbmap maps are not Garmin products and consequently the Activity Profile options may need to be changed in order for routing to work. Please look at https://openmtbmap.org/about-2/autorouting/.

    Did you open the BaseCamp Options (under the Edit Menu or ctrl-o), select Activity Profile on the left side, click on the Routing Tab and remove all of the checks for the Road Type Avoidances? Does routing still crash BaseCamp?

    To reinstall, download BaseCamp from http://www8.garmin.com/support/download_details.jsp?id=4435. Uninstall BaseCamp then run the download.
  • The reason I don't understand your previous post is that I do not see where Garmin Connect is involved. I have no experience with Garmin Connect, but if your issue is uploading a Route created using the openmtbmap to Garmin Connect it may be because the site tries to validate the route against Garmin maps. I would try to converting the Route to a Track and uploading the Track.
  • I'm sorry, my mistake!

    There are two seperate issues.

    The first is that Garmin Basecamp crashes. It looks horrible on a 4K monitor (it REALLY needs an update). It crashes when creating a route using openMTBmaps. But since the edge 1030 also crashes using the openmtb maps, it could be just the maps.

    The second is that garmin connect routing (the new trendline routing available on the 1030) also has a lot of errors and missing trails. I have two seperate threads on these topics, I mixed them up. Again, sorry for the confusion.
  • No problem.

    Let?s concentrate on the BaseCamp issues. You can?t do Auto-routing with the Global Map, but you can see how the application behaves with a Garmin map on a 4k screen. Without doing any routing, how does the application behave when doing simple operations like panning and zooming? Would you judge the map okay in appearance?

    Sluggish behavior can be the result of setting the map Detail Level too high. Check to see that your Detail Level setting is no higher than Medium. You may have to open that toolbar via the View Menu>Toolbars>Detail Level.

    Openmtbmap.org indicates that different layouts are available during installation. Did you choose the proper one? From their site (https://openmtbmap.org/download/odbl/):

    ?On installation you can choose the layout of the maps. Traditional layout is for Qlandkarte GT, Mapsource and Basecamp and offers a good layout and design for big screens. On the GPS thin, classic and wide or easy or hiking offer high contrast for best orientation while riding your bike or hiking.

    In order to change the layout - simply run openmtbmap_country_change_layout.exe (this is also linked in your Start --> Programs Folder for each map). This also enables you to quickly change the layout before sending maps to your GPS device, and then quickly change it back for better planning on your desktop.?

    Issues with routing when using non-Garmin products can be the result of road/trail classification in these maps. Have you removed all avoidances and tried routing to see if this is the problem? Type ctrl-o to open the Options window, click on Activity Profile along the left side of the window. Make sure the Profile you are using is displayed in the dropdown menu. Click on the Routing tab. Uncheck the Avoidances by clicking on any box that has a check mark. Now try creating a Route ? make sure you have changed the map back to the openmtbmap. Does BaseCamp still crash?

    If the Global map behaves poorly or is not satisfactory in appearance, report an issue with 4k monitors to Garmin Support. If you are still having issues with routing crashing after removing avoidances, you might be better off contacting openmtbmap.org. If they have a solution it would be helpful to others if you could post it here.