The ai addon does not or will not effect your ATC, so all should be fine Aamir.

 

No no, but my question is: Will ATC still be the presiding body controlling air traffic movements, or will this program take precedence?
i.e: If I'm running Pro ATC/X, will PATC/X be the one vectoring these AI onto the SIDs and STARs, the same it would do for me, or will this program override Pro ATC/X so essentially I'm taking orders from PATC/X and the AI from this program? I hope you understood, it's a rather roundabout way of asking a question, I do apologize

I'm the author of AISIDSTAR.  Thanks Julian (and everyone) for the feedback.

This is a fantastic idea Roland, thank you very much for keeping it freeware.  :im Not Worthy:

 

 

.e: If I'm running Pro ATC/X, will PATC/X be the one vectoring these AI onto the SIDs and STARs, the same it would do for me, or will this program override Pro ATC/X so essentially I'm taking orders from PATC/X and the AI from this program? I hope you understood, it's a rather roundabout way of asking a question, I do apologize

Ok, now I see what you mean, it should not interfere with pro atc, Sorry I misunderstood your question.

 

 

Ok, now I see what you mean, it should not interfere with pro atc, Sorry I misunderstood your question.

 

Awesome, this sounds just about perfect!
UT2+Pro ATC/X+AIDSTAR, man I can't wait to give it a go.

I'm actually working on a new version right now with significantly better capabilities.  Ronald Kohls (must give him credit) suggested to me why not monitor more than one airport?  It then dawned on me that he was right, with a little modification, there wasn't a limit to the number of airports the program could monitor as long as it had SID and STAR files for those airport.

I was going to write and ask for this too. You need to be able to cover at least planned departure and destination airports, and maybe one or two alternates. Ideally it would automatically handle the nearest airport(s), but for arrival airports it would presumably need to have a range of some 40 miles or more to ensure AI traffic is behaving correctly when the user arrives.

 

For example, you can monitor all the airports in a region at the same time.  Ronald wrote up SID and STAR files for the major airports in the LA metro region (KLAX, KBUR, KLGB, KONT, KSMO, KSNA, and KVNY).  The new version will load up all of those SID and STAR files (if you tell it to) and then vector the AI at all of those airports at the same time.  The result is that when you're flying through the region, all of the AI (except enroute AI passing through the area at flight levels) are following published SID and STAR procedures.  I'll include those files in the new version.   

That is all good, but would it be possible for you to accept one of the existing SID/STAR data formats (i.e. those available through NaviGraph or Aerosoft's NavDataPro? Your format seems unique. The one supplied for ProATC/X is in XML form but uses different tags. I was thinking of writing some sort of converter, but really the long term solution for all would be to adopt an existing one directly. What do you think?

 

Thanks for a very cute program in any case.

 

Pete Dowson

Not to detract from his great suggestions, but

Pete Dowson

That sure is a high profile endorsement if ever there was one! Keep up the good work.

 

What I also really want to see is the AI aircraft distributed across the available runways, rather than assigned the closest available runway, but that would require a hook, I think.

 

In the meantime, this is an excellent and much-needed addon. Thank you.

 

Bryn

 

 

What I also really want to see is the AI aircraft distributed across the available runways, rather than assigned the closest available runway, but that would require a hook, I think.

 

The closest runway to the airplane would be normal (generally not an opposite direction to the primary runway)...certainly with winds on the calm side.  I think it'd be cool if aircraft did pick runways that FSX tends to ignore.  Rwy 15 at KSBA is NEVER used by FSX...only the primary runway 7/25 is ever used.  Along the 'fix things' catagory, sometimes ATC assigns stupid runways to airplanes...2500 foot runway to a 737. 

 

 

I'm the author of AISIDSTAR.

 

Will this work with VoxAtc ?  Vox generates its own AI and I've had issues with other addons like Super Traffic Board because of the way AI is handled.

 

Thanks

 

 

That is all good, but would it be possible for you to accept one of the existing SID/STAR data formats (i.e. those available through NaviGraph or Aerosoft's NavDataPro? Your format seems unique. The one supplied for ProATC/X is in XML form but uses different tags. I was thinking of writing some sort of converter, but really the long term solution for all would be to adopt an existing one directly. What do you think?

 

Thanks!  I agree, I'll add support for standard format(s).  Now that I'm switching over to monitoring multiple airports, I can see the need to routinely load hundreds of SID/STAR files if the user wants to monitor a region, state or small country.

 

-Roland

 

 

 

 

 

Thanks!  I agree, I'll add support for standard format(s).  Now that I'm switching over to monitoring multiple airports, I can see the need to routinely load hundreds of SID/STAR files if the user wants to monitor a region, state or small country.
 
-Roland

 

You legend.  :im Not Worthy: 

Would I come across as a bit of a c*** if I ask for an ETA?

Will this work with VoxAtc ?  Vox generates its own AI and I've had issues with other addons like Super Traffic Board because of the way AI is handled.

 

Thanks

 

I don't have first hand experience with the program.  If it injects AI aircraft controlled by FSX it should work with AISIDSTAR.  It is hard for me to tell from the product description.  It is possible to generate "replacement" AI traffic with custom flight plans, but the AI is still controlled by FSX.  On the other hand, it is possible to  generate AI traffic not controlled by FSX, which I wouldn't know how to deal with.  Please give it a try and let me know.  I don't change FSX settings, so if it doesn't work, don't run AISIDSTAR and VoxATC will be back to normal.

Hmm... this looks very interesting. Perhaps you could also implement generic arrival procedures for the majority of airports that do not have SIDS or STARS... i.e. vector AI to downwind, base, final depending on direction of arrival. If the program could intelligently vector, control speed, and separate all arriving aircraft, that would really be ground-breaking !!!

Hmm... this looks very interesting. Perhaps you could also implement generic arrival procedures for the majority of airports that do not have SIDS or STARS... i.e. vector AI to downwind, base, final depending on direction of arrival. If the program could intelligently vector, control speed, and separate all arriving aircraft, that would really be ground-breaking !!!

 

Wouldn't that be more geared toward GA than anything else?

Thanks!  I agree, I'll add support for standard format(s).  Now that I'm switching over to monitoring multiple airports, I can see the need to routinely load hundreds of SID/STAR files if the user wants to monitor a region, state or small country.

Excellent! I look forward to it!

 

Pete

 

 

Wouldn't that be more geared toward GA than anything else?

 

Nope...geared toward everyone. There are hundreds of air-carrier serviced airports that have no SIDs or STARs.

@Clipper Ocean Spray: For the time being could you please add support for EHAM and EDDF soon?

 

Thanks,

Dirk.