TBarina

12 months to solve! Very reactive...

It's even worse at High Halden or other two airstrips fields when asking direction to final or inbound. You are often directed to the opposite IAF instead to the the proper one according to the radio message inditecating the the runway number. Unfortunately, IMHO, ED is fully concentrated to release new modules and doesn't care for the bugs they leave behind. It's a great sim indeed and it would deserve greater respect and attention.

Anyone has had the chance to test?

Hi, make sure you use DCS’s Built-in “3 Camera” Setup This allows DCS to render three separate viewports (left, center, right) with proper angles and maintains vertical FOV more accurately. Go to ...Saved Games\DCS\Config\MonitorSetup Use or create a monitor lua configuration for a triple screen In DCS options: Set Aspect Ratio to your true value (5720/1080 ≈ 5.29:1) Set resolution to 5720x1080 Choose your custom monitor config Note: This increases GPU load significantly because DCS renders each camera view separately.

I've tested again and created a new mission with Spitfire coming from the south and the ability to contact both HighHalden and Headcord. I've tried to call HH first. I've given direction to IAF for runway 11. Message says RW 04 (it doen't exist ad HighHalden, if I'm not wrong). Where is this RW 04 coming from?| Besides, even if the intention was for runway 11 that would be the wrong one since the is wind from 285 at 20 kts). Then I aborted and contacted HeadCord. I was vectored west of the airport to IAF for RW 10. Controller said to expect RW 28 (BTW: not 27, there is no 27 at Headcorn). Theoretically this should be the right one since the wind is coming from 285 (Met.105°). But the IAF where I'm vectored to is at the opposite side and it's not the right IAF for RW 28. I cannot say it is working properly. For me it's messing up things. Not to talk of problems when there is no wind blowing. Please, let us know and take action with ED if you have power to. I'm available for further testing in case of need. TB Spitfire - RTB.miz

Has anyone else encountered the same problem? IMHO it's bug in the INBOUND response that names the opposite runway as the active one (for which, instead, it provides proper IAF).

Hi, https://discord.gg/QXySHjPj is not working (invalid or expired). Is there any other link?

Hi, thanks for your great work on ATC. Instructions explain that is necessary to include files in .miz It is about 35MB size per mission. Would it be possible to install files once in a common directory and use Symbolic Links inside the various .miz file that I would like to create?

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:

+1

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

I've been able to fix it by upgrading DCS-BIOS to the the lastest version. Now it works flawlessly.

I followed your instructions (BTW: I already knew that because I've already used same procedures for other panels from TekCreations). My device in on COM4. Unfortunately it doesn't seem to work even if DCS-BIOS is properily working. Is there anything I can do to fix it? null

The bridge lays on the rails and there is no room for the trains to pass under it! Also banks invade rails track. There abundant free room to move them back a little Is it possible to have it fixed? null

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?