Funny thing. I havent experience most of the problems peeps are stating here and some of them occur when you have managed to confuse the software.

. Also, not sure where VOX is getting its list of frequencies because some are wrong.

Vox doesn't have an airport Frequency repository of any kind, all the Frequencies that are used by Vox are from

the Scenery/AFCAD files you got installed in your FSX and/or the build in FSX AFCD files (in case you don't have an external scenery for an air port it would use the default FSX frequencies).

as you remember as part of the Installation there was an Indexer process that scans your FSX folder. essentially

what it does, it reads all your AFCAD files (those who hold among other navigation details the Airport frequencies) and based on your scenery.cfg file it will know also what to use

(that is why it is a wise thing to run the Indexer every time you add or remove a scenery in FSX).

The incorrect radio frequencies you experienced are due to old FSX frequencies or sceneries, if you would use the FSX built in ATC at the same location, you would see it would use the same frequencies.

it is not a Vox Issue but rather an FSX/old Scenery issue.

 

Next, I did IFR from/to Class E airports. Here's where it got weird. So VOX assume you've called Departure/Center over the telephone and got your clearance. Because all it told me once airborne was to contact center with current altitude and final altitude. which is fine but I got no squawk code.

that could be a fluke or if you did not Install the Navigraph Airac cycle (AIRAC) LEVEL-D version and Attach it in the Vox setting.

Vox needs to know would how to connect the Scenery/AFCAD details to the airways, DEP/APP in use.

another reason could be, is if at that particular area/airport (AFCADs) were lacking airspace route data (common at some locations in FSX default

routing table).

 

So I use those two voices for controllers and I speed them up, just a little to act like the real world. That's a really great feature! Would be nice if you could separate the speed for controllers and pilots.

 

Actually you can, you can control the Volume and speed of every Voice individually, every voice is assigned either to a controller or

to an AI, FO is also possible (technically you could assign a single voice to all, but that would confuse you who is who).

that means you have that granularity of voice settings.

for example I speed up all my AI voices but not the controller ones.

 

BTW - have you D/L and Installed the VoxPOP voice packs?

those are great for your AI (could be used for controllers also if you wish) they got the static radio additive to it, etc. and it is free.

http://www.voxatc.co...ice.aspx/VoxPop

BTW - have you D/L and Installed the VoxPOP voice packs?

those are great for your AI (could be used for controllers also if you wish) they got the static radio additive to it, etc. and it is free.

 

Thanks for the tip...just downloaded and installed...like you said they're free and they sound pretty good...I did the recommend setup..and I like the static filter for pilots...cuts down on my cost...yeah.

 

Here's a weird one...I landed at TNCM - and I normally just like to set and watch traffic for awhile...so I need to keep VOX enable. Well, this is funny, first a DHL 737 hits the water and slowly sinks head first...then a twin had the hardest landing I've ever seen. It bounced about six times and it was like a see saw bounce...very funny...to watch that is.

 

Oh...I figured out that you need to request (0) zero to get permission to cross a runway and to back taxi...very very cool.

 

-Ray

yes, I have noticed the AI sometimes do crazy stuff, but I don't really care as most of the time I am busy Taxi/Flying than watching them.

the only time I need really the AI is during Taxi / Before take off & before landing (waiting in the queue). there you usually

don't see those crazy stuff.