LRBS

Which airplane are you using, and what’s your turbulence setting in the simulator? It's hard to evaluate without more information.

Installing the new NVIDIA driver fixed the issue for me. However, I'm still not satisfied with the app and continue to experience intermittent CTD problems. If I avoid using the app, everything works well. Something feels off with NVIDIA lately, which is very frustrating.

They possess gaming software with specific quality features. Obtaining a "simulator data license" is a lengthy and stringent process. A few examples include needing regulatory approval from the FAA, EASA FSTD, compliance for professional ATPL, and aircraft OEM, in addition to demonstrating accuracy. Unfortunately, they do not meet these requirements. The computer-based training (CBT) licensed by the FAA or EASA part ORA, utilized by a few airlines, only included the Level D 767 and Aerowinx 747.

In addition to an excellent product, it is worth noting that they did not snap at customers or speak down to them. Their technical and customer support was exceptional.

That is exactly right; the other thing worth mentioning is the "original" aircraft manuals for copyrights, etc. That's the reason why they don't provide them anymore. Just sell gimmicks, like "study level" terminology.

For free software, even though it's a work in progress, this product is fantastic. It outshines many paid developers. Congratulations! ❤️

The issue here is quite simple: something is incorrect and needs fixing. We want to enhance this software. If people are satisfied or unaware of what is incorrect, they should avoid unproductive discussions and enjoy what they like. However, please don't go in this unprofessional direction and tell people what to use or buy. This attitude is not advantageous for software development. Many years of issues with this ASOBO MSFS have already occurred, and limited progress has been made in many areas that require fixing.

I recently went through two Windows 11 re-installations and discovered that the first problem is related to NVIDIA drivers with the NVIDIA App. The second major issue is MSFS2024, which is full of bugs, causing all kinds of problems almost every time you start it. I've decided to give up on it for now; with MSFS2020, I don't have any issues. In its current state, MSFS2024 is not worth it.

No, I didn't think it could be any other way than AGL. Gentlemen, thank you very much for your effort. I'm using a VPN, and I'm not sure if this will work. Someone did a new MSFS installation, and now it is running fine on his PC. I hope that in a week, when I get home and do a re-install, it will also resolve my issue. THANK YOU!

I'm truly confused. All the entries are there, with the same wind as you have, but I haven't had any success. I have to leave on my trip for a week. If you find anything or anybody else, please send me a message. Two other (pilot) friends are experiencing the same issue. I wonder why three different computers experience the same problem and others don't. By the way, is anybody else here reading these posts seeing this behavior?

So, I used ms2020 at jfk 31l wind 230/16 with pmdg738, 748, 172, 208, 320. Same wx in ms2024 with the same default 748, lcf, 172, 208, 320, 330. See the pics. Rightfully so, in your example, it is correct. As it was mentioned, we concluded that when wx is injected by live wx, there is no issue, only when manually triggers that problem. See the next pics out of the KSEA manual wx, 080/20; the last one is on msfs2024. The same scenarios were tested on two other different computers with the same results. I'm wondering what's going on here.

Matt, Thank you! Hopefully, they will resolve this issue. The more I delve into this, the more I believe there's an issue with the WX panel. Yes, when it matches ATIS, this problem is not a concern at all. You see, if someone wants to "practice" a crosswind situation like this, they will get incorrect results.

Any airplane in MSFS 2020 or 2024 that displays wind data on the navigation display (ND).

Unfortunately, that's not the answer.

Matt, I hear you loud and clear. Let me try again; I am talking only about a crosswind condition; wind direction is not an issue at all; the velocity computations are wrong. They show 1/2 of the actual speed during the takeoff roll, and they kick into the correct value after t.o. at about 800-900 FT. This wind velocity indication should have nothing to do with ground_crosswind_effect_zero_speed and ground_crosswind_effect_max_speed. One is a meteorological condition, and the other is an aerodynamic adjustment that should not affect the wind direction or velocity. I just tried the 172, 208, 320, 330, and the 747s, and all show the same issue. At a crosswind condition, velocity is reduced by 1/2. See the picture; the actual surface wind is 230/15, and all show something different. As I stated, this does not happen in the real life.