This is a hit and miss, because it works for me most of the time without a glitch. 

What kind of problem ?I have installed VoxATC several times without success. The same problem remains.

 

I fly in the French and Switzerland countries. Perhaps these countries are the problem ?

 

 

On 5/16/2017 at 1:58 PM, Branech said:

This is a hit and miss, because it works for me most of the time without a glitch. 

What kind of problem ?I have installed VoxATC several times without success. The same problem remains.

 

I fly in the French and Switzerland countries. Perhaps these countries are the problem ?

 

The only place I've noticed not working well for me has been at Aguadilla Airport in Puerto Rico. Then again, it could simply be the scenery, and not VoxATC. For the most part here in the US, I haven't had an issue.

 

Edited May 18, 20179 yr by specialist

So, Beta 7.3 - seems to be going backwards.

1.  Now I do not receive SID or STAR clearance but annoying vectors when departing/arriving - or clearance to first waypoint -  yes, my Navdata is up to date.

2.  My FO is still clipping transmissions when asked to change frequencies, usually the decimal digits,

3.  On finals FO keeps repeating the instruction to contact tower.  When you try to manually set the radio frequency, Vox changes it right back.

4.  Still no support for numeric alpha flight numbers, which are now very common in Europe.

All reported to the developer via the website....but no response.  With this kind of mentality to support issues I doubt I will find the money to upgrade, if/when it is finally released.

6.52 works fine for me!

 

Ken

Flight from Kansas City to Los Angeles, ATC is not providing proper descent and flight level constraints. By the time I get to LA, I'm way too high.

I'm not convinced  that the new terrain-aware logic in 7.3 is working  correctly all the time. Try changing the option  to "FALSE" in VASettings.xml. 

2 hours ago, jabloomf1230 said:

I'm not convinced  that the new terrain-aware logic in 7.3 is working  correctly all the time. Try changing the option  to "FALSE" in VASettings.xml. 

 

I'm thinking the same thing, I will try your recommendation and see what happens the next time.

It's supposedly server based, but if so, I wonder what online database it uses for terrain elevation. Other users have posted that they get errors in VOXATC when the server is unavailable.

That would be interesting to find out, if it's an issue to do with the online database!

2 hours ago, jabloomf1230 said:

Try changing the option  to "FALSE" in VASettings.xml. 

Jay, sorry for the ignorance, but where do I find this xml file?

Never mind, found it! LOL

I was looking for this new terrain-aware logic in 7.3 within the xml file, but I'm not sure what I'm suppose to switch to "FALSE". I see an entry that reads; "<TerrainServiceEnabled Value="TRUE" />", it's that it?

Yes.

1 hour ago, jabloomf1230 said:

Yes.

Thanks, will make it false then, and see how that works out. The worst it can happen is that I have to switch back to true.

Well, after I made the change from TRUE to FALSE on the xml file,  I didn't try the same flight from Kansas City to Los Angeles, instead I decided to go east from Kansas City to Charlotte North Carolina, KCLT. This time it vector me correctly, and maintained the proper descent and flight level constraints all the way to my assigned ILS runway 23.

All VOXATC does with that set to "TRUE" is it downloads SRTM elevation data for the destination airport and instead of using a "shortest path" to the approach, it considers terrain. I've noticed that whatever algorithm is being used, its degree of success is dependent on the runway, approach and terrain. Sometimes it works just because terrain is not an issue, so it's difficult for me to tell anything except when it fails, like what apparently happened to you.