How to show custom Symbols in Oregon 450?

I have observed the same with my GPSMAP 62s and BaseCamp. There appears to be an incompatibility with naming convention between BC and the GPS.

As you know, custom symbols on your computer for BC need to be named 001.bmp, 002.bmp, etc. On my GPSMAP 62s, this naming is not recognized. If I rename the symbol file on the GPS to something alpha (001.bmp = RRxing.bmp), the symbol is now recognized in the GPS. Of course, it is now not recognized by BaseCamp!

If I assign a custom symbol (001.bmp) in BaseCamp and send the waypoint to the GPS it does not display as you noted. If I assign a custom symbol (RRxing.bmp) in the GPS and send it to BaseCamp, it does not display.

I have also noted some incompatibility between BaseCamps' standard symbols and what the GPS will recognize.

If I assign a custom symbol (RRxing.bmp) in the GPS and send it to BaseCamp, it does not display.
.

Your observations seem to be reasonable and I tried to repeat your tests, but I can't find in the Oregon the possibility to assign a custom defined symbol. I find only the tables with the normal waypoints.

Your observations seem to be reasonable and I tried to repeat your tests, but I can't find in the Oregon the possibility to assign a custom defined symbol. I find only the tables with the normal waypoints.

I am not familiar with the file/folder structure on the Oregon. On the GPSMAP 62s, custom symbols reside in the folder \Garmin\CustomSymbols. In the 62s when a waypoint is selected and displayed, the symbol can be edited as can the name, location, note, etc. When custom symbols are present, they will appear as a "category" along with the standard installed symbols.

In my case, if the custom symbols are named with the 001.bmp format as required by BaseCamp in the folder My Garmin\Custom Waypoint Symbols, they will NOT display on the 62s in that naming format. If renamed with letters (as in a word), they will display on the 62s (when in the GPS Custom Symbol folder).

I made some success, but not sufficient. The problem was: i used until now *.bmp files with 8 bit color, Garmin requires *.bmp files with 24 bit color.
I am able now to have and to show the same symbols with the same filenames in Garmin as well as in basecamp. I transfered this files with copy and paste, so that they are really identical.
But the problem still remaining is: If I asign such a symbol in my handheld and look to it afterwards in Basecamp, it is shown as empty . And vice versa: If I asign in Basecamp a symbol to a waypoint stored in Garmin, and look to this afterwards on my handheld, it is shown also as empty. Another observation: if I store the same symbols in my handheld in the Garmin itself as well as in the microcard, the symbols are shown twice on the respective category of my handheld.
It is obvious, that the three stored symbols
k:Garmin\Customsymbols\000.bmp
L:Garmin\Customsymbols\000.bmp
..documents\my Garmin\userdefined waypointsymbols\000.bmp
(K is the handheld, L is the microcard in it)
are considered to be three different waypoints.
So the task for the development people remains to extract the filename only from the symbol path and name befor comparision.

http://garminoregon.wikispaces.com/Custom+Symbols

You will need to name the symbols appropriately.

'001.bmp' on the PC needs to change to 'Custom 1.bmp' on the device. Then BaseCamp and the Oregon will sync correctly.

I just verified it, it works on my Oregon 450 with BaseCamp 3.2.2.

Thanks Falagar. For me, the problem is solved now.
But a remark to others who may read this: the naming convention is very stringend: custom 07.bmp is not the same as custom 7.bmp. Obviously the programmers compare the "number" as alphatext and not as number.

No doubt, this is confusing for the user.

We were planning to implement a better approach for custom waypoint symbols, we just haven't gotten around to it just yet.

Thanks for the link to the "Wiki" for the Oregon. Changing the names to Custom 1.bmp, etc. did the trick.

Is there a "fix" in the works so BaseCamp and the GPS both use the same filename configuration? Kind of a waste having to have one file with two different names.

Also observed, the use of a leading zero (01) is not acceptable; the file must be named "Custom 1" not "Custom 01". The problem with this is, in Windows, file name sorting will be affected...Custom 2 will appear between Custom 19 and Custom 20.