DCS Normandy 2.0 - ATC

[TBarina]

Is it me or the ATC in DCS Normandy 2.0 is not properly heading the player to final? I have tested it in a simple mission asking to High Halden for Vectors to final but it doesn't help me to find the airport. It becomes critical in low visibility conditions.
I've tried with "Inbound" also.

What am I doing wrong?

[MAXsenna]

A short track is probably helpful.

Sent from my SM-A536B using Tapatalk

[TBarina]

Hi, I've setup a mission where 2 P51-D are coming back. Radio available allows to tune to different airport (High Halden, Headcorn and Chailey: channels B, C and D respectively).

If I declare INBOUND to Chailey I receive proper heading to final (273 for landing to runway 15).

If I decalre INBOUND To HeadCorn it seems that i receive proper heading to final (334 for 15nm) (see picture). But I'd told to expect runway 28.
The problem here is that if I'm lost when I reach final IP I turn to M289° and fly to west insted to east. 

If I declare INBOUD do HighHalden I'm told to expect runway 11 but in low visibility I'm vectored to points that are not properly aligned to final.

It seems like airports with two runways are not managed properly.

I know that ATC is poor but I would expect to be able to be vectored properly in case of poor visibility.

Thanks.null

 

TB P-51D - RTB.miz

[TBarina]

I've added some wind from different directions (lastly 10 kts Meteo 276°) and it seems like ATC properly changes the IAF in accordance with wind directions.
Theoretically we are vectored to proper IAF.
The problem is that when declaring INBOUND to Headcorn ATC reports to expect opposite runway : runway 10 when wind 276° Meteo and 280 when wind from 100°.

IMHO it's bug in the INBOUND response that names the opposite runway as the active one (for which it provides proper IAF).

Seems like this bug only affects Headcorn airfield (that's what I've discovered so far)

BTW: Headcorn is RAF Lashenden as stated here:

 

 

Edited May 5 by TBarina