Yes, it is clearly doing antialiasing. But it's also adding shadows to the line objects. Here's a 400% enlargement of a detail from the maps I posted above.

You can see the dark outlines next to the stream in Mapsource. Those are not part of the custom type that I defined - mapsource is adding them.

I'll admit, it's a personal preference, but when I define a line to be one pixel wide (like the elevation contour in these examples), I really want a one pixel wide line and not a fuzzy 3 or 4 pixel wide line. Fullmetal Alchemist Brotherhood Pc Game. It gives the map a less crisp appearance, like it's a bit out of focus.

6.16.3 mapsource incomplete? Hi, I'm not sure if I need to start a new thread, if so sorry. I have Mapsourse 6.16.3 and the town I live in is about 1/2 there. 6.16.3 mapsource incomplete? Hi, I'm not sure if I need to start a new thread, if so sorry. I have Mapsourse 6.16.3 and the town I live in is about 1/2 there.

Basically, Garmin doesn't respect what the map author wants and imposes its own style. I guess it just 'is what it is'; I understand that Garmin makes these products to be used with their own maps and not third party maps.

But it does get frustrating. Custom types are supposed to give you complete control over appearance, but they no longer do.The thing is, their own maps also look bad. The desktop software developers and navigation device developers at Garmin seem to think they know better than the cartographers -- their own and third parties -- how maps should look.ken.

Is this behavior evident in older Mapsource versions? Many, myself included, have gone back to version 6.13.7 as our primary app. I've no experience with the custom mapping end of things, but I'm curious.The older versions of Mapsource did not do this cartoon rendering that ignores the line types the map authors provide. @OSTROFF01, In Mapsource, the new rendering style, along with other annoying display issues, begins when the new rendering engine was introduced in Mapsource 6.14.x. So 6.13.7 was the last version with rendering that is true to the map data (and remains installed on my system for use when map display speed and accuracy matters to me). The rendering on Garmin's Nuvi devices has been doing this nonsense for longer than the past year. I have a Nuvi 765T that has been available since at least early 2008 and it does it.

One side effect of this line 'heaviness' is that at some zoom levels topo maps are unusable on it. The countour lines are so heavy that they obscure all other details on the map. Lest anyone think this problem is limited to the small screens on personal navigation devices, I also have Garmin's Mobile PC which is a laptop navigation program that's sort of like stuffing a Nuvi into your laptop. Same user interface and same displays. Even on my desktop's 22' display at 1680x1050 pixels the contour lines at all zoom levels are too thick and at some zoom levels obscure everything else.ken. Fixed some map display issues (22s & 71s labels instead of highway names).