Thanks to folks here, I have been successful in modifying afcads to update my home airports (KUAO) current frequencies and control tower.  Everything works great except after taking off I get directed to contact a fictitious Oceanic center rather than Seattle center as I should.  When I use my modified afcad, I am instructed to tune to oceanic center really close the the airport. When I use the stock afcad, I get told to tune to Seattle center about five miles away from KUAO.  So, I’m thinking I need to define an additional frequency (I tried center but no joy) or a radius around the airport. 

Can someone point me in the right direction?

here is my modified afcad comm list 

https://drive.google.com/open?id=13KjPhaQF5B9T3UdEcIFtwBMIB6zMKpu9

Edited February 25, 20188 yr by 503Kento

VOXATC gets its ARTCC/FIR boundaries and comm frequencies from the file bvcf.bgl, which is located in the folder:

<drive>:\Program Files\Lockheed Martin\Prepar3D v4\Scenery\World\scenery

The only way to update this worldwide file is to convert it XML, edit it with a text editor and then recompile it with BGLComp.exe. fsaerodata supplies an updated version and that's a much easier route for the average user who wants accurate Center comm frequencies. Although some stock airports have Center comm frequencies in their list, it's unclear whether VOXATC does anything with that information except to fail, if one changes the comm frequency away from the stock value contained in bvcf.bgl. This probably is caused by an inconsistent frequency value between the ADE file and bvcf.bgl. Oceanic Center is the catchall phrase one hears when there is either a missing or inconsistent Center frequency. This is because there may not be a Center frequency over the open ocean, so the default phrase is used.

Edited February 25, 20188 yr by jabloomf1230

Thanks, I was pretty sure you would have the answer.  I’ll check our fsaerodata. 

It's not like I didn't go down the same path that you did at one point. There are two types of AI. The first is forgiving and has a sense of humor, like Alexa on Amazon's Echo personal assistants. The second is like the gruff,  all logic HAL 9000 in the movie 2001:A Space Odyssey. VOXATC is much closer in personality to the latter.

8 hours ago, jabloomf1230 said:

It's not like I didn't go down the same path that you did at one point. There are two types of AI. The first is forgiving and has a sense of humor, like Alexa on Amazon's Echo personal assistants. The second is like the gruff,  all logic HAL 9000 in the movie 2001:A Space Odyssey. VOXATC is much closer in personality to the latter.

Jaboom, all I can say is LOL!.

Agreed, very funny! 

On 2/24/2018 at 10:57 PM, jabloomf1230 said:

VOXATC gets its ARTCC/FIR boundaries and comm frequencies from the file bvcf.bgl, which is located in the folder:

<drive>:\Program Files\Lockheed Martin\Prepar3D v4\Scenery\World\scenery

The only way to update this worldwide file is to convert it XML, edit it with a text editor and then recompile it with BGLComp.exe. fsaerodata supplies an updated version and that's a much easier route for the average user who wants accurate Center comm frequencies. Although some stock airports have Center comm frequencies in their list, it's unclear whether VOXATC does anything with that information except to fail, if one changes the comm frequency away from the stock value contained in bvcf.bgl. This probably is caused by an inconsistent frequency value between the ADE file and bvcf.bgl. Oceanic Center is the catchall phrase one hears when there is either a missing or inconsistent Center frequency. This is because there may not be a Center frequency over the open ocean, so the default phrase is used.

Jay, I finally got around to getting fsaerodata/navigraph but it did not resolve the Oceanic center issue near KUAO.  In fact, it seemed to overwrite my AFCAD mods as I went back to utopia radio for FSS.

did I configure something wrong?  I enabled fsaerodata with the latest airac and got Vox pointed to the level D data. 

Thanks,

Kent

fsaerodata does not automatically install its updated FIR/ARTCC file. Do this:

1. In the folder <drive>:\Program Files\Lockheed Martin\Prepar3D v4\Scenery\World\scenery rename the default file bcvf.bgl to bcvf.bgl.off .
2. In the folder C:\Users\<username>\Documents\fsAerodata Files\Navigation Data\Navaids find the file fsad_airspace_FIR.BGL  and copy it to <drive>:\Program Files\Lockheed Martin\Prepar3D v4\Scenery\World\scenery.
3. Rename fsad_airspace_FIR.BGL to bcvf.bgl.
4. Run the VOXATC Indexer.
5. Run Little NavMap and check to make sure that the ARTCC/FIR boundaries are updated.

Hmmm, we’ll i tried your manual airspace update and found the FSaerodata options screen allowing me to select airspace updates. Neither one solved the problem. 

Little Nav Map, default ATC and the default GPS all show the class D airspace surrounding KUAO.  VoxATC indexer was run multiple times but Vox is still telling me to tune to oceanic center while still inside KUAO airspace. 

Anything else I can look at or try?

Thanks

 

I'm fairly certain that adding a Center frequency to an airport just gets overridden by whatever is in bvcf.bgl. Looking with Little NavMap, the only airspaces at  KUAO are the Class D and the two Seattle ARTCC Horton sectors, one for 0-18,000' MSL (121.4) and one for 18,000-60,000' MSL (132.075). Are you seeing those ARTCC sectors with LNM? If not, the bcvf.bgl file is still the default file. Also, try deleting the Center frequency from your modded ADE file.

If I'm looking in the right place, I'm only seeing the Class D.  Below is what I see in LNM on the Airspaces tab. 

Before via FSAeroData "Enable Button"
  Airspace: Aurora State  Map
Controlled, IFR and VFR, ATC clearance required.
Type:
Class D
Min altitude:
0 ft MSL
Max altitude:
2,700 ft MSL

Scenery
FSAD_Navaids
C:\Users\Thor\Documents\fsAerodata Files\Navigation Data\Navaids\scenery\FSAD_airspace.BGL

After via file copy and rename
  Airspace: Aurora State  Map
Controlled, IFR and VFR, ATC clearance required.
Type:
Class D
Min altitude:
0 ft MSL
Max altitude:
2,700 ft MSL

Scenery
Default Terrain
F:\Lockheed Martin\Prepar3D v4\Scenery\World\scenery\bcvf.BGL

I'll try again without the Center frequency in my AFCAD

removing the center frequency had no effect.

44 minutes ago, 503Kento said:

FSAD_Navaids
C:\Users\Thor\Documents\fsAerodata Files\Navigation Data\Navaids\scenery\FSAD_airspace.BGL

That won't work. The ARTCC/FIR must be named bvcf.bgl and be located in ../scenery/world/scenery. Anywhere else it is ignored by VOXATC.

I messed you up by misspelling bvcf.bgl in one of the above posts.

9 hours ago, jabloomf1230 said:

That won't work. The ARTCC/FIR must be named bvcf.bgl and be located in ../scenery/world/scenery. Anywhere else it is ignored by VOXATC.

I messed you up by misspelling bvcf.bgl in one of the above posts.

Ok, I repeated the provided file copy/rename process and corrected the spelling.  So, now the airspace tab (with Navigraph turned off) looks like this:

  Airspace: Aurora State  Map

Controlled, IFR and VFR, ATC clearance required.

Type:

Class D

Min altitude:

0 ft MSL

Max altitude:

2,700 ft MSL

Scenery

Default Terrain

F:\Lockheed Martin\Prepar3D v4\Scenery\World\scenery\bvcf.bgl

I reran the VoxATC indexer but still get Oceanic center shortly after takeoff while still in the Class D airspace

What does the LNM map view look like with ARTCC airspaces active? Do you see the most recent Seattle Center frequencies or the ones from the default sim?