40 minutes ago, Area said:

Since I didn't get a concise answer (this isn't a criticism of the participants in this discussion),

I turned to the flightsimulator.com forum.

The problem stems from this setting:

Topic : https://forums.flightsimulator.com/t/custom-weather-2024-su4-wind-speed-increases/758871

 

Did you notice any changes? Switching from Hybrid, US, or the other option doesn't show any change on my system. I'm checking with another user and waiting for an answer. 

Thanks.

Yes.

Settings: Language options > Unit of measurement => American.

On the ground, in the weather window, I set the wind speed to "5", I close the window and then reopen it; the wind speed remains at "5". I repeated this several times; the speed remains at 5.

I haven't tried testing this: on the ground, set the wind speed to "5", take off, gain altitude, and check.

29 minutes ago, Area said:

Yes.

Settings: Language options > Unit of measurement => American.

On the ground, in the weather window, I set the wind speed to "5", I close the window and then reopen it; the wind speed remains at "5". I repeated this several times; the speed remains at 5.

I haven't tried testing this: on the ground, set the wind speed to "5", take off, gain altitude, and check.

If you have time, would you check a 20 KTS x-wind and see what is shown during take-off roll and initial climb, please?

21 hours ago, LRBS said:

 

Thank you for posting this. Sorry it took so long for me to respond. This is showing exactly what I described. The wind on the ground was the input wind divided by 1.94 (the meters/second to knots conversion factor). The wind started increasing just after you left the runway. It looks like it just reached your input value of 33 knots at the end of the video when you were at 1240 feet radio altitude. From this, it is easy to conclude that MSFS 2024 is using the wind speed in meters/second (as your input wind in knots was divided by 1.94) on the ground, and the wind is in knots in flight. There is a transition gradient between them that appears to be on the order of 1200-1300 feet.

20 hours ago, jcomm said:

@Donstim,

are you by any chance my preferred freeware WW2 for XP maker ??? 🙂

I'm curious 🙂

 

Sorry, never worked on any projects for XP.

16 hours ago, Mark1616 said:

In the video example, the wind behaves precisely as intended. The wind speed at the ground is less than prescribed, due to the surface friction, it reaches the prescribed value at about 1000 ft, whereafter it continues to slowly increase with height following the logarithmic wind profile, as it should in the boundary layer. 

I think others have already pointed out that you are missing the point here. The intent is to use a custom weather setting such that there will be no wind gradient, that is, to have a constant wind from a specified altitude all the way to the ground. This can be done very easily in MSFS 2020, but is impossible in MSFS 2024.

14 hours ago, Area said:

Since I didn't get a concise answer (this isn't a criticism of the participants in this discussion),

I turned to the flightsimulator.com forum.

The problem stems from this setting:

Topic : https://forums.flightsimulator.com/t/custom-weather-2024-su4-wind-speed-increases/758871

 

Only the issue of the winds being increased by a factor of 1.94 every time the wind input in the weather dialog box is opened is associated with this setting. The bigger issue (at least for me) of having in-flight winds 1.94 times higher than the ground wind (with a wind gradient as you near the ground) is not caused by this setting, nor is it resolved by using either the US measurement system or the metric measurement system.

12 hours ago, LRBS said:

If you have time, would you check a 20 KTS x-wind and see what is shown during take-off roll and initial climb, please?

I've checked it with both the US measurement system and the metric measurement system. In both cases, the in-flight wind is 1.94 times higher than the wind on the ground with a wind gradient applied starting at a low altitude (somewhere around 1000-1200 feet). If the US measurement system is used, the input wind speed is taken as knots, but is converted to meters/second (divided by 1.94) when on the ground. In flight (above 1200 feet), the wind will be the input wind. If the metric measurement system is used, the input is taken as being in meters/second, and will be the wind used when on the ground. In flight, the wind will be converted to knots, and will be 1.94 times the input wind. 

In both cases, the in-flight wind is 1.94 times the ground wind, with the transition occurring gradually from ground level up to about 1000-1200 feet).

12 hours ago, Donstim said:

Thank you for posting this. Sorry it took so long for me to respond. This is showing exactly what I described. The wind on the ground was the input wind divided by 1.94 (the meters/second to knots conversion factor). The wind started increasing just after you left the runway. It looks like it just reached your input value of 33 knots at the end of the video when you were at 1240 feet radio altitude. From this, it is easy to conclude that MSFS 2024 is using the wind speed in meters/second (as your input wind in knots was divided by 1.94) on the ground, and the wind is in knots in flight. There is a transition gradient between them that appears to be on the order of 1200-1300 feet.

Sorry, never worked on any projects for XP.

I think others have already pointed out that you are missing the point here. The intent is to use a custom weather setting such that there will be no wind gradient, that is, to have a constant wind from a specified altitude all the way to the ground. This can be done very easily in MSFS 2020, but is impossible in MSFS 2024.

Only the issue of the winds being increased by a factor of 1.94 every time the wind input in the weather dialog box is opened is associated with this setting. The bigger issue (at least for me) of having in-flight winds 1.94 times higher than the ground wind (with a wind gradient as you near the ground) is not caused by this setting, nor is it resolved by using either the US measurement system or the metric measurement system.

I've checked it with both the US measurement system and the metric measurement system. In both cases, the in-flight wind is 1.94 times higher than the wind on the ground with a wind gradient applied starting at a low altitude (somewhere around 1000-1200 feet). If the US measurement system is used, the input wind speed is taken as knots, but is converted to meters/second (divided by 1.94) when on the ground. In flight (above 1200 feet), the wind will be the input wind. If the metric measurement system is used, the input is taken as being in meters/second, and will be the wind used when on the ground. In flight, the wind will be converted to knots, and will be 1.94 times the input wind. 

In both cases, the in-flight wind is 1.94 times the ground wind, with the transition occurring gradually from ground level up to about 1000-1200 feet).

Thank you. I appreciate it. ASOBO really needs to improve. There are numerous inconsistencies and missing features.  

On 2/25/2026 at 4:58 AM, Donstim said:

've checked it with both the US measurement system and the metric measurement system. In both cases, the in-flight wind is 1.94 times higher than the wind on the ground with a wind gradient applied starting at a low altitude (somewhere around 1000-1200 feet). If the US measurement system is used, the input wind speed is taken as knots, but is converted to meters/second (divided by 1.94) when on the ground. In flight (above 1200 feet), the wind will be the input wind. If the metric measurement system is used, the input is taken as being in meters/second, and will be the wind used when on the ground. In flight, the wind will be converted to knots, and will be 1.94 times the input wind. 

However the model is intended to work it should be the same with either measurement system. Have you reported this on the official forums as a bug and if so do you have a link to it?

I have noticed wind blows my plane the opposite direction of the flag. If the wind sock is blowing left, my plane will drift right, and vice versa

edit: Never mind, i just learned a physics lesson

Edited February 26Feb 26 by Sweetd31

6 minutes ago, Sweetd31 said:

I have noticed wind blows my plane the opposite direction of the flag. If the wind sock is blowing left, my plane will drift right, and vice versa

Drifts or points? Think of the tip of the wind sock as the edge of an arrow indicating what direction the wind is blowing to... Your aircraft wiill try to align with it, pointing towards where it comes from ..., but the actual drift if it happens should be towards the left indeed... Unless your heading and speed compensate for it...

Edited February 26Feb 26 by jcomm

Thank you, i just stumbled upon a reddit post explaining the physics of it! Would of never thought of that

27 minutes ago, Sweetd31 said:

Thank you, i just stumbled upon a reddit post explaining the physics of it! Would of never thought of that

A yacht (sailboat) tries to round up into the wind as well, especially in gusts. Steer away from the wind is a good way to remember it.

On 2/23/2026 at 5:01 PM, Donstim said:

 

What looks to me like what is going on is that the MSFS 2024 is confusing meters/second and knots. It seems to take the input wind speed in knots fine on the ground, but once airborne assumes it is in meters/second and converts it to knots (nearly doubling it). So to get the right speed in knots in the air, you need to halve the value of the desired wind when entering it in the custom weather window. Then when you get back to the ground, it converts it back, so that the wind you put in the weather window is what you get (which is half of what you wanted).

In regular Live Weather, surface winds come from the latest METAR report (in knots) and winds aloft come from the MeteoBlue model. I believe the transition from METAR wind to MB model wind happens about 1500 feet AGL.

Wind speed in a gridded weather model is always expressed in meters per second. The direction is expressed in rectangular coordinates U and V in which the U is the east/west component and V is the north/south component. Actual direction is calculated by doing a rectangular to polar coordinate transform.

It appears that when winds are set manually, the entered direction is being used (as entered), but the conversion routines used for the MeteoBlue model wind speed are still active even though the model is not actually in play. That would explain why speed manually entered in knots is being interpreted as meters per second above a certain AGL altitude. It seems as if this would be an easy thing for the developers to fix. The MB model wind parser should be completely disabled when manually entering wind. The directional parser is indeed disabled, but the speed parser is still active when it should not be.

Edited February 26Feb 26 by JRBarrett

29 minutes ago, JRBarrett said:

In regular Live Weather, surface winds come from the latest METAR report (in knots) and winds aloft come from the MeteoBlue model. I believe the transition from METAR wind to MB model wind happens about 1500 feet AGL.

Wind speed in a gridded weather model is always expressed in meters per second. The direction is expressed in rectangular coordinates U and V in which the U is the east/west component and V is the north/south component. Actual direction is calculated by doing a rectangular to polar coordinate transform.

It appears that when winds are set manually, the entered direction is being used (as entered), but the conversion routines used for the MeteoBlue model wind speed are still active even though the model is not actually in play. That would explain why speed manually entered in knots is being interpreted as meters per second above a certain AGL altitude. It seems as if this would be an easy thing for the developers to fix. The MB model wind parser should be completely disabled when manually entering wind. The directional parser is indeed disabled, but the speed parser is still active when it should not be.

Very well thought !

7 hours ago, bailout said:

However the model is intended to work it should be the same with either measurement system. Have you reported this on the official forums as a bug and if so do you have a link to it?

I reported in on the developer's forum. Do you have access there?