Winds in Knots

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes

Brief description of the issue:

Wind is displayed in m/s, whereas it should be displayed in knots as this is the standard ICAO way. Independant of Hybrid, Metric or Imperial.

Provide Screenshot(s)/video(s) of the issue encountered:

No

Provide coordinates (DevMode > Options > Display position)

No

Provide time & date of the observed Weather issue

No

Detailed steps to reproduce the issue encountered:

Wind is displayed in m/s when in Hybrid mode.

PC specs and/or peripheral set up if relevant:

i9/ 4080 nvidia/ 64Gb

Build Version # when you first started experiencing this issue:

1.33.8


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Check out this post: Wind speeds in m/s - #2 by N6722C. Only US.SYSTEM (imperial) uses speed in knots, the other 2 ones are using m/s as per design, they are not considering it as a bug:
Wind speeds in m/s - #16 by Jummivana

Yes, but the problem is, when set to the USA Units, Knots, ATIS is correctly calling the speed as Knots, but is giving a numeric value which is x2, and closer to ft/sec.

So, for example, if ATIS says the wind is 10 knots and its a direct crosswind, that seems reasonable for a small GA plane, BUT that 10 is really the speed in m/s, and the true speed in knots is about 19 knots ( approx double), which is a “Challenging” cross wind for most GA pilots.

So USA Sim pilots are thinking the cross wind is 10 knots, and then being alarmed that they cannot handle what is really a 20 knot crosswind, and typically blaming the plane’s flight model for being inaccurate !!!

All one has to do is look at the simvariable, displayed in Knots, to clearly see that the ATIS is reporting about half that speed – something that should be “TRIVIAL” to fix.

– maybe it has been “fixed” recently ???

1 Like

Ok, what you are reporting looks a different issue than what reported in the OP. In the OP I undersand that in the weather settings window, wind speed should always been expressed in knots whatever the unit of measurement is selected.
The issue you are describing is when selecting US settings, in the weather window you are seeing knots but when flying wind is blowing in m/s. Am I correct ?. Personally I am not experiencing that issue. When flying I am using LittleNav map and I am seeing the same value in knots than what I have in the sim. If you have screenshots as evidences it would help to understand your issue.

That is correct. I’m only reporting that in a Hybrid environment we NEVER user m/s in real life. I saw some discussions here, that for example gliders use meters and m/s as units, but (don’t get me wrong please) this is not a glider sim only.

But If Asobo wants m/s “as per design”, that is ok of course, but technically it is wrong. In a hybrid envorinment we always use knots as unit of measurement.

Only Russia and China use(d) m/s as units of measurement, but I’m not sure if they still do. They may have adapted to knots as well.

Thanks for the links to the other topics. I will check them out.

China and Russia still uses M/S:
ZGGG 260830Z 34006MPS 310V010 9999 FEW060 38/23 Q1000 NOSIG
UUEE 260900Z 12005MPS 9999 -TSRA BKN026CB 23/18 Q0999 R06C/CLRD62 TEMPO VRB10G18MPS 1000 TSRA SQ BKN007 BKN016CB

Always have to be the two countries doing things differently from everyone else. :laughing:

NO, the Opposite. Wind is blowing at correct speed, but ATIS in the USA is reporting wind as a m/sec numeric value, but calling it Knots.

I will re-check this and confirm is still happeneing or not) , with screen shots of ATIS text and simvar display (as I did a year ago)

Frustrates me to no end, when I see Asobo making the excuse that something is “Correct” and “By design”, when it is technically incorrect.

2 Likes

Oh ok, so if you can still reproduce it with evidences then you should open a new bug report, I don’t think there is an existing one.

Not only that, but distances are in kilometers and speeds in kilometers per hour, which is WRONG, hybrid uses knots and nautical miles as well, the developers should understand that since they live in France which uses this exact format like most of the world.
Having said that I do not expect this being addressed anytime soon, this sim already has many more important problems currently, such as that annoying white dot, that despite causing a lot of stir, being much more game breaking hasn’t been fixed in over 2 months, and probably won’t be fixed until September when su13 drops.

1 Like

I find it most interesting what is important to some people. !

The wind being reported incorrectly , at about ha;f of what it really is, which in the RW could be a total disaster

or

A little white cosmetic white DOT, that can appear on the screen under specific conditions.

If ever there was a test to distinguish someone interested in Flight Simulation to someone why just want to play at a flying game, the above might be the ideal question .

– BTW --as this is in a PC topic, as opposed to an X-box topic, there is already a simple MOD available for FREE, to eliminate the trivial white Dot issue.

Not so easy for a user to fix the incorrect wind speed issue

3 Likes

You are, of course 100% Correct … Do not post things as FACTS, without some PROOF … so here it is,

Latest version of MSFS as of 7/26/2023

Sitting on Ground, with weather set to winds 271 @ 21 (True North, and Knots)

Atis is reporting wind as 281 @ 42 (Mag north & Knots)
USA Units, at KIAD, USA

Simvars for ambient wind shown, confirming that wind is really as set, 20,8 Knots

So why is ATIS saying 42 Knots ?

42 is not Knots, or m/s
Closest is ft/sec which would be 35.2 but that is not the 42 that Atis is reporting,

Garmin is correcting displaying wind as 21 Knots

So what units, or crazy calculation is MSFS Atis doing to be reporting 42 as the speed in knots. ???

and how difficult is it for Asobo to fix this, which has been reported continually for the past 3 years, as being totally INCORRECT

Asobo: BY DESIGN ??? well, DESIGN is INCORRECT, so please correct the design, and then correct the Code.

This is embarrassingly shameful

=============
Actually, it is looking like Atis is reporting the windspeed as KNOTS x 2

Note. These are meant to be GROUND level winds, and not some “calculated” winds @ 1000ft.
The ATIS wind sensor is ground based, typically on a tower (that is not 1000ft tall)

ASOS_011

2 Likes

You mean like how the united states uses imperial measurement but everyone else uses metric?

We commonly think of bugs as “broken code” to be fixed. However bugs can and do occur at any time during development and production. This may be an example of a code bug or possibly a design bug. There can be requirements bugs which are the most difficult to fix. For example there is a requirement that winds sometimes have TRUE and other times MAGNETIC direction or what units are used to display speed. If the requirements are not captured correctly, the design is going to be wrong and the the code will be displaying incorrect information. “Working as designed” does not mean there isn’t a design or requirements bug. For users, it all looks the same. Something isn’t working correctly.

1 Like

FYI: You are responding to a Software Analyst and Project Manger in the Aerospace Industry, so yes, I understand where you are coming from, but in this case, its just a naive aviation system mistake.

(Former Project Manager for weather sensor development for USA ASOS - AWOS systems)

2 Likes

even experts get it wrong sometimes. We’re all human, everyone makes mistakes and we’re all entitled to our opinions.

This isn’t a hill to die on.

Dude, I’ve had this white dot cut my mixture on final approach in the new comanche, because it appeared as soon as I was going to pull it full in, and it pulled it all the way out, it’s specially bad for me because my joystick is old and a bit noisy so it appears often and makes it difficult to press and flick switches and some times caused my engine to turn off in a critical phase of flight.
so yeah that is much more game breaking for me than the wind being reported incorrectly by an ATIS that I DO NOT USE, I have no use for the in-game ATC which is terrible in every way shape or form and I have it disabled. I use VATSIM, when no controller is available I use the digital ATIS from real world available for the entire USA, which not only gives me the correct wind information but also which taxiways, runways are closed and more actual useful information I use for my flight.

Now If you use the sim ATIS and is upset it is giving wrong information that is fine, you have the right to complain and I think you’re right, this should be fixed, all I did was point out that a fix for this is likely not coming any time soon, whether you like it or not the community is way more upset about the white dot, simply look how many replies that thread has and how recent it is, and yet it hasn’t been fixed for months, and won’t for months to come, so you can only imagine how long it will take them to fix this that has a very small amount of people upset about.

How come this topic is in General Discussion / World instead of Bug reports?

1 Like

No everyone else is either using US Imperial or Hybrid. Metric is only used in very very few countries.

Sorry I moved it.