STOP the Radar from AUTOMATICALLY going into FORECAST
-
@Suty Here's a perfect demo of the issue, we've got small rain cells moving east to west but the forecast totally reverses the showers.
-
Any news on this? Here we are beginning of May and the radar keeps automatically rolling into forecast, it's really frustrating and misleading when the display changes modes uncommanded and you don't notice.
-
@Frank-Billington It will be fixed in the version 46, planned to be released in the second half of May.
-
I've also found myself wanting a button to move the radar display to "Now" and "Last Observation".
I would also appreciate a version without the interpolation of the original data, which would just display the pixels as they are available. There was a funnel cloud a week ago near my sister's place, and I wonder if the radar signature might have been clearer without interpolation.
I do appreciate the good job that Windy does with integration of the various systems, particularly the US and Canada. I asked Environment Canada about that integration in 2004, after seeing a prototype briefly on their site.
-
@Suty It's June 1 and the problem persists.
-
@Frank-Billington Version 46 is planned to be released this week.
-
@Suty I can see that I'm now on version 46.0.1 on both my personal and work computers, but this issue is still occurring for me on both computers.
-
@MidwestDrummer Okay, and the issue appears after a few minutes or in a longer time?
-
Small update and apology from our team, this fix and solution will be available with next update to 46.1, since some complications appeared in the development.
-
@Suty Sorry for the late reply, and thanks for the update.
-
Is the 46 available already for IOS? I cannot find it in the AppStore
-
@michele7 No, it is still not. But I think it will be released in a week.
-
@Suty ...
March 12: "we will fix this issue with accidental switching to the forecast part in the next update"
May 5: "It will be fixed in the version 46, planned to be released in the second half of May."
June 2: "Version 46 is planned to be released this week."
June 6: "Small update and apology from our team, this fix and solution will be available with next update to 46.1, since some complications appeared in the development."
And now here we are nearly three weeks since:
June 9: "But I think it will be released in a week."
Look, I've worked in software web app customer service at the manager level, wedged between needy users and oblivious devs, I get that you might caught between a rock and a hard place, but (1) I have a really hard time buying that this can't be resolved with a hotfix. Someone there can certainly invest 30 minutes to find the bit of code that is doing this and comment it out until a permanent fix is sorted, and (2) if you are powerless to make that happen, then at least hold some people accountable to a realistic actionable fix date. If it is going to take 6 months, just say so and stop the credibility bleeding. I've already been burned a couple of times here telling my group that a fix for this is just a couple of weeks away - twice.
Thanks for reading. I don't miss that job.
-
@Frank-Billington We have this change already in the testing phase and it will be in version 47, which is planned as a next release. To confirm that information, I forwarded your post to our colleague from the dev team, responsible for that change.
-
@Suty appears to have been fixed, thank you and thanks to your devs. My guys are deeply appreciative, as I am sure the bulk of your customers also are.
