[REPORTED] Wind or ATC 180 degrees out.

[VH-Kestrel]

When flying Instrument approaches i found something was 180 degrees out. I had a mission linked below, where the wind is set to 040 in the mission editor. In game I can see a smoke stack with the wind blowing heading 040, but when i call ATC for start up they say wind FROM 220 and then give me taxi to runway 04 which gives me a tailwind take off, this also means that when landing only the ADF and RSBN landing signal is working on runway 04 to get a tailwind landing as well. I tested wind the wind set to 220 and everything resverses to give a tailwind.

 

https://dl.dropboxusercontent.com/u/25510491/L39%20nav.miz

Edited October 9, 2015 by BIGNEWY

[Gierasimov]

Wind velocity

 

To test that I used Kobuleti. In mission editor I set wind to 250 at 2 kts.

Starting from the ramp I am cleared to taxi to RWY 7.

When approaching, vector to RWY 7 is given again. On final, wind zero – seven – zero is reported (headwind). Which is correct. ATC or ATIS gives you the wind velocity, velocity is a vector which simply means that it is defined by two parameters, speed and direction. Wind direction is always given as a radial measure in degrees stating the direction from which the wind is blowing. In another words Wind zero-seven zero is a wind direction from azimuth 070 degrees magnetic.

So, if your heading is 070 and wind direction in ME is 250, the wind call out by ATC will be exactly 180 degrees opposite.

 

What I will do though, I will check the same with Krymsk base, as with the wind 040 you should not be assigned RWY 04 for take - off.

[IvanK]

Agree have seen the same thing Wind entry in the ME seems to require where the wind is blowing TO to get a logical result in game.

[Gierasimov]

Known already?

 

So, it seems that I found two problems with Krymsk air base.

I set wind direction 220 to have spot on headwind for TO and landing on RWY 04.

First, I was given clearance to taxi to RWY 22 (wrong, as it would be tailwind operations).

So I actually rolled to RWY 04 and was cleared to take off.

When flying a mission, another A-10C was supposed to take off for another sortie, AI is cleared RWY 22 as well but then stopped at the first taxi way intersection.

After the mission, I was vectored for RWY 22 approach, which I ignored. When on final, I was cleared to land RWY 22 although I was on final to 04 – so not only ATC uses wrong RWY (downwind) but also is completely unaware of what is happening.

 

 

If you look at AI section of bug reports there is actually few issues reported relating to both AI taxi logic as well as downwind operations (which was acknowledged as a bug).

Edited October 9, 2015 by Gierasimov

[BIGNEWY]

This issue has been reported. thanks

[Gierasimov]

Solved with Hot Fix 2 for 1.5 as far as I know.