First of all thanks for developing this addon. I must confess couldn't read all 23 pages, but only the first 5 and the last, so sorry if I asked something just replied:

 

1) is it possible to run it with RC4 or PATCX? Make sense? Or only default atc?

2) if it only works with default ATC this would be a big improvement of FSX default atc, meaning the ATC can assing SID and STAR (only to AI traffic suppose).

3) is it possible to update databse via navigraph or navdatapro?

 

Thanks so much for your work!

First of all thanks for developing this addon. I must confess couldn't read all 23 pages, but only the first 5 and the last, so sorry if I asked something just replied:

 

1) is it possible to run it with RC4 or PATCX? Make sense? Or only default atc?

2) if it only works with default ATC this would be a big improvement of FSX default atc, meaning the ATC can assing SID and STAR (only to AI traffic suppose).

3) is it possible to update databse via navigraph or navdatapro?

 

Thanks so much for your work!

Let me see if I can help:

1) It was recommended to use 3rd party ATC or even to the extreme of turning off the default ATC sound. The reason is because when the ai is being vectored by the program, it conflicts with fsx's ATC commands-which try to vector the ai rather than use published procedures. Currently, most 3rd party atc dont bother the ai.

2) see 1

3) yes. The procedures are derived from PMDG's airac cycles. you should follow the manual on how to implement, add or update yours

I am late to the game here. ysfsim, I notice that you state that 3rd party ATC is recommended. Does this include VoxATC? Please forgive me if this question has been asked and answered before.

 

Graham

Let me see if I can help:

1) It was recommended to use 3rd party ATC or even to the extreme of turning off the default ATC sound. The reason is because when the ai is being vectored by the program, it conflicts with fsx's ATC commands-which try to vector the ai rather than use published procedures. Currently, most 3rd party atc dont bother the ai.

2) see 1

3) yes. The procedures are derived from PMDG's airac cycles. you should follow the manual on how to implement, add or update yours

 

Anthony thank so much for your reply. So if I well understand for example it may work with RC4, so the AI traffic can follow assigned SID or STAR, the same user could be assigned to? or am I wrong?

I am late to the game here. ysfsim, I notice that you state that 3rd party ATC is recommended. Does this include VoxATC? Please forgive me if this question has been asked and answered before.

 

Graham

 

Im not too sure about vox. I believe some users asked about it in earlier posts. I don't use vox but Im under the impression that it does it's own Sid/Stars?

Anthony thank so much for your reply. So if I well understand for example it may work with RC4, so the AI traffic can follow assigned SID or STAR, the same user could be assigned to? or am I wrong?

That is the main goal of Aisidstars. As for RC, It doesnt bother the ai so the ai can do whatever. If you are spotting ai at airports and listening to the radio, you will hear the atc making lots of repeated commands and such because the ai won't follow instructions while it is under the control of aisidstars. Remember the default atc doesn't care for procedures.

Any thoughts?  I was expecting that aircraft with AILandWithoutClearance=0 would not land without clearance (as per post #552).

 

Yes, the AI should not have landed without clearance.  Can you email me the aisidstar.ini file you're using?  Maybe its a combination of different parameters causing unexpected results.  

 

Also, if you get a chance, add debugatcid1=TF-AMT to your .ini file (this is a new option I added to selectively debug specific AI aircraft).  Then, zip up the aisidstar.log file and email it to my support address listed in the readme.  Thanks!

 

 

Anthony thank so much for your reply. So if I well understand for example it may work with RC4, so the AI traffic can follow assigned SID or STAR, the same user could be assigned to? or am I wrong?

 

RC4 works fine with AISIDSTAR from personal experience.  I think Pro-ATC/X and Pro Flight Emulator will work as well.  Your aircraft and the AI traffic should follow the same assigned SID or STAR if both you and the AI are approach the STAR entry point from a similar position and landing on the same runway(s) covered by the STAR.  However, if there are dozens and dozens of STARs active for a monitored airport in AISIDSTAR, the chances go down that you will end up on the same STAR as the bulk of the AI.  One solution is deactivate excessive STAR files by moving them into a backup (inactive) directory (e.g., aidstar12/Chicago Metro Area Airports/KORD/inactive).   Regarding SID(s), you're more likely to end up sharing the same SID with an AI because only a few usually correspond to a particular takeoff runway.

I am late to the game here. ysfsim, I notice that you state that 3rd party ATC is recommended. Does this include VoxATC? Please forgive me if this question has been asked and answered before.

 

Graham

 

Yes, there was some discussion of this before.  If I remember correctly, departing AI work fine (when assigned SIDs at departure by AISIDSTAR).  You can use AISIDSTAR for SID(s) only.  As for arriving AI, the problem is VoxATC injects VFR AI for a circling approach with no departure or destination data, so AISIDSTAR doesn't control them (can't determine whether they're departing from and arriving at a monitored airport).  It might be ok just to let VoxATC do its own thing regarding these arriving VFR aircraft.  You could also try AISIDSTAR's AICull traffic density options (see the quick reference guide, p. 2 or the readme, p. 13), which delete AI not found to be departing from or arriving at monitored airports (i.e., the VFR VoxATC AI with no departure or destination data). However, I'm not sure what effect this would have on VoxATC (e.g., would it still think the deleted VFR AI are there?).

 

-Roland     

Thank you all for your replies. I will give it a try with Vox and report my findings.

Thank you all for your replies. I will give it a try with Vox and report my findings.

 I'm the one who has been testing with VoxATC. All I can say is that VoxATC and AISIDSTAR it's a no go, at least for me.

VoxATC inject random AI just to give the impression of traffic.

It's worst on arrival. And AISIDSTAR has no data to know where the AI want to land or takeoff.

I'm starting to do some flight with the default ATC because of this.

Matias,

 

Thanks for saving me the time and effort to get to the same conclusion.

 

Graham

Matias,

 

Thanks for saving me the time and effort to get to the same conclusion.

 

Graham

 

Matias or Graham,

 

Could you give the AICull feature a try and see how that works?  Add AICull=2 and AICullHeight=18000 to the .ini.  That should delete all airborne VFR traffic below 18000 feet near all airports monitored by AISIDSTAR.  The best case result would be VoxATC detects the VFR traffic is no longer present and proceeds normally.

 

-Roland

Roland,

 

I think Matias would be the one to look into this. I have not used the program as of yet. Don't mean to volunteer you Matias, but you have experience I lack.

Roland,

 

I think Matias would be the one to look into this. I have not used the program as of yet. Don't mean to volunteer you Matias, but you have experience I lack.

No problem Graham,

 

At soon I have a little time I'll give it a go.

Hi everyone!
Tell me, please, how can I make the AI ​​perform a left traffic pattern? After STAR and approach it always starts right and crashed into the rocks. Kelowna (CYLW) Airport, runway 34.
Thank you.

Hi Clipper

 

Some expectation to see some type of update SID/STAR with Navigraph or similar?

It'd be nice if I could minimize this to the tooltray and be able to put it in my exe.xml file so that way it can boot up automatically with FSX.