And another issue with resetting. When you click somewhere on the map it resets the position of the map so that the clicked location is in the centre. This is a problem if you click near the edge of the areas of a particular model, because the map recentres on the point, then the model switches to another model because it considers the view to be outside the range of what is applicable for that model.

For example, choose ICON-D2, sounding, then click on Gloucester in the UK. The map scrolls so that Gloucester is in the centre of the non-sounding part of the map, then the model switches to ICON-EU. (I think it is using the centre of the whole screen - including the portion of the map that is hidden by the sounding pop-up - to determine whether the model can be used. So you have two inconsistent definitions of centre.)

One more vote for scrolling through the timeline on mobile.

Also can we have an option for the green dotted line for thermals to be drawn automatically based on the actual surface temperature and surface dew point? This should really be the default. It is rare to want to know what a parcel of air would do if released into the atmosphere with some random temperature and random humidity.

Since today, when viewing windy.com on my laptop with Firefox (Ubuntu 21.10), the mobile version of the page is being shown. The mobile version doesn't work on desktop since it requires touch interactions which the mouse seems not to trigger. This is despite deleting all cookies and clearing the cache. Same on private window. Same logged out. On Chrome, the desktop version of the page is correctly shown.

Have you recently changed a version-detection string regex perhaps?

@Ondřej-Šutera sorry I missed your reply. I have updated my notifications settings to email me so I shouldn't happen again.

I could provided another screenshot but I'm not sure it will help you replicate it. I have been using Windy several times per week for the last few years and this bug has always existed. It happens on every model for every layer for every part of the map. It happens on my phone (Pixel 3a) but also the one other Android phone I have tested it on so far (Oppo Find X5). My timezone is Europe/London in case that matters.

Is it possible that the time slider is doing some calculation based on screen width that is being unreliably calculated? (I know getting window dimenions in a browser/WebView can be error prone.)

What is definitely true is that the logic to determine what time to display on the time slider is not the same logic to determine what time of data to fetch and display on the map. Even if you can't reproduce, I would guess that you would be able to verify this in code.

How can I best help you investigate this further - provide more screenshots or a video, or get a list of more devices that are affected, or something else?

Version is currently 39.3.2.

On web when you select the sounding view, the temperature number is displayed on the map on top of whatever was being shown there previously, eg the wind arrow, so that neither are readable. You can get the temperature to go away if you switch layers or close the sounding.

This bug was introduced about 4 weeks ago IIRC.

This is a huge bug. It exists on every Android device I've tried. It's very frustrating Windy have completely redesigned the interface but don't fix this very simple error.

@Korina have the dev team looked at this yet?

Sorry for the delay replying. I have attached a screenshot but the bug is very easy to reproduce without. Tested on two phones. Surely wrong every Android phone.

The image shows two screenshots which both say "13:00" on the time slider, but the data shown is different for both. To be clear, the model has not changed, nor anything else besides moving the time slider. The only difference is that the second image has the time slider moved towards the end of the hour.

Basically every time a user looks at a forecast in the future, there's a 50/50 chance the data displayed will be wrong. This is an enormous bug and probably very easy to fix. I would guess that the code for getting the time from the slider is duplicated in two places, one using round, one using floor.

One more vote for scrolling through the timeline on mobile.

Also can we have an option for the green dotted line for thermals to be drawn automatically based on the actual surface temperature and surface dew point? This should really be the default. It is rare to want to know what a parcel of air would do if released into the atmosphere with some random temperature and random humidity.

Just want to highlight this bug again. I forgot to say the mobile platform is Android. No idea about iPhone. Tested on two devices. This is a major bug. Windy is fantastic in general.

And another issue with resetting. When you click somewhere on the map it resets the position of the map so that the clicked location is in the centre. This is a problem if you click near the edge of the areas of a particular model, because the map recentres on the point, then the model switches to another model because it considers the view to be outside the range of what is applicable for that model.

For example, choose ICON-D2, sounding, then click on Gloucester in the UK. The map scrolls so that Gloucester is in the centre of the non-sounding part of the map, then the model switches to ICON-EU. (I think it is using the centre of the whole screen - including the portion of the map that is hidden by the sounding pop-up - to determine whether the model can be used. So you have two inconsistent definitions of centre.)

It would be good if the zoom/scroll of the sounding window didn't reset either. This makes it hard to compare soundings for different spots. (As a paraglider pilot, I want to be able to look at the soundings for different parts of the country to help make a decision which site to go to.)

When you drag the time slider to, say, 15:00, you may get shown the data for 15:00 or 16:00 depending on exactly how far you slide it. Looks like a basic rounding error to me where the data for the position of the slider is rounded to the nearest hour in two different ways, one for text display on the slider, and two to decide which data to display on the map.

Very easy to reproduce and has existed as long as I can remember using Windy, so I'm not sure why it hasn't been noticed by the developers unless there's something more subtle going on.