Reversed Wind Directions?

Ok, time for a, "why is this designed this way" question.

Why is the editor setup to give a "to" wind direction, when we receive a "from" wind direction in game.

Setting up a bit of crosswind training practice flying into Senaki-Kolkhi. Landing on runway 09 with a 20 knot left to right crosswind from due north 00 degrees.

When you actually fly the mission the wind is coming from due South 180 degrees.

Thanks folks!

Nobody knows. It has been like that since the beginning for no intelligent reason.

Ok, time for a, "why is this designed this way" question.

Why is the editor setup to give a "to" wind direction, when we receive a "from" wind direction in game.

 

[ATTACH]151196[/ATTACH]

 

Setting up a bit of crosswind training practice flying into Senaki-Kolkhi. Landing on runway 09 with a 20 knot left to right crosswind from due north 00 degrees.

When you actually fly the mission the wind is coming from due South 180 degrees.

 

[ATTACH]151194[/ATTACH]

 

Thanks folks!

++1

Think of it like the TV weater forecast,

if the wind is blowing north to south the arrows on the forecast map point south,

so in the editor if you wanted to have the wind blow north to south you need to point the arrow direction indicator to face south like on the weather forcast

Think of it like the TV weater forecast,

if the wind is blowing north to south the arrows on the forecast map point south,

so in the editor if you wanted to have the wind blow north to south you need to point the arrow direction indicator to face south like on the weather forcast

He knows that.

I saw this feature request a few times already and I am 100% in support. Afaik in all of aviation you get wind in 'bearing from' not in wind to, this is confusing as hell and an option/mod to set this would be great.

Same for wind in the briefing I believe.

I think, it is just an user interface thing. That small knob that you can rotate to enter headings - it is used wherever a direction is to be entered in the mission editor. And so, in ancient times, someone at ED used this knob as well for wind, to enter 0 - 359 degrees ... as a heading/where-the-wind-blows-to/etc. which is just contrary to everyday RL handling of wind directions ("where-it-blows-from").

It is correct to do so that when "north-wind" blows, it is marked so that arrow points to South, and not to North.

The arrow shows the direction where the motion is going, not where it is from.

Windsocks (and smoke plumes) Point south when a north wind blows, but no one finds that confusing when the tower tells you the wind direction is 0 degrees, so just mentally call the arrow in the editor a windsock and it is fixed. No need to change it. ;)

Windsocks (and smoke plumes) Point south when a north wind blows, but no one finds that confusing when the tower tells you the wind direction is 0 degrees, so just mentally call the arrow in the editor a windsock and it is fixed. No need to change it. ;)

The problem is that when you have north wind, the mission briefing will inform you that you have 180 deg wind :). The ATC will give you the correct heading (0).

Yes. Wind direction has been a headache for as long as I can remember!

Maybe it's just the way my brain works? I am old ;)

Once we solve this one, maybe we can tackle the thorny issue of how dates are written too? Is December 1st written 1/12/2016 or 12/1/2016? The same principal applies. It is simply a question of interpretation.

I have a feeling that wind direction is described the way it is due to the way weather vanes work. They point towards the direction the wind is blowing from, but that doesn't invalidate the use of a system in which a wind can be described as a direction the wind is blowing to. All you need to know is which applies in which situation.

As we know that the mission planner works by indicating the direction the wind is blowing to, and it isn't the same method as used by air traffic controllers, then the problem is solved. Neither system is incorrect, they are just different.

If however you would like ED to change the format to save confusion, then of course, that is an entirely different matter. The fact is however, that as soon as you see what is happening, the problem is solved.

There is another issue regarding the Wind (I can't find a more suitable place to mention it).

The smoke stacks etc show smoke blowing downwind (EG: Right to Left) but we have to use the Opposite Rudder (regardless of aircraft) to compensate. If as in the Example above the wind is blowing right to left, then one would expect to have to use Right Rudder to compensate.

BUT for quite some time now (in both Single and MultiPlayer), we have had to use the Left Rudder input to compensate.

This can be very confusing since ED refuses to create Wind Socks at airports, counting on Smoke Stack Smoke (which should work well enough IF there are smoke stacks close enough to see the direction the smoke is blowing) AND since the Physics of Wind vs Rudder Compensation is Bass-Aackwards. !!!!

Please Fix This.

There is another issue regarding the Wind (I can't find a more suitable place to mention it).

 

The smoke stacks etc show smoke blowing downwind (EG: Right to Left) but we have to use the Opposite Rudder (regardless of aircraft) to compensate. If as in the Example above the wind is blowing right to left, then one would expect to have to use Right Rudder to compensate.

BUT for quite some time now (in both Single and MultiPlayer), we have had to use the Left Rudder input to compensate.

This can be very confusing since ED refuses to create Wind Socks at airports, counting on Smoke Stack Smoke (which should work well enough IF there are smoke stacks close enough to see the direction the smoke is blowing) AND since the Physics of Wind vs Rudder Compensation is Bass-Aackwards. !!!!

 

Please Fix This.

There are wind socks, you can place them in mission editor.

There is another issue regarding the Wind (I can't find a more suitable place to mention it).

 

The smoke stacks etc show smoke blowing downwind (EG: Right to Left) but we have to use the Opposite Rudder (regardless of aircraft) to compensate. If as in the Example above the wind is blowing right to left, then one would expect to have to use Right Rudder to compensate.

BUT for quite some time now (in both Single and MultiPlayer), we have had to use the Left Rudder input to compensate.

This can be very confusing since ED refuses to create Wind Socks at airports, counting on Smoke Stack Smoke (which should work well enough IF there are smoke stacks close enough to see the direction the smoke is blowing) AND since the Physics of Wind vs Rudder Compensation is Bass-Aackwards. !!!!

 

Please Fix This.

Your aircraft is weathervaning into the wind. Wind from the right means the aircraft nose is vaning to the right. Correct crosswind technique for takeoff is aileron (stick) into the wind, rudder to keep nose aligned with the centerline.

I think ED could correct the wind direction "To" to make it "from" in the "briefing" menú, So You could take this correct wind before You fly a mission, and later input in the A10C's CDU.

If there is a mod that do that, why don't ED do It?

Your aircraft is weathervaning into the wind. Wind from the right means the aircraft nose is vaning to the right. Correct crosswind technique for takeoff is aileron (stick) into the wind, rudder to keep nose aligned with the centerline.

Uh .. ya ... I know.

The problem I was experiencing (which may or may not still exist ... I haven't flown the Mustang or much else Online since) is that the OPPOSITE Corrections were required.

The wind coming from the right, causing weather-vaning the nose to the LEFT.

Rather than pushing the rudder towards the oncoming direction, you would have to use the opposite rudder.

Eg .. smoke blowing right to left SHOULD require Right Rudder to compensate. But for the longest time, we would have to use Left Rudder which made/makes no sense.

But I like I said, I have no idea if it still exists because I haven't been flying (online or off) much lately. Stuff like that which started after an update (that presumably had nothing to do with wind direction but ultimately ended up affecting it anyway) made me have to take a break.

Uh .. ya ... I know.

The problem I was experiencing (which may or may not still exist ... I haven't flown the Mustang or much else Online since) is that the OPPOSITE Corrections were required.

 

The wind coming from the right, causing weather-vaning the nose to the LEFT.

Wind FROM the right, strikes the tail fin, causing the nose to weather vane to the RIGHT, into the wind.

Rather than pushing the rudder towards the oncoming direction, you would have to use the opposite rudder.

On approach you'd use the crab into the crosswind to compensate for the RIGHT to LEFT crosswind drift.

On/near touchdown, you'd use LEFT rudder to straighten up and a little RIGHT HAND bank to reduce crosswind drift.

Upwind Aileron, Opposite Rudder = RH Aileron, LH Rudder for a RIGHT to LEFT crosswind.

Eg .. smoke blowing right to left SHOULD require Right Rudder to compensate. But for the longest time, we would have to use Left Rudder which made/makes no sense.

See the above diagram - wind blowing right to left requires LEFT rudder.

But I like I said, I have no idea if it still exists because I haven't been flying (online or off) much lately. Stuff like that which started after an update (that presumably had nothing to do with wind direction but ultimately ended up affecting it anyway) made me have to take a break.

I don't fly the Mustang very much, but taxiing/landing the L-39 requires opposite rudder to stop the nose weather-vaning INTO a crosswind.

Edit: IIRC, there was a debate about how the Mustang behaved in the landing 'roundout' in crosswinds (perhaps due to the interaction of prop wash, engine torque and ground effect modelling). However, AFAIK the Mustang's taxi and landing is otherwise normal and as I describe.

You know what ?

I don't even give a damn any more.

It has been a while since I have been in any aircraft to remember the exact motions.

But all I can say is IT WAS ALL BACKWARDS.

Never mind anything else I have said here.

I was not the only one noticing the problem. EVERYONE that was on the same server at the same time, during the same patch/build .. experienced the same thing.

The direction we SHOULD Have had to make corrections was OPPOSITE that which it should have been.

So I'm just telling you ... IT WAS ALL WRONG at the time and may well have already been corrected.

I don't really care.

Please everybody ... MOVE ON. Nothing going on here !