ATC Problems

[mytai01]

As I understand, the normal flow with ATC logic from a cold start on the ramp is request engine start, request taxi, request take-off. However, it seems helicopters have a problem when they hover taxi (in ground effect, below 20kts) or air taxi (below 100 feet, above 20kts) to the runway. It seems that the ATC logic flow becomes disrupted and thinks the helicopter has already taken-off and re-sets the ATC logic to the inbound state even if you're hovering short of the runway and want to request take-off, or it re-sets to the request engine start step if you set it down short of the departure runway. I even screwed the ATC logic up so badly that it was stuck on the request take-off step even though I was airborne and trying to contact another facility at another airport for approach instructions.:lol::megalol:

 

I'm thinking that ATC has to be it's own module to even have a prayer of being close to realistic. Not to mention, ATC is a little to a lot different from US ATC in different countries, so one would have to know the regional procedures for each geographical area for each geogrphical module in DCS World.

 

At the very least, add the helicopter departure/arrival procedures for non-movement areas (ramps/parking areas). Example, "Spear tree niner, departure/landing from/at the ramp will be at your own risk, use caution."

Edited January 25, 2016 by mytai01

[JUICE-AWG]

As I understand, the normal flow with ATC logic from a cold start on the ramp is request engine start, request taxi, request take-off. However, it seems helicopters have a problem when they hover taxi (in ground effect, below 20kts) or air taxi (below 100 feet, above 20kts) to the runway. It seems that the ATC logic flow becomes disrupted and thinks the helicopter has already taken-off and re-sets the ATC logic to the inbound state even if you're hovering short of the runway and want to request take-off, or it re-sets to the request engine start step if you set it down short of the departure runway. I even screwed the ATC logic up so badly that it was stuck on the request take-off step even though I was airborne and trying to contact another facility at another airport for approach instructions.:lol::megalol:

 

I'm thinking that ATC has to be it's own module to even have a prayer of being close to realistic. Not to mention, ATC is a little to a lot different from US ATC in different countries, so one would have to know the regional procedures for each geographical area for each geogrphical module in DCS World.

 

At the very least, add the helicopter departure/arrival procedures for non-movement areas (ramps/parking areas). Example, "Spear tree niner, departure/landing from/at the ramp will be at your own risk, use caution."

This is what I would love to see...

 

• Proper ATC protocols for Ground, Tower, Approach Control, Center, and Clearance Delivery with realistic radio affects and voices with full variance in character models beyond the previous practice of only using a few actors' voices.
  
• Traffic Advisories within the airspace to include restrictions, proximity alerts, and vectors around civilian and military traffic.
  
• Designation of taxiway/runway assignments, updates, and hold-short instructions. (The current system instructs landing clearances to Runways 21/03 without proper regard to Left or Right designations)
  
• Conversion from QFE standard to Altimeter settings and integration of ATIS information with Alpha designations such as "Nellis Information Sierra Current, 1915 Zulu as an example" with all normal ATIS information provided.
  

[tintifaxl]

A reworked ATC was (still is?) on the feature list of DCS World 2.0, so there is hope.

[mytai01]

This is what I would love to see...

 

• Proper ATC protocols for Ground, Tower, Approach Control, Center, and Clearance Delivery with realistic radio affects and voices with full variance in character models beyond the previous practice of only using a few actors' voices.
  
• Traffic Advisories within the airspace to include restrictions, proximity alerts, and vectors around civilian and military traffic.
  
• Designation of taxiway/runway assignments, updates, and hold-short instructions. (The current system instructs landing clearances to Runways 21/03 without proper regard to Left or Right designations)
  
• Conversion from QFE standard to Altimeter settings and integration of ATIS information with Alpha designations such as "Nellis Information Sierra Current, 1915 Zulu as an example" with all normal ATIS information provided.
  

 

You might need a server just just to handle the ATC part of DCS World...:thumbup: Since we're asking for the world, if you don't follow ATC instructions you get a Pilot Deviation, FSDO shows up to your house and takes your flight controllers away and bans you from the virtual skies for life!

Edited February 8, 2016 by mytai01

[Nealius]

Working active runway assignments would be nice too. Some fields like Tbilisi and Mozdok assign the same active regardless of wind conditions. Mozdok seems to be broken anyways since wind direction is always 180 degrees opposite of what you assign in the ME.

[JUICE-AWG]

You might need a server just just to handle the ATC part of DCS World...:thumbup: Since we're asking for the world, if you don't follow ATC instructions you get a Pilot Deviation, FSDO shows up to your house and takes your flight controllers away and bans you from the virtual skies for life!

 

Love it...my local FSDO office is my wife!