I got a new 665. I've uploaded the same camera poi file I have been using on my 2730 and 2820 for years with no problems. I get a warning at the camera locations, I even get the MP3 warning. What I've seem to have lost was the little icon that shows up at the intersection on the gps screen.
Garmin of course said I should use their paid poi file that you can only use on one device.
Anyone have an answer for this?
Is this an Zumo ? If so try ikon in 16 or 24bit insted of 8bit.
Yep on my Zumo. I'll convert it and see what happens.
OK, I've tried the following all with no luck.
Converted the camera icon to 24bit (.bmp) The .mp3 file works just fine.
Downloaded Garmin's trial camera database and their camera icon shows up fine.
Checked spelling of icon.
It seems that none of the icons I have associated with POI files show up. My waypoint icons show up just fine. But these are the ones from Garmin in their mapping software.
I looked for icons here, but can't seem to find the file. Can someone point me in that direction to?
Now this isn't something I can't live with, but I'd sure would like to make it work.
Did you try 16 bit? Some zumo use 24bit and some 16 bit.
I am just random thinking of things:
POI Loader says:
Loading Custom Bitmaps
You can include images in Custom POI files you create using MapSource.
POI Loader can also associate customized bitmaps (.bmp) with the points in a data file if the .bmp has the same file name as the data file. For example, a customized bitmap named "Speed_30.bmp" would be associated with all the points in the file named "Speed_30.csv" or "Speed_30.gpx." Bitmaps must be saved in the same directory as the associated data files.
You can also associate .bmp images with all the data files in a subcategory. For example, a customized bitmap called "restaurants.bmp" would be associated with all the points in a "Restaurants" subcategory. Custom bitmaps associated with individual file names take precedence over custom bitmaps associated with subcategories.
Your Garmin GPS device may have image size requirements. Most compatible Garmin products work well with icons that are 24x24 pixels or smaller. Bitmaps that do not meet those requirements may appear distorted when viewed on the unit's screen.
In addition to the above, I assume you have it named EXACTLY the same character string as the POI file except for the ending 4 characters ("dot" plus extension) since you say that the .mp3s are working, but double check and make sure you do not have a double extension on it.
Try zooming in to 300 feet and see what happens while driving.
Next tings I've tried.
I should say, my waypoint icons show up just find. It's only the POI ones I'm having trouble with.
Contacted Garmin, NO HELP. They suggested I down load their camera file, which I did. The free trial. THEIR camera Icon shows up just fine.
I then downloaded all new icons from our database here. They still don't show.
I double check that they were all named properly.
I get my custom .mp3 warning, the the intersection name shows. It's just the stupid Icon.
I'm using the 3D maps Next time I'm out I'm going to try their 2D and see what happens.
As I said before: Did you try 16 bit? Some zumo use 24bit and some 16 bit.
yep, converted them, and it didn't help
Ok. I was thinking of something. Maby this new Zumo use 8bit color like nuvis.
Many of the Icons from Poi Factory are in 24-bit color and not 8-bit. Older Nuvi could use 24bit also so It is not before now this problem comes up, as the newer units only accept 8-bit.
So I think you should check your origial icons and see if they realy where 8 bit from the start.
Maby it is so simple.
Well I think I've finally figured it out. I put the gps in 2D mode and the icons show up just fine.
I think, it's the way the 3D mode displays along with all the screen movement. The icons are there. When I stopped and pulled over and switched from 2d to 3d, and when there was no movement, I could see them. As soon as I was moving they could come and go, mostly go.
I converted them to 16bit. I don't know if 8bit works or not because the are not in 16bit.
terms | privacy | contactCopyright © 2006-2021