Hi,just recently got Voxatc and with the traffic I turn it to 0% for both GA and Airline in FSX and 60% or whatever in Voxatc. I get mostly my WoAI planes at the airport but i also get some of tthe default world travel, orbit etc aircraft. Any ideas?

this is normal behavior.what is it you are trying to achieve?

I am just trying to get rid of the default AI. I only want the WoAI.

let me explain on how Vox knows about your AI and knows what to spawn and based on that you could play around with the files and control what would be spawned.when you run the Indexer (VoxATC Indexer) along with finding the scenery and Planes you have installedin your FSX, it also discovers all your AI BGL files regardless to the source it came from.Vox handles all the AI files equally when it comes to AI spawn.if you wish on removing the Default AI from Vox spawn , you need to delete or rename the file extension of the default AI BGL file from your FSX folder.Most likely located in scenerywordscenery a file trafficAircraft.bgl , Delete the trafficAircraft.bgl file or rename it to something like trafficAircraft.orgonce you do that , you should run the Indexer again.just remember that every time you run the Indexer you need to be sure the file is not present (or renamed)the same is true to all other AI files from other vendors, if you wish on removing them , then just delete/rename the file(s) and run the Vox indexer.Note that many Scenery installations in many cases install some AI with them, hence they may appear as well if not removed prior running the Vox Indexer.

Thank you Joel for the explanation, I'm also interested in the "spawning" of AI. My question is what radius around airports, or method is used to populate or trigger the AI to spawn.

 

I was flying from KSEA to KLAS (Vox traffic set to 40%, FSX to 0%, I have MyTraffic X installed as well) and there are some planes at KSEA on the ground and when I take off but the ones in the air are always behind me. As I fly South they all stay in the KSEA area and that’s it. I would have expected to see some airplanes and flights from the Portland area at a minimum. As I continue South Vox ATC calls for a frequency change to contact Oakland, the FO switches the radio and planes appear, again not in front of me though.

 

When I fly the same route with MyTraffic X controlling the sky’s (FSX settings to 40%) and no VoxATC there are planes everywhere through the whole flight.

 

Is there a config item that I need to change or is this just the way the program works ?

 

Thanks in advance for your help

Mark

I don't know how Vox decides the radius of spawning AI.

it is something I asked myself as well.

Mytraffic and Vox are different AI spawning engines , hence you can't compare them with each other.

that is why you also seeing different results.

That I would ask the Vox Support, they might be able and answer this as it's part of the code.

there could be an xml file you might be able and tweak to change this behavior , however I couldn't find any reference to AI

in the existing xml files in the VoxATC folder.

I advise you asking the support, they might know.

if you do find the answer it would be great if you could share this with us.

This is something i have been concerned about of late. I have decent traffic movement at Departing Airport and at Arrival but i don't see any enroute traffic, i may occasionally get some radio chatter from traffic to tower enroute but i dont see them.

 

VoxATC Traffic Al movement is the one issue i would like to see improved in the future update as apart from that its a great program and i think any other issues that crop up are probably my own fault : ).

VoxATC Traffic Al movement is the one issue i would like to see improved in the future update as apart from that its a great program and i think any other issues that crop up are probably my own fault : ).

 

Agreed - AI handling is poor - from AI entering active runways while taking off to pushing back in the wrong direction. Other than this, VOX is outstanding.

I sent in a request about this issue (see my earlier post this thread) and as usual I received a prompt answer (excellent support). Here is what I learned:

-----------

For the moment VoxATC takes a simplistic approach to enroute traffic. It generates traffic in a 60 NM radius around the user's aircraft. It will generate enroute traffic from the arrivals/departures from your departure and arrival airports. It should distrubute the aircraft around you but in the current version they end up behind you.

-----------

 

So for now in this version it seems to be working as expected. I also hope this is re-worked in the next version. I still think Vox is a great product, can't wait for the update

thanks for the Update man.

that shed some light on the topic.

I agree that VOX is a great program. My one major complaint is how it handles AI traffic. As you stated, there is very little enroute traffic that is visible. You hear a lot of chatter, but see no traffic. Also, when on the ground, when you taxi close to another aircraft, it just disappears.

I sent in a request about this issue (see my earlier post this thread) and as usual I received a prompt answer (excellent support). Here is what I learned:

-----------

For the moment VoxATC takes a simplistic approach to enroute traffic. It generates traffic in a 60 NM radius around the user's aircraft. It will generate enroute traffic from the arrivals/departures from your departure and arrival airports. It should distrubute the aircraft around you but in the current version they end up behind you.

-----------

 

So for now in this version it seems to be working as expected. I also hope this is re-worked in the next version. I still think Vox is a great product, can't wait for the update

 

Thanks for the info.

 

I take it from that then that we will hopefully see some Al traffic improvements in a future update then?

 

Cheers.

pretty much so.

So if we get Al traffic within a 60nm radius, which is fine whilst on the ground and on departure and approach in the air it might be a good idea to have say a 200nm radius whilst at cruise alt, perhaps? It's good to see air traffic in the distance (especially at night) when enroute and not just empty skies. Something we all get in our traffic programs but this is lost when using VoxATC.

 

Along with a few other Al issues i hope something like this can be implemented in the next update.

It just holds VoxATC back from being top of the pile. Heres hoping...

 

Cheers.

Is there anything better than VOXatc at this point?