Donstim

The aircraft tracking debug window in dev mode will give you the ground and air distance separately as well as the total distance from when you opened the window. Takeoff and landing distances include both a ground and an air distance. You can get the ground distance easily from the debug tracking window, but to get only the portion of the air distance you want it works best to make a video to be able to separate out the portion of the total air distance that you want to add to the ground distance to get the complete takeoff or landing distance.

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

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

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

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

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.

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

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

I'm a little curious as to where you came up with these entries as many of them are either deprecated or non-existent in the FS2020 SDK, and only a few of them would affect the behavior the OP is concerned about.

By jove, you've found it. I had my winds set with AGL for exactly this reason. I had found this some time ago, and that is why I changed to using AMGL, but had completely forgotten about it. @LRBS If using the AMSL altitude basis for preset weather, the winds are halved for some reason. The total wind velocity is halved, so both headwind/tailwind and crosswinds are affected. (Don't ask me why!☺️)

Interesting. Have you tried it with the default Asobo 787-10? I think that one has the crosswind parameters set to use the real wind by default. At least, I don't remember having to change them.

If you install the MSFS SDK, Simvar.exe should be in C:\MSFS SDK\Samples\SimvarWatcher\bin\x64\Release That's for MSFS 2020. I don't know if it would be any different for MSFS 2024.

Good question. Are you manually entering or confirming the correct value for the 2 ground crosswind parameters into the Flight Tuning section of the flight model.cfg file and making sure there isn't a different entry later in the file? Are you doing this before starting MSFS? I just confirmed that the PMDG 737-700 works the same way I showed for the default Asobo 787-10 once I manually edited the 2 crosswind parameters to change their values to -1000. Screenshot below. The true vs mag heading issue remains as well. Not sure about that one. Screenshot 2025-03-30 114058.jpg

The same wind direction issue is present with live weather. I just confirmed it with the 787, and @fsiscool's screenshot shows it as well (magvar for KJFK is 13 degrees W). Screenshot 2025-03-30 083310.jpg

Sure it is. Which airplane did you use? See below screenshot for the default 787-10. I also included the Simvar watcher window, which shows exactly what wind is being applied in MSFS (that is, for the default ground crosswind parameters it will show half the crosswind that is input in the weather UI). The ambient wind velocity/direction and ambient wind X (crosswind) all show the full 20 knots of crosswind being applied. @jcomm the Simvars show wind direction referenced to true. Since the ambient wind direction Simvar is the same as the wind direction that was input in the UI, this implies that input winds are referenced to true. Note that the 787-10 cockpit wind display shows a different direction, which is different by approximately the magvar for that runway. Normally wind direction shown on airplane NDs is referenced to true, but I don't know if that's the case with the 787. If it is, then there is something either messed up with the display coding, or there is something odd about manually input wind direction in MSFS and the Simvar depiction of it. Screenshot 2025-03-30 080741.jpg