This may be one of those "can't see the forest for the trees" deals, but having gone through a whole lot of posts I'm unable to find an answer for my issue.
First, love the plane, but I'm at a loss on how to hear the COM2 radio. It's in aircraft.cfg as being available, just not seeing how to switch to it on the panel. All the files I downloaded are for the 73F, so I'm as sure as I can be that that's not the issue.
Post by aerofoto - HJG Admin on May 9, 2021 1:24:57 GMT
The RADIO STACK in each of our DC-8 panels is identical and "pretty simple/basic" in respect of its user friendliness .
Command it into view using the "RDO" icon located at the bottom left of each panel and among other sub panel view selection icons .... OR .... use keyboard commands "SHIFT+2" .... both options open/close the RADIO STACK in each DC-8 panel.
To adjust either COMM1 or COMM2 radio frequencies one must left mouse click at the left upper and lower or right upper and lower sides of the radio frequency display window in order to adjust either the frequency prefix or suffix accordingly.
This's all covered within our forum based online DC-8 manual.
Below I've copied & pasted the RADIO STACK section of this manual .... note the information concerning both COMM1 and COMM2 radios ....
DC-8 SHIP ONE 1958 - RADIO STACK
The Radio Stack sub panel can be activated/deactivated using either the "RDO" labelled sub panel view selector switch, located within the extreme lower center middle section of the Main Panel (below the DME1 gauge) .... or using SHIFT + 2 keyboard commands. The Radio Stack features all of the elements described below and which function as follows ....
- The VHF NAV1/VHF NAV2 radios are located within the upper and center left sections of the Radio Stack sub panel .... left mouse clicking, at 2 separate vertical points (+ or - respectively), below the extreme left side of either VHF NAV1/VHF NAV2 radio frequency display window cycles the displayed 3-digit radio frequency prefix .... left mouse clicking, at 2 vertical separate points (+ or - respectively), below the extreme right side of either VHF NAV1/VHF NAV2 radio frequency display window cycles the displayed 2-digit radio frequency suffix.
- The ADF1/ADF2 radios are located within lower and center left sections of the Radio Stack sub panel .... left mouse clicking, at 2 separate vertical points (- or + respectively), below each of the digits composing either ADF1/ADF2 radio frequencies cycles the 3-digit frequency displayed within each ADF frequency display window.
The VHF COMM1/VHF COMM2 radios are located within the upper and center right sections of the Radio Stack sub panel .... left mouse clicking, at 2 separate vertical points (+ or - respectively), below the extreme left side of either VHF COMM1/VHF COMM2 radio frequency display window cycles the displayed 3-digit radio frequency prefix .... left mouse clicking, at 2 separate vertical points (+ or - respectively), below the extreme right side of either VHF COMM1/VHF COMM2 radio frequency display window cycles the displayed 2-digit radio frequency suffix.
So long as it's "correctly tuned to any FS supplied COMM radio frequency" .... and so long as ATC/COMM's etc option is activated within FS too .... then you should be be able to hear whatever you're tuned to.
The RADIO STACK is "ON" by default (it doesn't need being selected "ON") .... and remains "ON" provided at least 1 engine is running. During any engines "OFF" situation the RADIO stack will lose power completely after around 3 to 5 minutes (unless one uses Pete DOWSON's FSUIPC module and has the "EXTEND BATTERY LIFE" option enabled and which then provides unlimited duration battery power) .... and won't be useable again until the engines are started and running. These should be it's only limitations
If you've missed or are otherwise unfamiliar with our DC-8 manual then use the following link ....
I guess I could've been clearer what I was asking about. I know how to get the radio sub-panel up on the screen and how to tune, but what I should've made clearer was how to switch between COM1 and COM2. In other words, if I'm listening to Approach on COM1 but want to briefly switch to COM2 to pick up ATIS info, can I do that? Usually there are COM1, COM2, BOTH buttons on a radio stack. If there are and I'm just not seeing them, find something suitable to thump me upside my head.
If you're saying both radios are listenable at the same time then I'm really confused because I flew into an airport where COM1 was on the Tower freq and COM2 was on ATIS. Never heard ATIS audio until I switched COM1 to that freq.
Post by aerofoto - HJG Admin on May 10, 2021 0:38:00 GMT
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.
First, this is why I like this forum. You ask a question, you get an answer. Not in a week but right away. You actually take the time to load up a plane to see what a user is having trouble with. Just wanted you to know it's appreciated out here in the world.
Now with that out of the way, after I wrote last time and because I sometimes am too lazy to change how I do things, I already did basically what you suggested. I modified the panel.cfg to use the 737 radio stack and adjusted the [radios] section of aircraft.cfg to allow frequency standby.
I know it's not how the panel was so meticulously designed, but I like it this way. You know the saying about old dogs and new tricks.
Post by aerofoto - HJG Admin on May 11, 2021 3:33:10 GMT
Thanks for that George
One of many reasons why I go (try to at least .... subject to a zillion other real world things going on around me at any one time) to the extent of not only replying, but also, replying the way I often do is because I only too well remenber those days when I first entered FS (during the very late 80's) .... a time when I knew "NOTHING AT ALL" .... but .... still had a concept in mind of how things should be and work, but, not being able to do anything about it ("BLOODY FRUSTRATING" to say the very least) simply because I didn't, then, know how to .... until I progressively "learned" (and in doing so also learned that "understanding isn't really a destination, but rather, it's a constant state of travel/progress, to the extent we never know everything .... regardless how much we all understand"). Where possible (and sometimes it's not possible) I do try to put myself in other peoples shoes .... by virtue of the fact I appreciate they may well be in the very same situation I was once in myself all those years ago.
For it all to work though .... and for people to be able to benefit too .... requires one side being able to communicate clearly and the other side to be able to listen intently (some people can't be helped .... of course .... but .... that "DOES NOT" apply to you). Not everyone can do such .... but .... you've done so quite well .... and as such I hope you've benefitted .... as I hope others may also.
BTW .... I wasn't actually advocating importing the Radio Stack from another panel to our DC-8 panels. I was really just making comparisons between the functionality of our current DC-8 panel Radios and that of the default MS CESSNA, but, if you've done it .... then you've done it .... and if it's working successfully for you then better still. I don't think what you've done will hurt anything else associated with the functionalities of our DC-8 panels, but, must advise we won't be able to provide support "for that particular edit" as the result of it being a non-standard/non-HJG-endorsed edit. I'm sure you'll be fine though
FYI .... I've now (today) updated the DC-8 manual .... except for it's supporting imagery which will have to wait a bit longer.
I totally get what you're saying, Mark. If I break it, it's my problem. I know probably the really "right" thing to do is to always make a backup of a cfg file, but I typically just remark out the line(s) I'm changing with a ";" so when something doesn't work, it's much easier for me to find what I broke and can quickly get back to what was there to begin with.
I've been playing with config files for a long time and am fairly comfortable with certain sections but just because some change worked on Plane A, that's no guarantee it'll work on Plane B. If it doesn't, I just put it back to how it was and get on with my life. I like to learn but not at the cost of banging my head on the desk. Besides, it hurts and it'll just ruin the desk.