So I have noticed a little quirk with VoxATC that is a bit annoying.

 

Sometimes it is spot on and sometimes it is so off the mark that it has almost killed my virtual plane.

 

One thing it seems to get consistently wrong is the altimeter settings while on the ground.    You tune into the ATIS and the green ticker starts scrolling across the top and the ticker will say Altimeter 30.08 but VoxATC will say "Altimeter 29.96" (or any number of numbers that don't match the ATIS green strip).   If you have FSX ATC turned on and listen to their ATIS read back at the same time as VoxATC, FSX ALWAYS gets the Altimeter right on the strip but VoxATC is hit and miss.    As the METAR data is all coming in from the exact same place, why does VoxATC have problems getting this right?

 

VoxATC is also bad at wind directions.    Twice now, while my Avilasoft EFB has said  "Winds favor a 22" departure" and I create my flight plan to depart on Runway 22 (El Paso International in this example), I've pushed back from the gate and asked for taxi to the active and VoxATC is like, "Taxi to runway 4 via blahblahblah"    I am like @_@     But.. but... ALL the airport traffic is taxing to runway 22... why do you want me to taxi to the exact opposite end of the runway you daffy *(%&@*%& controller!?    Are you trying to kill me!?

 

It has done this at several other airports.    I file a flight plan with departures based on the wind direction being fed in by NOAA data and it gives me the wrong damn runway.    Don't get me started on a STAR approach in which it wants to take me 50 miles out of the pattern to sequence me.   The last several airport approaches I've had to disable VoxATC on the approach because the controller is giving me crazy instructions that I refuse to follow and the AI controller won't shutup.

 

I love VoxATC but the wrong altimeter and wrong runways are annoying.  Anyone found a work around this or know why it is doing this in the first place?     I use FS Passengers X with all procedures turned on and this incorrect Altimeter settings cost me points on my final score 50% of the time.

 

 

 

 

I totally agree, sometimes VoxATC tried to murder me..

 

I have proof !...

 

 

 

Despite of this near miss incidents, 95% of the time VoxAtc did guided me safely through the airspace.

While I have had planes taxi through my tail section while I was calling for clearance, I have never encountered something as drastic as posted in the videos above. I would like to suggest if I may that the next time you see this kind of behavior you open task manager and check the processes tab (If you have not already).

 

I have been doing a lot of reading in the forums lately and seen quite a few problems that could be explained by two VoxATC Server processes running at the same time. Two servers running simultaneously is something that happens to me every time FSX Crashes while VoxATC is running (Enabled). When FSX crashes VoxATC is not aware of the flight simulator closing since it was an abnormal shutdown. Upon restarting FSX, the VoxATC panel is not aware of the already running server process and starts a new one.

 

If you couple that with the fact that VoxATC generates and controls its own AI Traffic you can end up with two sets of traffic fighting over the same airport. And then it gets really interesting. VoxATC takes snapshots of the weather METAR and uses them for "as long as it feels like". This is why people who use weather updates from programs like REX (like I do) find the AWOS reports to often times be inaccurate.

 

For example if I start FSX, turn on VoxATC and tune to the AWOS frequency before REX injects the current weather, the snapshot that VoxATC has and is repeating to me is not the same as what FSX has for weather. I'm not sure how to get VoxATC to re-read the METAR from FSX but I do know that just flipping off the frequency and back again does not work. If it were me... I would call it a bug and change the code to update the METAR in VoxATC at the beginning of every loop of the "transmission".

 

At any rate I just wanted to share my thoughts and see if it helps. if you do find that you have two processes running you can turn off the current one using the disable button from within FSX and then close the other one with task manager. After that just hit the enable buttim fron withing FSX to fire a clean copy back up.

 

May your simulator flights be blessed with cloudy skies server wind sheering engine failures and damaged landing gear... and may your real flights be blessed with none of them.

 

Bao

 

 

At any rate I just wanted to share my thoughts and see if it helps. if you do find that you have two processes running you can turn off the current one using the disable button from within FSX and then close the other one with task manager. After that just hit the enable buttim fron withing FSX to fire a clean copy back up.

 

You make lota sense there, will look out for the double processes situation. Thanks.

Another incident recorded weeks ago that was probably a double processes situation. Slowly I learn how to anticipate the AI traffic to avoid disaster.