• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA ADE Compile Issue?

Messages
29
Country
unitedstates
Hello Everyone,

Need some advise from the experts here. I don't know if this is an ADE compile issue or an issue with editvoicepack. I am using Fly Tampa's Kai Tak. A known issue with the scenery is when speaking with atc, FSX does not use "Kai Tak" in its phraseology ie. Kai Tak Tower, Kai Tak Ground, Kai Tak approach, etc. Easy enough to fix using EVP which Martin of Fly Tampa suggested when I first purchased the scenery a couple of years ago. I have the necessary agent names to add "Kai Tak" to FSX and have done so in the past without incident. However, this time I decided to just add an ICAO modification "VHHX Kai Tak" and see if EVP would write the agent names correctly to FSX. I had to modify the Kai Tak afcad comm list with ADE and replace the unique identifiers with "Kai Tak" All worked well and the usual ATC comms were present. The only issue was that every AI ship used in the scenery was calling Kai Tak for IFR clearance. While amusing, not the desired result.
I learned yesterday from another forum post the AI ship issue is the reason Fly Tampa used the unique identifiers in the comm list. So, I went about correcting the issue by removing the ICAO mod, using the original identifiers listed in the comms section of the afcad and using the "agent names" modifications I have. Recompiled the airport and all worked well as I expected. Kai Tak was restored into ATC communications and the AI ships are not being heard. Now for the issue.....I noticed the frequency being used for departure is not what is listed in the comms section of the afcad. ATC is using the approach frequency while saying "departure" All the other frequencies are being used correctly. I am wondering if this is an EVP issue as to why ATC is not using the correct frequency, or if I did not perform a function correctly with ADE. The identifier for departure is correct. I have also checked the surrounding area to make sure the departure frequency isn't being used elsewhere. Why wouldn't FSX use the correct frequency??
I apologize for the lengthy post but I wanted to give you some background info vs just asking why the wrong frequency is being used. I have attached a screen of the comms list for the afcad. Thanks for you time.

Regards,
Rob


ktc_zps61deb818.jpg
 
Hello Everyone,

snip-----------------

Now for the issue.....I noticed the frequency being used for departure is not what is listed in the comms section of the afcad. ATC is using the approach frequency while saying "departure" All the other frequencies are being used correctly. I am wondering if this is an EVP issue as to why ATC is not using the correct frequency, or if I did not perform a function correctly with ADE. The identifier for departure is correct. I have also checked the surrounding area to make sure the departure frequency isn't being used elsewhere. Why wouldn't FSX use the correct frequency??
I apologize for the lengthy post but I wanted to give you some background info vs just asking why the wrong frequency is being used. I have attached a screen of the comms list for the afcad. Thanks for you time.
Regards,
Rob

Many frequencies listed does not mean FS will use them. You can see this at airports with multiple Tower, Ground, App, Dep, etc type freq's.

The ATC approach and departure area of Hong Kong in FS is controlled by VHHH since VHHX never had those freq's assigned. The primary Appr and Dep freq is 119.1 for VHHH and the surrounding sector area.

It appears that there is only one channel in FS assigned for the Appr and Dep of the Hong Kong VHHH area which includes VHHX, VHSK, VMMC and ZGSZ . If you change the 119.1 Appr freq at VHHX to something else it will also by default be the Departure freq based on the assigned single channel.
 
Last edited:
Hi Jim,

Thanks for the reply. This is new to me. So even though we assign frequencies to an afcad via the comms list there is no guarantee that FSX will use those exact frequencies?? I was under the impression this was set in stone so to speak like assigning a library object to one of your airport projects. Prior to adding the new agent names to the voice pack to restore "Kai Tak" to the ATC communications, I did load up the stock afcad for VHHH and change any conflicting radio frequencies. I have never checked VHHH to see if ATC is using the new frequencies I assigned. I assumed all was well due to not hearing any VHHH ATC traffic while at VHHX. Prior to changing the VHHH frequencies I was receiving VHHH ATIS and I believe Ground while at VHHX if I remember correctly.
One thing I tried today was swapping the approach and departure freq. Since nothing I was doing was convincing FSX to use the correct departure freq. I changed the approach/departure freq. in the comms list and recompiled the airport. In the comms list I changed departure to 119.100 which FSX was using anyway, and I changed approach from 119.100 to 128.500. Much to my surprise that worked. Approach and departure had their separate freq. albeit backwards from the Fly Tampa afcad. If I am understanding what you're saying about the one channel for the Hong Kong area why did that work?? Or did that change something at VHHH as well??
How do you find out how many channels are in the area?? Is it a matter of checking the afcads for the airports in the area to see if they have the same freq. or is there another "trick" to it?? Is there a way to add additional channels to an area to enable one to have separate comms?? Thanks for your time.

Regards,
Rob
 
Last edited:
In the comms list I changed departure to 119.100 which FSX was using anyway, and I changed approach from 119.100 to 128.500. Much to my surprise that worked. Approach and departure had their separate freq.

Hi Rob

I changed my VHHX the same as you. My findings do not agree with yours. When I reversed 119.1 and 128.5 that made 128.5 the primary channel for both Approach and Departure. At no time during a IFR departure from VHHX, the approach to VHHX, a missed approach from VHHX was I given 119.1 since it was no longer the primary channel. I was given (based on the 20 NM rule distance) the VHHH departure freq of 119.1 (when vectored within range) but that is a VHHH channel and not a VHHX channel.

You could try and add another channel for VHHX so the secondary 128.5 is used. This is done with a Boundary for Com's as per the BGL Compiler SDK. However if you are satisfied with your results since I cannot replicate them I would leave it as is.

If you want to look at some research into Comm's this post might help.

http://www.fsdeveloper.com/forum/threads/setting-comms-arrival-approach-channel.19797/
 
Hi Jim,

Well, after reading your post I was ready to upload a screen of my separate app/dep freq. for Kai Tak and marvel at my success.............then FSX brought me painfully back to reality. My results were the same as yours. Last night when I swapped out the freq. I sat on the runway, hit the slew button and went straight up until the ATC window changed and advised to contact approach. Today, I attempted several IFR flights and had the same result as yourself. Both VHHH and VHHX use the same freq. for approach and departure. 128.5 for VHHX and in my case 119.05 for VHHH. I had changed the freq. to 119.05 for VHHH in the afcad to avoid a conflict with VHHX. A real surprise came from RCQC (Magong Airport). RCQC is an airport I reactivated in FSX as a base for all my retro AI to fly into VHHX. Approach and departure are the same freq. as well.
I obviously did something wrong last night to give me the erroneous result. After taking the time to test it today after reading your post, it was clear that there was no way I was going to have app/dep on separate channels. I apologize for jumping the gun and putting out bad info.
The link you posted was extremely interesting. I had no idea at the complexity of ATC in FSX. There are far more variables involved than I had imagined. So much for my "set it, and forget it" theory.
On post #9 of that thread you state " If you build a airport from scratch and add multiple approach/departure freqs then FS chooses the first one listed and disregards all others since the compiled XML cannot add itself to the freq boundary files that are coded by FS." If this is the case then why bother adding half a dozen app/dep freqs.?? Or, do the other channels get used at some point based upon the other variables like altitude, heading to the airport, distance, etc ??
Your post #15 was also interesting in that the sim can use an approach freq. from an entirely different airport from the one we are going to but still use the destination airports name in the ATC communications.
So, is it safe to say that the primary or active channel is the first one listed in the comms section of the afcad, and the only way to add additional active channels is to modify the "bvcf.bgl" file??
Thanks for your time Jim, lots of good info here.

Regards,
Rob
 
Back
Top