Guys, I haven't used VoxATC for a while, please remind me if it reads wx dynamically and assigns STARs based on the current wx like say ProATC/X does?

 

Thanks,

Dirk.

 

My understanding is that vox does not assign STARs dynamically - the STAR (or waypoints included in the STAR) need to be in the current flight plan. Vox does seem to observe the current weather as ATIS appears to be accurate as does runway in use. 

 

 

My understanding is that vox does not assign STARs dynamically - the STAR (or waypoints included in the STAR) need to be in the current flight plan. Vox does seem to observe the current weather as ATIS appears to be accurate as does runway in use.

 

Can I correct you? VOXATC does not need a STAR in the FP, and indeed may ignore any that are in there. It assigns the STAR dynamically.

You may indeed correct me. I have never observed this and always receive vectors - unless I have a STAR (or waypoints of) in my FP. From the manual...

 

"To be assigned a SID or STAR, your flight plan must have some waypoints that correspond with waypoints in the SIDs at your departure airport and/or STARs at your destination. The assigned procedure may vary depending upon the runway in use."

The minimum that VOXATC needs is for the end waypoint of the FP to be the first waypoint of one or more STARs. It will then assign a STAR, which may be the only one from that waypoint, or else the appropriate one for the runway in use (if there are several potential STARs depending on runway directions and winds). It then allows the pilot to fly that STAR up to a point, when it will then start to issue vectors. At this point the pilot can either comply with the vectors or else request another approach which they will navigate themselves. The latter option is useful for approaches in mountainous terrain because VOXATC is unaware of terrain. Before flying the flight, it is also possible to tell VOXATC that a certain flightplan should always be flown according to a STAR termination, and never with vectors. An example, any flight into LSGG Geneva, where a flight into Runway 05 would be suicidal unless following approach procedures.

 

If using real world flight plans, they will almost always link into one or more STARs at the arrival airport.

 

The converse also applies to SIDs, of course.

Please, Vololiberista, ask Dave to change the 15 min pause. I've alredy asked him and he told me to fly in Windows mode.  I think that the way FSCaptain does it, makes more sense.  I actually removed the program because the pausing happened to occur while I was trying to figure things out.

I think it's a great program with a lot of potential. 

 

tony

It is a bit of an impediment I agree. But it is a demo only. A taste so to speak. The main programme has 119 regional voices and in ver. 3.0.2 you can do a round the world flight assuming you have enough fuel lol

If using real world flight plans, they will almost always link into one or more STARs at the arrival airport.

 

The converse also applies to SIDs, of course.

A case in point on the PF3 forum. One visitor complained that his fpl didn't work properly because the last wypt he said LEV was too far away. Well it is in respect of 278nm but it is the start of the GILCO FOUR STAR. All the fpl generators will stop there. So you have to either wing it to Houston or enter the STAR waypoints at least as far as GILCO. Without the extra information any ATC programme is going to have to guess its way from there. It wil do it but it's not accurate.

You guys may wish to have a look at this thread.

 

http://www.avsim.com/topic/483009-pf3-atc-program-thoughts/

After reading the 30 plus pages, thanks but no thanks, I'll pass.

After reading the 30 plus pages, thanks but no thanks, I'll pass.

Which manuel did you read lol. The PF3 user guide has 166 pages!!

Can I correct you? VOXATC does not need a STAR in the FP, and indeed may ignore any that are in there. It assigns the STAR dynamically.

 

Thats right. But this feature do now work as it should. 40% of the times the SID/STAR is wrong.

I report this problem to the developer with a few log files. I never get an answer. Maeby because is dificult to repair, and as we can see, the developer do not have to much time for us (voxatc customers).

Thats right. But this feature do now work as it should. 40% of the times the SID/STAR is wrong.

I report this problem to the developer with a few log files. I never get an answer. Maeby because is dificult to repair, and as we can see, the developer do not have to much time for us (voxatc customers).

I'm always interested in buying and supporting addons for flight simulation but will draw the line now when I find that customer support is unresponsive.It's a real shame that voxatc and radar contact seem to now be neglected wrt keeping up with P3d development.

Jay

I'm always interested in buying and supporting addons for flight simulation but will draw the line now when I find that customer support is unresponsive.It's a real shame that voxatc and radar contact seem to now be neglected wrt keeping up with P3d development.

Jay

 

I do ton have P3D, i stil in FSX. But i thing if he update voxatc, maeby some bugs will be repaired. I think I am naive.

In the last update the only fix the developer did was to change the speed of the IA... do not seem to complicate.

it seems that the developer does not intend to improve or repair the product.

Maybe he does P3D compatible to continue to sell ... but either. it seems that the developer has better things to do.

 

 

But this feature do now work as it should. 40% of the times the SID/STAR is wrong.

 

Wrong in what sense?

Wrong in what sense?

 

For example:

The ATIS says the active runway is 18R.

I get a SID for runway 36R

Finally i get taxi instructions to 18R

 

The same for the arrival:

The ATC give me the STAR for runway 18R and finally send me to the ILS of the 36L

 

I have more than 3 log files that proves what i say (if you want it i can send to you)

I have the last AIRAC

This use to happend arround 40% of the times, and that proves i do not do nothing wrong, because 60% of the time work well doing exatctly the same process.

This seems to be a problem with ATC programmes that "give you" a SID/STAR it's invariably the wrong SID/STAR. In real life the SID/STAR that forms part of your fpl will almost always be given as there has to be good reason for sending you another way. That's why I prefer to have an option to at least choose.

Which manuel did you read lol. The PF3 user guide has 166 pages!!

the 30 pages of posts not the manual.

The minimum that VOXATC needs is for the end waypoint of the FP to be the first waypoint of one or more STARs. It will then assign a STAR, which may be the only one from that waypoint, or else the appropriate one for the runway in use (if there are several potential STARs depending on runway directions and winds). It then allows the pilot to fly that STAR up to a point, when it will then start to issue vectors. At this point the pilot can either comply with the vectors or else request another approach which they will navigate themselves. The latter option is useful for approaches in mountainous terrain because VOXATC is unaware of terrain. Before flying the flight, it is also possible to tell VOXATC that a certain flightplan should always be flown according to a STAR termination, and never with vectors. An example, any flight into LSGG Geneva, where a flight into Runway 05 would be suicidal unless following approach procedures.

 

If using real world flight plans, they will almost always link into one or more STARs at the arrival airport.

 

The converse also applies to SIDs, of course.

 

I'm copying and pasting the above to my own readme on VoxATC, very useful for understanding how it works with assigning SID/STARs

 

Thanks, Petraus.

 

Dirk.