I was building some new ColorMaps using the .png format and all was going well. They loaded fine in GF Standalone 3.92 and worked great. I'm using these to "colorize" jpg images.
Then I began having an error code appear that blocked their loading, "Error Starting ColorMap "xxx" 55320." I'm running the ColorMaps from the ToolBar, not a script.
Sometimes these new ColorMaps will load and work without a problem, but more likely than not, the error code appears and they won't load. They do appear in the ColorMap list in the ToolBar.
The unpredictability has me stumped.
I'd be happy to attach three .png files to show you examples of ColorMaps that load everytime and some that are iffy, but I don't see a way to attach a file to a post on this forum. I'll try attaching the files as an link.
ColorMap "brown 2" always works.
ColorMap "brown 3" and "gray3" are iffy.
Any ideas based on the error code?
http://www.bnh.net/brown2.png
http://www.bnh.net/gray3.png
http://www.bnh.net/brown3.png
Error Code 55320 Color Map
Moderators: BTT, andy55, b.dwall, juxtiphi
The Color Map Problems Evolve
In reference to the above post, I am now able to use the new ColorMaps I created using the .png method. These two new ColorMaps would not load in the previous post, but now they do, and they work great.
I did not change the ColorMaps. These are the same ColorMaps that would not load yesterday. The 55320 Error code no longer appears. I simply let GF run for a very long time, and cycle through countless 55320 error codes indicating these ColorMaps would not load. All of a sudden, it was loading the new ColorMaps. I can't explain it. But since it started working, who cares.
However, a new anomaly appeared that may help explain the original problem, because since I can't explain the solution, the 55320 error code may appear again and prevent loading these ColorMaps.
I have documented this anomaly hoping it might explain this 55320 error code.
I'm using the Standalone version. When GForce first loads, it randomally selectes a ColorMap, which is displayed in the Tool Bar. Fine.
In the drop down menu for the ColorMaps in the Tool Bar, I had checked only the two new color maps, which I had labled as Gray4.png and Brown3.png.
After a short period of time, GForce will cycle away from the first randomly chosen ColorMap and load my two new ColorMaps. However, the use of the new ColorMaps will not be reflected in the ToolBar.
The Tool Bar will hold onto the name of the first ColorMap, even though it will eventally cycle and use the ColorMaps I have checked, i.e. Gray4 and Brown3.
I captured a Screen Print of the set up. As you can see, the ToolBar shows that DT - Ocean Club is being used as a ColorMap. However, the image clearly shows the use of my Gray4 Color Map.
If I wait until the next ColorMap cycle, which is pre-checked to be Brown3, the name in the Tool Bar will not change. However, GForce will actually use the Brown3 ColorMap. In fact, the Tool Bar will show no change in the selection of the ColorMap, even though the ColorMaps are obviously changing.
So somehow, my use of the new .png ColorMaps, which wouldn't even load yesterday, are now loading fine, but their use is not being reflected in the Tool Bar.
I hope this helps in finding an answer.
I did not change the ColorMaps. These are the same ColorMaps that would not load yesterday. The 55320 Error code no longer appears. I simply let GF run for a very long time, and cycle through countless 55320 error codes indicating these ColorMaps would not load. All of a sudden, it was loading the new ColorMaps. I can't explain it. But since it started working, who cares.
However, a new anomaly appeared that may help explain the original problem, because since I can't explain the solution, the 55320 error code may appear again and prevent loading these ColorMaps.
I have documented this anomaly hoping it might explain this 55320 error code.
I'm using the Standalone version. When GForce first loads, it randomally selectes a ColorMap, which is displayed in the Tool Bar. Fine.
In the drop down menu for the ColorMaps in the Tool Bar, I had checked only the two new color maps, which I had labled as Gray4.png and Brown3.png.
After a short period of time, GForce will cycle away from the first randomly chosen ColorMap and load my two new ColorMaps. However, the use of the new ColorMaps will not be reflected in the ToolBar.
The Tool Bar will hold onto the name of the first ColorMap, even though it will eventally cycle and use the ColorMaps I have checked, i.e. Gray4 and Brown3.
I captured a Screen Print of the set up. As you can see, the ToolBar shows that DT - Ocean Club is being used as a ColorMap. However, the image clearly shows the use of my Gray4 Color Map.
If I wait until the next ColorMap cycle, which is pre-checked to be Brown3, the name in the Tool Bar will not change. However, GForce will actually use the Brown3 ColorMap. In fact, the Tool Bar will show no change in the selection of the ColorMap, even though the ColorMaps are obviously changing.
So somehow, my use of the new .png ColorMaps, which wouldn't even load yesterday, are now loading fine, but their use is not being reflected in the Tool Bar.
I hope this helps in finding an answer.