Map Colour Shades Bug

W8-HSR

Hi,

If you delete all the shades/colours in any spectrum, it renders the map colours useless. It’s then not possible to add any, start again or reset.

It is possible to fix this urgently or reset my account to defaults?

Thanks
Henry

Korina

@w8-hsr Hello, you can customise colors for each layer at https://www.windy.com/colors?iconEu,45.599,16.540,4. Of course, if you delete all the color lines, you will be left with unusable map. You can also load defaults.

idefix37

@korina
@W8-HSR

I’ve tried to replicate this bug on Chrome on my iPad. It’s right that if all color lines in setting panel are delete, or color code in [view code], everything is blocked. I needed to re-install Chrome on my tablet. On desktop, I guess it is necessary to clean the cache.

Korina

@idefix37 @W8-HSR Hello, I was able to replicate this issue, our team will look into this.

W8-HSR

Any news on this? Is there any way you are able to just reset my account to defaults while the issue is fixed?

Sorry, I assumed I would just be able to start from scratch after deleting all colour settings… didn’t think it would become unusable afterwards .

idefix37

@w8-hsr

For Wind, try to click [view code] below color scale setting. Delete all lines of code in the small pop up window, then paste in it this code which is the standard code for wind:
[[0,[98,113,183,255]],
[1,[57,97,159,255]],
[3,[74,148,169,255]],
[5,[77,141,123,255]],
[7,[83,165,83,255]],
[9,[53,159,53,255]],
[11,[167,157,81,255]],
[13,[159,127,58,255]],
[15,[161,108,92,255]],
[17,[129,58,78,255]],
[19,[175,80,136,255]],
[21,[117,74,147,255]],
[24,[109,97,163,255]],
[27,[68,105,141,255]],
[29,[92,144,152,255]],
[36,[125,68,165,255]],
[46,[231,215,215,256]],
[51,[219,212,135,256]],
[77,[205,202,112,256]],
[104,[128,128,128,255]]]

Click [Import]
That should solve the issue at least for this layer.

Korina

@w8-hsr @idefix37 Hello, we apologise for the inconvenience, we plan to fix this issue during this week.

Korina

@w8-hsr @idefix37 Hi, in the end we were able to fix this issue today and the bug-free version is in production already.