Even more confusing it gets now, when Metoblue AI is the default model for the local mode, but not being available for the map. It is possible that this way you will get more tickets here. At least you could pop-up a warning. Or decouple the two views, the map and the local weather forecast, why you impose them to be the same ("if its available")?

But I am sure that Windy will find a more logical and ergonomic way to allow people to do what they want to do. For example, by letting Premiums to set every single parameter to their liking in a central, single dialog. Vivaldi browser has succeeded in this. A daunting task will be to find the default values for the masses, of course...

It remains for Windy to decide is this a functionality they want to provide (to peek into the local weather from the map with a chosen local model, without changing the map model).

Even if not, the current behaviour is a bug.

Asking the user to reload the page would not make it less a bug, I am afraid.

Please do not mix the expected behaviour with the third test - even if it contains the blinding Metoblue AI selection : this is the same problem, only that the bug you acknowledged in https://community.windy.com/post/231081 takes in the "Meteoblue AI" to baffle the minds in this already confusing behaviour.

Why the parameter management is prone to these bugs: because now you have decided to mix settings, stored in the user's profile, to be managed both in the user's profile (correct) and in the local weather widget (not good). That's for my 2¢.

Do I understand the issue?

However, if I update the whole app in browser and open the detail once again, it behaves normally then.

On a personal note, I think Windy is getting difficult to you use by unnecessary dispersion of user parameters distributed here and there with the glue between them missing.

But since I am not the stakeholder here, only a tester, and because that detail has nothing do with the original question, let's wait if @pgilbrea confirms that the application works as expected.

Test on Vivaldi browser,
Windy version: 51.1.0 (d0b690a99)
built: 2026-08-06T07:59:23.893Z

FIRST TEST

SECOND TEST

THIRD TEST

STEP 1: RELOAD THE PAGE

(Metoblue.AI is the default if no forced model in local view selected)

Now, the map selection has remain the same, probably because Meteoblue.AI is not available for the region where GFS was.

I do not have no position about the above being a bug, feature, or does it make perfectly sense. Just wanted to test it. Hope it helps to understand the actual behaviour for further discussion, if any.

In my profile user settings, I have the 'startup layer and location' set to 'use last *'.

I'm not sure exactly what's happening on the backend, but my take is that the model variable doesn't seem to be properly passed from the map to the point forecast when RE-instancing a point forecast. It may be keeping the last point forecast instance active?

What do you have set here?

If I click the map for a point forecast when viewing the map using a model that is different from my default (in 'settings for point fcst' menu), it always goes back to the default model. This works as I expect.

I purposefully turned that feature off in the settings hoping that it would keep the map forecast and point forecast model consistent.

Hi @pgilbrea, may I ask you how do you turn off that "feature" in the settings - User Settings in the profile, or in 'settings for point fcst' menu? I am interested in testing it but do not know how to do it. Thank you.

An example: I view a point forecast with the GFS, then close the point forecast and change model (in map mode) to view the ECMWF map. If I click a location to pull another point forecast, it goes back to a GFS point forecast instead of the expected ECMWF.