The reason I provided a more-or-less full description in regard to the basic Radio Stack functions is simply to aid more folk than whom ever ask any question .... since a full description usually always better serves those whom might lack confidence to log-in and post but are still in need of assistance
No problem though I've just had a closer look at this for you.
I need to say I "DO NOT" ever use the FS generated ATC .... by virtue of the fact I simply "DO NOT" like it.
I could get ATIS information by manually tuning COMM1 to the appropriate frequency for the airport at which I performed my check/s .... the default KSEA in this particular case, but, couldn't get it to work via COMM2.
I'd previously "assumed" ATIS dialogue could be engaged by tuning either COMM1 or COMM2 frequencies within this particular Radio Stack, but, it seems this "IS NOT" the case. This's obviously "a basic limitation" in regard to the way Marco designed the COMMS functionalities of our DC-8 panel/s Radio Stack (which even I've been unaware of until now) .... and which will also similarly apply to our CV-880 and CV-990 panel/s too since each uses the very same Radio Stack.
Also this particular Radio Stack "DOES NOT" feature tabs to enable switching the unit "ON/OFF or selecting between active "COMM1/2" frequencies either whereas the default FS CESSNA Radio Stack does .... along with featuring a "BOTH" selection tab as well and which I think is also COMM's related.
A limitation to the DC-8 Radio Stack we've always been aware of is it's not equipped with either NAV1/2 ID or MKR beacon selector tabs either. If one wants these items to function then one needs to load the default MS CESSNA "first" ..... then .... manually engage each of these items on the CESSNA Radio Stack .... then .... select one's DC-8 of choice in order for these items to function.
Despite not being necessary for some of our panel offerings the default FS CESSNA should always be temporarily loaded first and before selecting any of our DC-8's (CV-880's and CV-990's) anyway. This's in order to ensure all panel features are set to their default FS configuration/s. The default FS CESSNA should also be loaded whenever changing from any DC-8 (CV-880 and CV-990) to another aircraft type within the very same FS session.
ANYWAY .... to get back to the point of the DC-8 Radio Stack COMM1/2 functionalities in particular Using our DC-8 version Radio Stack it seems "ALL" ATC related COMM's function via the "FS ATC dialogue facility" and which, when engaged, auto-generates both ATC/ATIS dialogue ....
via the "COMM1 Radio" only.- Use the keyboard "TILDE" tab in order to open/close the FS ATC dialogue box.
- Identify one's intent from listed and numbered items/options within the FS ATC dialogue box.
- Use keyboard number tabs in accordance with the corresponding/desired ATC option/intent in order to auto-engage the related communication dialogue.Even I learned something "NEW" today
.... so I'll further update the Radio Stack sections of our DC-8 manual with this information "once I have time to do so"
As I said at the start of this reply .... I "NEVER" use the FS generated ATC functions, BUT, did use it today (in the process performing a TO, full climb to altitude, cruise, descent, and then landing), solely for the purpose of this check and reply. In doing so I noted it seems to work fine/acceptably (as described), but again,
only through COMM1 and options selected per the FS ATC dialogue box .... therefore suggesting whilst COMM2 remains selectable it doesn't actually function in accordance with any ATC or ATIS dialogue.
This may be evidence (I don't know .... I'm only speculating) of plans possibly having originally been made to provide a more fully functional Radio Stack in the future and which have obviously not since been proceeded with.
It's all "pretty basic" .... I appreciate .... but .... that's the way ATC/ATIS via this particular Radio Stack seems to work .... subject to whatever FS imposed limitation/s might apply to it.
I further suspect (though haven't checked) that FS generated ATC will probably best function in regard to an FS Flight Plan having first being compiled, saved, and then executed .... and once again subject to whatever FS limitation/s might apply.
Mark C
AKL/NZ