@ivo
I might start to be repetitive, but:

• you decided to destroy perfectly working system just because of what? I perfectly understand devs ego to do "state of the art" things just because they can, but it's kindergarden behaviour. Unfortunately this new UI is the state of the wrong art. Did you do any research beforehand? Did you show your brilliant idea to a single paying user and get anything close to "it's exactly what I dream about!"?
• you are not the first company (and for sure not biggest) who shoot itself in the foot for no reason. But why? why would you do it? Could you control your devs ego a bit?
• it's your problem that plugins are not converted to new UI. On what basis did you decide that 2 months is enough time for plugin maintainers? Do you realize that one or other pluging might be the major reason for user to pay for windy? You could easily postpone this new UI till majority of plugings will be converted... And believe me no one will be missing your new UI even if it will be posponed for 20 years..

What you can (easily) do now:

• revert back to prev version for people who ask for it - all of us?
• make windy-2 and satisfy your devs ego there. You may make separate subscription for it, experiment to any level of madness/excellence there. People will switch to new in no time when new will be at least as useful as old one.

PS.
your Sounding implementation is not as useful as one from plugin. Just have a look side by side and spot the diff.

@Suty
just make yourself windy-2 and experiment there.
When you will see how many people are willing to pay for it... A/B testing - have you heard about it?

I.e. from your answer I can see you have no idea why people use (or rather did use) windy, what they liked and why are willing to pay for it.

why would one change the UI before make sure all (or at least most) OLD features are unaffected and available?
I prefer working features vs fancy looking useless UI.

@Suty

1. select wind (at 2000m in this case, but I think it's irrelevant) and see normal wind info. pic-1
2. select sounding plugin
3. just do mouse click at any point. Now I have second point and sounding info for it. Wind marker stays where it was prio to plugin activation. pic-2

In prev UI the wind marker would be placed at mouse click position as well, but not anymore.
I have chrome Version 124.0.6367.60 (Official Build) (64-bit) on Linux

4. if I leave plugin the mouse click starts to move wind marker again.

pic-1

pic-2

@Suty
Well - nope, none of you suggestions are helpful

what I need is to see wind from diff models at some point at some height (2d slice) in area of lets say 20x20km (not exact number). Also I need to see sounding for that point (i.e. vertical slice). I was able to do so in one click before. Now I cannot do it at all - unless I zoom in and out all the time.

The problems:

• I don't need detailed forecast as it has info I have no interest and it consumes my screen and it changes the view (new panel with detailed forecast pops up..)
• if I select detailed forecast I am loosing the view of plugin. It was annoying even in prev UI by the way
• now the sounding point/picker and wind point/picker on the map are two separate points if I just do mouse click. which is also the bug. see pic

As I said in height selection for wind bug - you could just let me drag and drop model selection widget and use it. Your map style selection widget you can sell to someone else :). And all will be happy.

pic

@Suty
I see it was fixed by moving height widget outside of menu
i.e. it's back to be useful. Thank you very much.

Also idea to allow user to drag and drop things is one in right direction. If you would extend it one step further allowing users to select all widgets they need you might solve 95% of problems you created with new UI.

I.e. in case I would be able to place model selection widget where I need it and clear it displaying from your "logic" I would immediately get working (for me) env.

@Suty
Very simple use case
"user want to see what diff models prediction are for given spot"

With current "logic" as soon as I zoom to the spot of interest I don't have ability to do so. And as you see from pics it's happening very early in zoom process.

Another lost of functionality with UI update...
And again - why do you think you know better than me what I really need?

1. pic-1: user in wind mode and can select any height
2. user activate plugin
3. pic-2: user switch to wind mode and now get wing at surface level without possibility to change it as height widget is not available anymore

Should I say there was no such problem with disappearing height widget in prev UI?

pic-1

pic-2

1. pic-1 one can select model at some zoom level
2. pic-2 zoom a bit closer and there is no more model selection

What should user do now to be able to select model at any zoom? Should I say it did work conveniently in prev UI?

Should I say that it looks like this change from model selection widget to unrelated map mode selection widget is made on purpose.. but not clear which purpose.

pic-1

pic-2

@ivo
I might start to be repetitive, but:

• you decided to destroy perfectly working system just because of what? I perfectly understand devs ego to do "state of the art" things just because they can, but it's kindergarden behaviour. Unfortunately this new UI is the state of the wrong art. Did you do any research beforehand? Did you show your brilliant idea to a single paying user and get anything close to "it's exactly what I dream about!"?
• you are not the first company (and for sure not biggest) who shoot itself in the foot for no reason. But why? why would you do it? Could you control your devs ego a bit?
• it's your problem that plugins are not converted to new UI. On what basis did you decide that 2 months is enough time for plugin maintainers? Do you realize that one or other pluging might be the major reason for user to pay for windy? You could easily postpone this new UI till majority of plugings will be converted... And believe me no one will be missing your new UI even if it will be posponed for 20 years..

What you can (easily) do now:

• revert back to prev version for people who ask for it - all of us?
• make windy-2 and satisfy your devs ego there. You may make separate subscription for it, experiment to any level of madness/excellence there. People will switch to new in no time when new will be at least as useful as old one.

PS.
your Sounding implementation is not as useful as one from plugin. Just have a look side by side and spot the diff.

@Suty
just make yourself windy-2 and experiment there.
When you will see how many people are willing to pay for it... A/B testing - have you heard about it?

I.e. from your answer I can see you have no idea why people use (or rather did use) windy, what they liked and why are willing to pay for it.

why would one change the UI before make sure all (or at least most) OLD features are unaffected and available?
I prefer working features vs fancy looking useless UI.