Hi all, i was follow my traffic on flightsim commander9. All my traffic took off runway 7R @ lebl (Barcelone ) according the wind direction. Altought i ve got a problem with the traffic at arrival your programm assign a star for a landing to the runway 25R.

Well, i want to know how your programm interact with the weather.

Thanks.

I have a problem with a bunch of ai traffic all landing close together at UK2000 EGLL.  Is there a way to fix that

 

 

 

I have a problem with a bunch of ai traffic all landing close together at UK2000 EGLL.  Is there a way to fix that

 

 

Untitled-1.jpg

 

What configuration settings you were using?!  E.g., did you turn on traffic separation and if, so, what values are you using?  Did you also turn on holding?

 

 

Hi all, i was follow my traffic on flightsim commander9. All my traffic took off runway 7R @ lebl (Barcelone ) according the wind direction. Altought i ve got a problem with the traffic at arrival your programm assign a star for a landing to the runway 25R.

Well, i want to know how your programm interact with the weather.

Thanks.

 

Sometimes there's a delay between detecting the runways in use and getting that info. to all of the AI(s).  It is explained a bit more in the readme.pdf.

 

-Roland

What configuration settings you were using?!  E.g., did you turn on traffic separation and if, so, what values are you using?  Did you also turn on holding?

I changed the AIseparationdistance=6.0 and the AIholdingallowed=3 in the .ini.

 

Mike

 

 

I have a problem with a bunch of ai traffic all landing close together at UK2000 EGLL. Is there a way to fix that

 

I use AISmooth.  AISmooth will instruct approaching AI aircraft to perform holding patterns if they are following the aircraft in front too closely. 

 

Best regards,

Jim

I changed the AIseparationdistance=6.0 and the AIholdingallowed=3 in the .ini.

 

Mike

 

Were there a lot of AI holding?  If more than 35 AI start holding in the reality bubble, the program will start force releasing them without regard to separation because, if it doesn't release them, a standoff occurs and the arrival rates drop.  The output console will let you know the AI are being forced released from hold.  

 

The next version has some more robust options (you can change the max number of holders as as increase the program sampling rate to deal with packs of AI packed together closely in a holding pattern).

 

-Roland

Thanks for the log file, I converted the Swiss procedures using the revised AIConv.exe and the output seems OK.  I'll have Rev. M up shortly.

 

I found where the error lies by turning on the logging and verbose features. Let me just elaborate a little more...

 

 

I use AISmooth.  AISmooth will instruct approaching AI aircraft to perform holding patterns if they are following the aircraft in front too closely. 

 

Best regards,

Jim

 

AISmooth is a great program, but I don't think it is compatible with AISIDSTAR.  If you're not interested in AI arrival and departure procedures, AISmooth and AISeparation are both good on their own.  AISeparation however can be used with AISIDSTAR and its method of slewing conflicting AI backwards in a straight line, while brute force, usually gets the job done rather quickly.  ^_^

Good info.  Thanks!

 

Best regards,

Jim

Rev. 1.2M (beta) can be found here: 

 

http://www.mediafire.com/download/8cdaa2si4bsihie/AISIDSTAR12M.zip

 

New: Ultimate Traffic (UT2) Compatibility.  To enable, (1) set UT2Compatibility=1, (2) set AImaxspawndistancefromstar=60 (or 50 or 70), and (3) provide a full FSX path to your folder where the FSX flight plans are stored, e.g., MyFSXDocumentsPath=C:\Users\My Name\My Documents\Flight Simulator X Files.  For network users, a network (UNC) path may be specified to a shared folder with write access. 

 

NOTAM: when running AISIDSTAR in UT2 mode, AISIDSTAR must run on a networked PC.  Directions for running FSX utilities on a networked PC (any old laptop will do) are included in the readme.pdf file and it is something most readers should have done already anyway (and not just for this program).

 

NOTAM: this option will preserve the UT2 jet routes except for a circumstance so limited, you'll never see it. 

 

New: Telemetry for external program interface.  To enable, set AITelemetry=1 and provide path to FSX flight plan folder as discussed above.  Very interesting things are in the works regarding how other programs may use this feature, stay tuned!

 

New: High Sampling Rate option.  To enable, set AIhighsamplerate=1.  Sampling period will change from 4 sec. (default) to 1 sec. (high).  AISIDSTAR has been "tuned" to the default 4 sec. sampling period, which should be satisfactory in all but the most extreme AI densities.

 

New: AI Max Holding limit (undocumented).  To enable, add this line to .ini:  AIMaxHolding=X, where X=any number other than 35 (default).  When the max AI holding limit is exceeded, the program starts releasing AI from hold without regard to separation in order to clear out the holding AI and to keep the arrival rate up.  If you want more AI to hold before this happens, bump this number up, but you may want to also turn enable a high sampling rate (above) and reduce the array sort rate (below).

 

New: Array Sort Rate (undocumented).  To enable, add this line to .ini: AIVectorSortPeriod=X, where X=any number other than 20 (default) (secs).  Part of the secret sauce in this program is a rather large array sorted by AI pattern distances.  This sort is probably the most computationally intensive task the program does, but if you're running the utility on a networked PC, why not crank this down to 5 seconds or so (so what if the CPU usage on your networked laptop goes up to 2%)?

 

Revised: AImaxspawndistancefromsid and AImaxspawndistancefromstar now refer to the distance from the airport rather than the entry point to the STAR or SID.  If you were seeing departing AI not getting vectored because supposedly it was too far away from the airport, yet when you looked at a traffic map the AI had just taken off, this should fix the problem.  Previously this parameter referred to entry way points, which in some situations were past the AImaxspawndistancefromsid from the airport, in which case the departing AI would not get vectored when it should have.  

 

Fixed:  AIConv.exe for certain patterns was inserting the text "HOLD" into the altitude restriction field, causing AISISTAR to crsh when the file was loaded.  

 

 

New:  Video Documentation (Upated to Rev. M).

 

Video 1 - Installing, Working with the Included Sample SID/STAR Files and Creating New Files Using AIConv.exe:  http://www.mediafire.com/watch/mj3hgm33w24thcv/AISIDSTAR_Video_1_Sample_SID_STAR_Files_and_Creating_New_Ones_Using_AIConv.mp4

 

Video 2 - Custom Editing SID/STAR Files - http://www.mediafire.com/watch/t9irz80c497beo7/AISIDSTAR_Video_2_Custom_Edit_SID_STAR_Files.mp4

 

Video 3 - Operating Parameters.

 

Part 1: http://www.mediafire.com/watch/t7bhbs0x2gnrekn/AISIDSTAR_Video_3_Operating_Parameters_Part_1.mp4

Part 2: http://www.mediafire.com/watch/t8nvlywnceoh67a/AISIDSTAR_Video_3_Operating_Parameters_Part_2.mp4

Part 3: http://www.mediafire.com/watch/c3j1rmkvhoa6xas/AISIDSTAR_Video_3_Operating_Parameters_Part_3.mp4

Part 4: http://www.mediafire.com/watch/t76l7wzds0zz9z8/AISIDSTAR_Video_3_Operating_Parameters_Part_4.mp4

Part 5: http://www.mediafire.com/watch/24s4ek5x7xtiuf8/AISIDSTAR_Video_3_Operating_Parameters_Part_5.mp4

 

 

Thanks!

-Roland

The increased sampling rate in rev M has helped a lot. Here are some of my observations; I will try to get a "verbose" log tomorrow, it's kind of hard to see what's going on in the console with it on.

1. Arriving traffic seems to be put into holds too readily. For example, when AI aircraft arrive close to eachother at the edge of the "bubble", one seems to be put into a hold immediately, at the start of a very long star (plenty of time for speed differentiation). Instead of speeding the lead up and slowing the other down, the program seems to put one of them into a hold immediately, and this is compounded when there's lots of traffic. Sometimes you see freshly spawned traffic that gets put into a hold due to another aircraft that is on the same STAR while 15+ miles away, so something doesn't seem right. That said, I can imagine the complexity in trying to "predict" the need for holding, so this might well be by design. This is with AIholding=3 and a separation distance of 4.5 by the way.

2. The holding patterns flown by the AI seem really really large and spread out. Is this intentional? Is putting them into neat, compact racetracks over the waypoint too system-demanding? As it stands, the patterns seem to cover miles, and often the traffic is out of position or at the wrong altitude when released from the hold, leading to dive-bombing to get to the correct altitude and other issues. Some traffic gets put into a hold at the entry, and then actually seems to follow the STAR (hard to tell exactly in the traffic toolbox map), before I get the "released from hold" message near the STAR's exit point.

 

3. Is there a way to increase the "Hold release" frequency. Ideally, lets say if 10 aircraft suddenly spawn at close to the same track distance on their respective STARs, the first few would continue at varying speeds to increase separation, while the remainder tightly orbit the entry waypoint at various stacked altitudes. Then, at intervals of 45 seconds (enough for lead aircraft at ~355 knots to go 4.5 nm for separation), you would release the aircraft in the race track from their holds, leading to a nice "string of pearls". This might be beyond the limitations of FS or your program (I probably would be stuck in getting it to work), I apologize if that's the case.

ANyways, thanks for the great program. I'll try to get a log for you so you can have more concrete data.

Downloaded the rev M.  It seem to fix the bunch of planes landing behind one another at UK2000 EGLL, but now it seems that the AI planes are keeping on doing a flyby around the runway even though the runway is clear.  I changed the AIhighsamplerate=1 and AIMaxHolding=50

Roland,

 

thanks for version M, I will test it right away. 

 

I have a question regarding Tunis (DTTA): whenever I run the DTTA.txt through Aiconv.exe I get out SIDs but no STARs.

Could you please explain shortly what this is related to and what changes I could make to be able retrieve STARs as well?

 

Thanks so much!

 

Nizar

Hi Nizar

 

Are you using the PMDG  DTTA.txt file?  If so, if you open it you will find only SIDs, there are no STARs in that file.

I've also just looked at the chart for TUNIS, just to confirm that there are no STARs. This is correct. There are only NDB and VOR approaches

 

Hope this helps

 

 

Clive

Hey Clive,

 

yes, that's the file. I had a look too and I noticed it had no STARs, but I thought that maybe there is a way to make changes in order to make AI fly the waypoints in there.

 

Thanks for your help!

 

Best

 

Nizar