I have encountered the same issue and have given up on being able to do crosswind testing in MSFS 2024. I have tried one wind layer at the ground, multiple wind layers all with the same wind speed/direction at different altitudes, and just now with @LRBS's suggestion of setting one layer at 10,000 feet. 

Here is what happened on that last attempt and my hypothesis of what the problem is. On the ground at KLAX 25R, I moved the wind layer up to about 10,000 feet and set a wind of 40 knots at 340 degrees, gusts 0 knots at 340 degrees. Shortly after takeoff (I have a screenshot at about 2100 feet), the wind had increased to nearly 80 knots (340 degrees). To get the wind back to 40 knots, I had to change that layer to about 20 "knots." Returning to land, as I neared flare height, the wind started decreasing from 40 knots, reaching 20 knots by the time I touched down.

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).

1 hour ago, jcomm said:

In MSFS 2020 there were parameters like:

ground_crosswind_effect_max_speed = X
ground_crosswind_effect_zero_speed = Y

and even later with SU9 (MSFS 2020)

ground_high_speed_steeringwheel_static_friction_scalar
ground_high_speed_otherwheel_static_friction_scalar
ground_crosswind_effect_zero_speed
ground_crosswind_effect_max_speed

which are also used in MSFS 2024.

From the ASOBO documentation for MSFS2024 you can get:

ground_crosswind_effect_max_speed ::=

This parameter represents the world speed (in ft per second) at which 100% of the crosswind effect is applied to the aircraft.

Note that this value can be set to -1000 to have a 100% realistic simulation where the crosswind is never cancelled out.

Default value is 80.

ground_crosswind_effect_zero_speed ::=

 

This parameter represents the world speed (in ft per second) at which 0% of the crosswind effect is applied to the aircraft. This parameter will work in two different ways:

With the ground rudder assistance enabled, at the given speed and below, the lateral (x) component of the wind is set to zero.

With the ground rudder assistance disabled, crosswind is completely cancelled out below ground_crosswind_effect_zero_speed ft per seconds of IAS, and it is gradually blended in up to 100% at ground_crosswind_effect_max_speed ft per seconds of IAS.

Note that this value can be set to -1000 to have a 100% realistic simulation where the crosswind is never cancelled out.

Default value is 5.

 

100% correct. Just a side note, if they had correctly simulated those wind effects, we wouldn't see all these odd reactions during wind changes, unrealistic rudder fishtailing, bad tiller reaction, twitches, skidding, abrupt transition from the nose wheel steering to rudder during takeoff and landing,  etc. As an example, a Boeing 737, 757,767, 787, 747, and Airbus 330, 340, 380, due to their size, will not react at a crosswind of 5 KTS OR 8 FT/SEC, yet they claim that the "ground_crosswind_effect_zero_speed" default value should be 5 FT/SEC, equal to 2.9 KTS. Or, their statement is "Note that this value can be set to -1000 to have a 100% realistic simulation where the crosswind is never cancelled out. Same problem: they think the default for "ground_crosswind_effect_max_speed" is 80 FT/SEC or 47 KTS. All these errors combined result in a unrealist aircraft behaviour. Fortunately, only a few paying developers have managed to overcome ASOBO's shortcomings, such as the third-party add-ons Fenix, FlyByWire A380, and Ifly737.

14 minutes ago, Donstim said:

I have encountered the same issue and have given up on being able to do crosswind testing in MSFS 2024. I have tried one wind layer at the ground, multiple wind layers all with the same wind speed/direction at different altitudes, and just now with @LRBS's suggestion of setting one layer at 10,000 feet. 

Here is what happened on that last attempt and my hypothesis of what the problem is. On the ground at KLAX 25R, I moved the wind layer up to about 10,000 feet and set a wind of 40 knots at 340 degrees, gusts 0 knots at 340 degrees. Shortly after takeoff (I have a screenshot at about 2100 feet), the wind had increased to nearly 80 knots (340 degrees). To get the wind back to 40 knots, I had to change that layer to about 20 "knots." Returning to land, as I neared flare height, the wind started decreasing from 40 knots, reaching 20 knots by the time I touched down.

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).

Wow, that's a new one. In my case, if I set a 30 KTS x-wind, during the takeoff roll up to about 800 FT, my wind velocity shows only half; above 800, it changes to the 30 KTS value I set previously. During the approach to landing, the wind is 30 KTS up to about 800 FT, then dies down to 15 KTS for the touchdown. A totally unrealistic mess. VERY FRUSTRATING, such a joke.

31 minutes ago, LRBS said:

Wow, that's a new one. In my case, if I set a 30 KTS x-wind, during the takeoff roll up to about 800 FT, my wind velocity shows only half; above 800, it changes to the 30 KTS value I set previously. During the approach to landing, the wind is 30 KTS up to about 800 FT, then dies down to 15 KTS for the touchdown. A totally unrealistic mess. VERY FRUSTRATING, such a joke.

That appears to be the same unnecessary and unwanted meters/second to knots conversion (and reverse). Just manifested a bit differently.

1 hour ago, LRBS said:

Wow, that's a new one. In my case, if I set a 30 KTS x-wind, during the takeoff roll up to about 800 FT, my wind velocity shows only half; above 800, it changes to the 30 KTS value I set previously. During the approach to landing, the wind is 30 KTS up to about 800 FT, then dies down to 15 KTS for the touchdown. A totally unrealistic mess. VERY FRUSTRATING, such a joke.

I'm curious given the current discussion: do you perceive whether it's altitude based or speed based...? I.e., when you fly, I assume you do normal take-offs and approaches, which might make it appear to be influenced by alt rather than speed...?

If iFly and Fenix have implemented this properly, it's enough to get me to move over to them for this factor alone - is that confirmed?

do you or @jcomm know if any of the Hi Fi light GA aircraft implement this properly...? E.g., Black Square or A2A or...?

2 hours ago, jcomm said:

In DCS World it's even worst ... or at least not better... All aircraft with even the most sophisticated FMs only start "feeling" the normal wind component as their ground speed get's past a given limit... AEROFLY FS also limits x-wind near and on ground, ...

I'm beginning to understand why you're known as The UnInstaller!! 😁

In re DCSW, one always has to heavily squint their eyes when looking at "weather" effects and such. ED have even recently stated they're not interested in implementing real-time or even realistic weather(!). It seems really similar to the Prepar3D weather effects...?

It's somewhat understandable given the nature of DCS being regional map-based (rather than a global simulation), and, of course, the raison de etre of the simulation being realistic air combat rather than realistic aviation. It's kinda like you just need to pretend you're flying in SoCal in the summer time: it's always "72 and Sunny" 🤣

 

Edited February 23Feb 23 by UrgentSiesta

2 hours ago, Donstim said:

That appears to be the same unnecessary and unwanted meters/second to knots conversion (and reverse). Just manifested a bit differently.

I agree the conversion equation is correct (if that's the case), but why is it always 1/2 the wind velocity when wind is set manually to a fixed value, without any gusts or variance, and what triggers that switch at around 800 FT when you take off or land? The only thing I can think of is that when you set different options in Active Sky, there is an option "to bypass reduced wind speed at the surface."  Again, this seems to be in ASOBO's faulty coding, and instead of allocating time to fix it, they decided to implement this nonsense. 

1 hour ago, UrgentSiesta said:

I'm curious given the current discussion: do you perceive whether it's altitude based or speed based...? I.e., when you fly, I assume you do normal take-offs and approaches, which might make it appear to be influenced by alt rather than speed...?

If iFly and Fenix have implemented this properly, it's enough to get me to move over to them for this factor alone - is that confirmed?

do you or @jcomm know if any of the Hi Fi light GA aircraft implement this properly...? E.g., Black Square or A2A or...?

 

From my perspective, iFly and Fenix have managed to address this problem effectively; it's evident they employ qualified personnel and prioritize their product quality. They at least recognize bugs and work to fix them, unlike other developers who deny issues and continue selling defective products. Based on certain reviews and my experience flying similar aircraft professionally, I believe their quality and flight physics are quite convincing and a valuable addition to our hobby. To be frank, I have no regrets about spending money on these developers, and I don't feel deceived. 

3 hours ago, UrgentSiesta said:

I'm curious given the current discussion: do you perceive whether it's altitude based or speed based...? I.e., when you fly, I assume you do normal take-offs and approaches, which might make it appear to be influenced by alt rather than speed...?

If iFly and Fenix have implemented this properly, it's enough to get me to move over to them for this factor alone - is that confirmed?

do you or @jcomm know if any of the Hi Fi light GA aircraft implement this properly...? E.g., Black Square or A2A or...?

The issue in the post you replied to is not an airplane developer issue. It is purely an Asobo bug in the custom weather settings. It is based on whether the airplane is on the ground or not, or as was shown in the video in this post 

, any time you re-open the weather window and look at the wind that is set.  That is different than the parameters that allow developers to specify when a crosswind effect starts being appled.

2 hours ago, LRBS said:

I agree the conversion equation is correct (if that's the case), but why is it always 1/2 the wind velocity when wind is set manually to a fixed value, without any gusts or variance, and what triggers that switch at around 800 FT when you take off or land? The only thing I can think of is that when you set different options in Active Sky, there is an option "to bypass reduced wind speed at the surface."  Again, this seems to be in ASOBO's faulty coding, and instead of allocating time to fix it, they decided to implement this nonsense. 

It isn't a switch at 800 feet. It starts to occur as soon as the airplane is off the ground. The reason that is a factor of 2 (or 1/2 depending on your perspective) is, as I tried to explain before, a faulty use of converting units from meters/second to knots, or the other way around. MSFS 2024 seems to be confused over what units the wind input is and what the wind should be in the sim. When the inputs are approximately doubled (such as when you have made the input while on the ground and the airplane becomes airborne, or you simply re-open the weather window and look at the wind value), it is converting from meters/second to knots. When the input is halved, such as when you are in the air, and you input a wind value, it is converting from knots to meters/second.

You have to be careful about how you are verifying what the wind actually is in the sim. You can do that by using the simulation variables (simvars) "ambient wind direction" and "ambient wind velocity." The wind won't increase in a step fashion, Asobo a while ago put in a nice, smooth transition for wind changes after step changes from live weather caused a lot of problems. So you won't see the wind suddenly jumping when you go from the ground to being airborne, or vice versa, but you can definitely see it start to increase immediately after becoming airborne and end up at half the value input in flight when the airplane touches down.

 I've made a little video that shows the increase after liftoff. (Ignore the piloting; I did not bother fully set up the MCDU or to even watch what I was doing input wise.)

2026-02-23 18-52-02.mp4

Edited February 24Feb 24 by Donstim

27 minutes ago, Donstim said:

It isn't a switch at 800 feet. It occurs as soon as the airplane is off the ground. The reason that is a factor of 2 (or 1/2 depending on your perspective) is, as I tried to explain before, a faulty use of converting units from meters/second to knots, or the other way around. MSFS 2024 seems to be confused over what units the wind input is and what the wind should be in the sim. When the inputs are approximately doubled (such as when you have made the input while on the ground and the airplane becomes airborne, or you simply re-open the weather window and look at the wind value), it is converting from meters/second to knots. When the input is halved, such as when you are in the air, and you input a wind value, it is converting from knots to meters/second.

You have to be careful about how you are verifying what the wind actually is in the sim. You can do that by using the simulation variables (simvars) "ambient wind direction" and "ambient wind velocity." The wind won't increase in a step fashion, Asobo a while ago put in a nice, smooth transition for wind changes after step changes from live weather caused a lot of problems. So you won't see the wind suddenly jumping when you go from the ground to being airborne, or vice versa, but you can definitely see it start to increase immediately after becoming airborne and end up at half the value input in flight when the airplane touches down.

 I've made a little video that shows this. (Ignore the piloting; I did not bother fully set up the MCDU or to even watch what I was doing input wise.)

2026-02-23 18-52-02.mp4

What you experience is totally different from what I do. My situation is different, as I mentioned, I set a crosswind of 33 KTS with a layer up to 10K. During t.o., my wind velocity is tabulated at 1/2 the value (16 KTS) until about 800 FT, from which it increases to 33 KTS up to 10K. During descent, 33 KTS is displayed until 800 FT, then drops to 16. So obviously, different scenarios with different outcomes. For sure, something is amiss with them: they don't understand how it should work and can't program correctly. Too bad.

1 hour ago, LRBS said:

What you experience is totally different from what I do. My situation is different, as I mentioned, I set a crosswind of 33 KTS with a layer up to 10K. During t.o., my wind velocity is tabulated at 1/2 the value (16 KTS) until about 800 FT, from which it increases to 33 KTS up to 10K. During descent, 33 KTS is displayed until 800 FT, then drops to 16. So obviously, different scenarios with different outcomes. For sure, something is amiss with them: they don't understand how it should work and can't program correctly. Too bad.

Where is your 33 KTS (or 16 KTS) displayed? How about a video?

Edited February 24Feb 24 by Donstim

1 hour ago, Donstim said:

Where is your 33 KTS (or 16 KTS) displayed? How about a video?

 

13 hours ago, LRBS said:

@Area, please follow my suggestions,

and read my previous post, please.

 

I followed your suggestions and the problem persists:

 

To clarify, if I don't close the weather window but minimize it, the wind speed remains at the initial value I entered.

Edited February 24Feb 24 by Area

10 minutes ago, Area said:

I followed your suggestions and the problem persists:

 

To clarify, if I don't close the weather window but minimize it, the wind speed remains at the initial value I entered.

Sorry to hear that. Unfortunately, this software has many disappointing aspects.