I think if it's the same thing in mapsource (can't search by numbers) it's most likely the map since that is the map I'm using on all my units...somehow street numbers were omitted during the unlock in the process/method which may of differed by theirs methods/unlock. I doubt it's the units. I have several models that I tried with RG 1.24 (255w, 285wt, 3790t, 2360LT) and all those do not display the street number and just point to the default location on the street. I dont think they are faulty and the US/EU street numbers show up fine on their respective maps.
Just want to confirm with vortex, that 23 adb and 175 or any higher number show different positions on the map or it's simply just keeping 23 on the display but still pointing to default/same location on street regardless of the street number inputted. If you can also do the same in Mapsource, if you enter 2 different numbers, same street. If it indeed does show 2 different locations when you input 2 different numbers on the same street then pretty sure it was our method of unlocking our maps that produce this problem.
Have not modified the firmware on any of my units they are all stock US firmware, some have been updated to latest firmware by garmin update. Again I don't think this matters much if the same img from mapsource was transferred on the garmin units, if you can't search numbers in the mapsource version should be the same on the unit, hence it's probably the way we unlocked our maps that caused this.
(my method was using the unlocker to unlock mapsource rg... then send map from mapsource to garmin unit, hence using exact same map as the one in my mapsource). I did not use the gmapsupp.img file unlocked/locked posted in an archive.
Bookmarks