Would it be possible to improve the ATIS code so we would hear, for example, landing and departing runways 27L and 27R..presently RC only identifies one runway no matter how many are active...

Would it be possible to improve the ATIS code so we would hear, for example, landing and departing runways 27L and 27R..presently RC only identifies one runway no matter how many are active...

already done in v5

Read my mind pal..thanks!! Was a wee bit unrealistic to hear "Landing and departing 27L" at EGLL...

Read my mind pal..thanks!! Was a wee bit unrealistic to hear "Landing and departing 27L" at EGLL...

might be unrealistic, but even in v5, if the ai ARE landing and departing 27L, ATIS will report it that way. i call them the way i see them. :-)

Just as a suggestion, what our ATIS does here in Honolulu (in real life) is say, "Landing and departing Runway 4 and 8." For us this means 4L, 4R, 8L, and 8R are in use. Also at Kalaeloa (PHJR), if they're using say 22L and 22R, the ATIS will simply say, "Landing and departing Runway 22". I don't know what it's like in the rest of the US (or abroad for that matter) but maybe if you have parallel runways, just put the number and omit the left and/or right to indicate both are in use. That way you don't have to have ATIS saying "Runway 4L, Runway 4R, Runway 8L, and Runway 8R in use". I mean here we already have an ATIS that's a minute thirty seconds long; literally.Also, at HNL we have a synthetic voice while the other airports have the controller on duty record the ATIS. Maybe the Class B airports in RC could use the synthetic voice for authenticity. And I know this is over kill for realism but what about LAHSO?And just as a bit of local knowledge. We keep using 4 and 8 at HNL as much as possible. That means that the tailwind component has to be 10kts or greater before ATC will turn the airport around (go to using 22 and 26). For us GA folks, if it's slow or we're lucky, we can request a headwind departure but that doesn't happen very often.

All these questions about RCv5....does this mean it's close to' release?

All these questions about RCv5....does this mean it's close to' release?

Definitely not. That is why suggestions are important.You will know we are getting near the fine tuning stage when we place an all call for volunteers to do phrase voice recording. At that point "phraseology" will mostly be frozen.Our language (and procedures) is determined by our ATC Controller division of our beta team which includes current or recently retired ATC controllers. We also use input from our beta team r/w pilots both airliner and general aviation private and commercial plus our sim pilots. We have ICAO and FAA jurisdiction participants and our language makes that distinction based on where your aircraft is.The language is parsed down into scripts and then common generic and specific phrases. At some point the phrases will be frozen and only script changes using those existing phrases will be allowed in the final language tuning.User input is always appreciated and will be evaluated. We also use the closest voice accent we have available for the region.We'll also have to look at in regard to runways where operations are split among multiple active runways. That gets complex because of AI behavior frequently not following airport design.I don't know if it will make it into RCv5 version one but the comments in this thread make me think we might use a different ATIS broadcast for departure and arrival that applies to split operation where one runway is departure only and another is arrival only when so designated. (I can already hear the groans from j.d. :) ).We can't satisfy all in order to get the product out the door but the most significant and some not so significant protocols will make it into V5.I don't want to scare any volunteers off but I can tell you that as of recently each controller voice has 3,122 phrases and each pilot/copilot has 3,013 at the current stage. By contrast an RC4 controller has 1,917 and pilot has 1,796. This includes airline and some airport names. The close proximity in numbers is because of pilot acks repeating many ATC commands though not all as we have been told. It has been our policy that each volunteer records a set of controller and a set of pilot voices is they are willing to do it.Subs is in charge of coordinating all the audio stuff. Most of the phrases are one or two word items and a some are consistent multiple word phrases such as used in ATIS and clearances. A few are longer such as the current "NOTAM" controller caution advisory about obstacle clearance.For the volunteers and our audio processing volunteers that alone will be a tedious lengthy task to clean up the recorded phrases and then adjust them for volume, "radio-izing" them, etc.So there will be lots of time when that starts to before release.