4 hours ago, nam1394 said:

Johnny,

how does PE deal with addon airports? What if I have an addon airport that is defferent from the controller and other pilots?

 

regards

I've never had an issue flying into default vs addon airports, so I'm assuming it doesn't matter what addon you are using, they all have the same DP, STAR, and frequency. The only time I've had an issue was when my navigraph data was not up to date and some of the procedures had changed.

11 hours ago, specialist said:

I've never had an issue flying into default vs addon airports, so I'm assuming it doesn't matter what addon you are using, they all have the same DP, STAR, and frequency. The only time I've had an issue was when my navigraph data was not up to date and some of the procedures had changed.

What about ground guidance?

Taxi ways don't generally change, so there is no issue on my end when getting taxi instructions. I always have charts, so I always compare where I'm at to where I'm going regardless.

Can anyone help me?.

 

I'm getting two ground controller voices repeating the same directions, constantly telling me to standby over and over again and to "pass message" when I've said nothing, and basically a loop of nonsense  at flytampa EHAM with Fslabs a320.  Any thoughts?  It seems totally messed up.  I don't know what is causing this.    

I'm getting no departure response after handoff at EGLL and EHAM. 

This issue is causing the program to be unusable for me.

 

A fatal error is occurring sometimes, I think that is leading to these controller problems.  I am using FSlabs a320 and I notice that the autopilot d/c's sometimes using VOX and will not work again on that flight.

 

5 hours ago, Heathrow to Dublin said:

Can anyone help me?.

 

I'm getting two ground controller voices repeating the same directions, constantly telling me to standby over and over again and to "pass message" when I've said nothing, and basically a loop of nonsense  at flytampa EHAM with Fslabs a320.  Any thoughts?  It seems totally messed up.  I don't know what is causing this.    

I'm getting no departure response after handoff at EGLL and EHAM. 

This issue is causing the program to be unusable for me.

 

I had the same problem at Flytampa EHAM. I think it is the scenery AFCAD itself. It is made differently than regular addons. If you have a program with a moving map that shows AI, you will notice that the landing AI landing on invisible runways.

Sadly, voxatc indexer can't read all addon airports.

4 hours ago, nam1394 said:

I had the same problem at Flytampa EHAM. I think it is the scenery AFCAD itself. It is made differently than regular addons. If you have a program with a moving map that shows AI, you will notice that the landing AI landing on invisible runways.

Sadly, voxatc indexer can't read all addon airports.

Anytime I install any scenery, I make sure there are no duplicate AFCADs, and that the scenery is mapped correctly in the sim. Ironically I've seen an addon scenery load, and it looks like it install correctly, but it actually didn't. Even when running the runway number update in VoxATC, may not map correcly in your scenery.cfg file. The best thing to do every time you add or change a scenery configuration is run a scenery configuration editor tool. This will show you any errors, and allow you to corrected in there without opening your simulation program. I use one found here; https://sourceforge.net/projects/fs-sceditor/

You can also run FSX Airport Scanner 1.00.03, a neat utility by ScruffyDuck that allows you to scan duplicate AFX bgl files. One thing you want to make sure before you run this utility, is look in the settings configuration .ini and make sure your sim is mapped to the correct location, because it doesn't automatically detects FSX unless it was installed in the default drive. For instance, mine was in C:\FSX, but the default is C:\Microsoft\Flight Simulation X.

Edited April 25, 20179 yr by specialist
Forgot to mention a procedure.

1 hour ago, specialist said:

Anytime I install any scenery, I make sure there are no duplicate AFCADs, and that the scenery is mapped correctly in the sim. Ironically I've seen an addon scenery load, and it looks like it install correctly, but it actually didn't. Even when running the runway number update in VoxATC, may not map correcly in your scenery.cfg file. The best thing to do every time you add or change a scenery configuration is run a scenery configuration editor tool. This will show you any errors, and allow you to corrected in there without opening your simulation program. I use one found here; https://sourceforge.net/projects/fs-sceditor/

Thanks for the info and I will try these links. But, I am afraid it isn't a case of duplicate AFCADs. I am sure you know that some developers add fake runways to force FSX default ATC to use multiple runways with different headings at once(Flytampa EHAM and Fsdreateam LSZH). Those runways are invisible in the scenery. You can tell they are there by listening to the default FSX ATIS, it will list them as available runways but default ATC won't use them for the AI nor other ATC addons like RCv4, PF3, Proatcx, and Voxatc 6. Voxatc 7 on the other hand will use them. If you run Voxatc 7 AITIS at EHAM, you will hear it saying it is using them and I have FS flight keeper which has a moving map showing AI planes and I can see them lining to land on those fake runways until very low altitude then aborting and this will lead VOXATC to stop working properly. I think the new indexer can't differentiate between those fake runways and the real ones. 

 

For the time being, I am using VOXATC 7 almost flawlessly except for those Addon airports.

 

There are other things that cause VOXATC to not work properly. Changing in winds direction will lead to problems with VOX. So, I always use ASN's winds lock to prevent it from happening. 

I really doubt that they "fake" runways have any bearing on this issue. These runways are almost always placed thousands  of miles from the addon airport center. It's the default  ATC  in the sim that is not coded to just reference  local runways in the ATIS. Either LM should get rid of the crosswind  runway scenery  bug or they should fix the ATIS. I should  note here that VOXATC always announces the correct active departure  runway in the ATIS.

On the other hand, some 3rd party  airports are not 100% correct in the way that they exclude items from the stock airport. Between  that and duplicate  3rd party  airports even a real world pilot would get befuddled. Maybe we should  refer to this bug as the Harrison Ford Syndrome.

What could be causing a fatal error at Eham for me?  Something I'm doing wrong with my setup?

 

 

1 hour ago, Heathrow to Dublin said:

What could be causing a fatal error at Eham for me?  Something I'm doing wrong with my setup?

 

I doubt it. Unfortunately, the only way of figuring out why you are getting a fatal error at just one airport would be to turn on VOXATC error logging  in the settings and email the log file to the developer. Unfortunately, he has not responded to anyone in months. Maybe Kevin Firth has an idea of what to do. He may have looked over the VOXATC log files before.  I have other FlyTampa Airports, but not EHAM.

9 hours ago, Heathrow to Dublin said:

What could be causing a fatal error at Eham for me?  Something I'm doing wrong with my setup?

 

Do me a favor and start a flight at EHAM and listen to the ATIS. Let's see if you have the same problem as I do. This way we know if it is the scenery or my setup.

 

thanks in advance

22 hours ago, nam1394 said:

Do me a favor and start a flight at EHAM and listen to the ATIS. Let's see if you have the same problem as I do. This way we know if it is the scenery or my setup.

 

thanks in advance

Sorry already uninstalled this product.  I may re-install it and try this later though.  I actually prefer VOX to the other software,  but I couldn't get it to work at the airports I want to fly into.  Right now playing with PRO ATC/X and trying to solve some issues there too, heh.

As far as I can remember though, the VOX atis seemed pretty normal.  The default atis did list a whole bunch of runways in use yes.