bug with basecamp 3.2.1 and Topo Suisse V2

Does this happen when you're viewing the map in 3D mode, too?

I couldn't say for sure, I nearly never use 3D. It doesn't happen every time in 2D either, I couldn't detect a pattern, it's not when I have a device connected and it's not related to the last map I used which is generally always the Suisse Topo.

Although, I just started BC and it was in 3D with Suisse Topo showing the country view, clicking on a folder for "display on map" the problem did occur.

But, I exited and restarted, BC started in 2D but still started at the country level. This is new, BC didn't do this with the previous release. And again, displaying a folder on the map gives the same issue.

This time, I corrected it by switching to Suisse Topo V1 & then back to V2. Now after a restart the behaviour is what I expect, I'm seeing the zoom level I was on before and the waymarks are displayed correctly.

This is still a problem. Waypoints are leaping around depending on the zoom level. It makes it difficult, nearly impossible, to do any route planning.

Is there any intention to address this?

Next time it happens, try clicking on the North-Up arrow in the upper left corner of the map. Could be that your map was slightly rotated when you closed it last and isn't indexing properly when it loads.

Cheers,

Dirtbyk,
I believe that just-off-north rotation rendering bug is fixed as of 3.2.2, partially because we just snap to north up for anything within ~five degrees.

SnowSlider,
Is there a part of this issue that switching your map product back and forth doesn't fix? There's a similar issue we investigated recently here that can be worked around with that, but if other parts of our application's scale/routing aren't "fixed" by that then this may be a different issue from what we've seen.

The gist of the problem we've observed is that you start off in a weird position/zoom and the map's scale is off from that point on, affecting the rendering of map labels and waypoints. It sounds very similar to what you've got happening, but if there's a separate issue we should be looking into I'd like to know.

Dirtbyk,
I believe that just-off-north rotation rendering bug is fixed as of 3.2.2, partially because we just snap to north up for anything within ~five degrees.

I realize you do that at startup but at any time one can inadvertantly slightly rotate the map and cause the following condition.



May not be the case for SNOWSLIDER's issue though.

Cheers,

If you take a look at the images above you'll see we're talking about a major displacement not just a minor one caused by moving orientation.

Thanks to both DRTBYK & PAXTER1 but you're missing the point . I know how to "fix" the problem, I don't need any more ways to fix it :)

The point you're missing is that you first need to know there's a problem.

So, this morning I had to go and do something on a local mountain. For various reasons I wanted to go to points well off the paths & away from landmarks. I could have micro naved to them with a compass but I opened Basecamp, set up three waypoints and transferred them to the GPS.

As soon as I switched the GPS on the hill I realised the waypoints were rubbish so I ended up using a map and compass anyway.

Sure enough, I got back, opened Basecamp and my three waypoints leapt from where I actually put them to where Basecamp thought I had, or, if you prefer, to where Basecamp had put them from where I had put them.

So, sorry, not good enough by a long, long way, it's broken.

Snowslider:

I'm just trying to make sure that the bug you're reporting matches one we've already looked into here. Do you have any consistent ways to reproduce this or is it just "most of the time" at startup? Part of the difficulty we've had in fixing this is the apparent unreliability of its occurrence. If it happens every time for you, perhaps you could send your ~/Library/Preferences/com.garmin.BaseCamp.plist to [email][email protected][/email]?