Hello,
The CAT on the new update is terrible. Only goes to FL300, which we used to be able to use it to FL450 and you can no longer adjust the altitude while using IFR/Distance and Planning routes.
Please bring back the previous version, this one really is terrible compared to what you had before.
Also, soundings still do not take start at the elevation of the location. A sounding in Denver, CO should NOT start at 1000mb, since they are roughly 6000FT in elevation.
Good morning!
As of today when I open soundings it automatically opens with the meteoblue AI everytime, even though my model is set at ECMWF, GFS, ICON, etc. Is there a way to not have it open with meteoblue AI every single time?
@Suty Good Morning!
I have attached 2 screen shots. The first one is a GPX route sting, where we are able to adjust the flight levels on the map while in the mode.
The 2nd screen shot is the same route string, but with the clear air turbulence overlay. We used to be able to adjust the flight levels while in the format, but now we cannot. We use FL390 the most (for what I do), so only having up to FL300 available is pretty useless now. And I have to exit out of this to adjust to flight level, then go back into this. Its taking almost double the amount of time than it did before.
Note, on the first image (winds), the flight level toggle is adjustable. On the CAT one, it is no longer adjustable
Hello,
The CAT on the new update is terrible. Only goes to FL300, which we used to be able to use it to FL450 and you can no longer adjust the altitude while using IFR/Distance and Planning routes.
Please bring back the previous version, this one really is terrible compared to what you had before.
Also, soundings still do not take start at the elevation of the location. A sounding in Denver, CO should NOT start at 1000mb, since they are roughly 6000FT in elevation.
My colleagues and I noticed that the station points for the airports around the world are no longer showing on the Windy interface. Is this something that is part of a recent Windy update?
Hello,
Me and a handful of my colleagues noticed that the elevation on the skew-T soundings is not taken into account. Basically, the Sounding starts at sea level for places like MMTO (Mexico City) that are high in elevation instead of starting at the elevation of the airport. Is there any way to get this fixed? Thank you!
Searching for an airport or pulling up soundings in route mode will often cause the entire program to freeze.
@Suty Thank you, that would be excellent. I've found no other issues.
It's too difficult to see changes in the wind barbs to quickly eye layers of shear. Either go back to a light background for the soundings or change the wind barbs to a more contrasting white color.
Preferably use a white background with black wind barbs, how it was, because wind barbs should be dark.
Thanks
@Suty The Flight Planner plugin has been very useful. I would like to see it compatible with this new version.