Hello Roland,

User of UT2, I would like to know on which parameter I have to act so that in the starting up of aisidstar, so that all the planes which are close to the airport, approximately 30-40 nm, can land.

I use SuperTrafficBoard v2.3 for UT2. The flights are always to delay (or sometimes do not land) because planes go back up(raise) and go towards a star given by aisidstar.

 

The ideal: - planes already follow a star before 30-40 nm by the airport.

               - Flight UT2 at the hour.

 

Thank you, Jimmy.

Other good idea:

According to the altitude of the plane ai generated by UT2, the plane ai enters on the point of the STAR the closest to its altitude instead of going at the beginning of the STAR.

To reflect.

AIImmediateForceLandAll =1

AIHoldForRunwayPattern=0

AIFinalPrecisionModeAlt=2500

AIFinalApproachGoArounds = 1

AICustomHold = 1

AIFinalApproachAutoRecord=0

AITrafficPattern = 0

 

Nice, I haven't thought of that combination!  Glad to see people experimenting with the options.

 

 

 

The flights are always to delay (or sometimes do not land) because planes go back up(raise) and go towards a star given by aisidstar.

 

There's several way to address the issue.  You could add AIMaxSpawnDistanceFromAirport=30 to your .ini file.  That will prevent any arriving AI spawned within 30 nm of the destination airport from being assigned a STAR.  

 

Also, if you're using the SIDSTARConverter program to creates STARs, make sure the "Create Short STAR" box has the number 30 or lower in it.  

 

You can also edit the STAR files yourself to achieve the same result.  For example, if one STAR has five waypoints, where the entry waypoint is 40 nm out, the second waypoint is 30 nm out, etc., you can create two (or more) STAR files having the same basic STAR, but different entry points.  E.g., the first STAR has the normal entry waypoint 40 nm out, the second STAR has the second waypoint as the first (entry) waypoint 30 nm out.

 

 

According to the altitude of the plane ai generated by UT2, the plane ai enters on the point of the STAR the closest to its altitude instead of going at the beginning of the STAR.

 

Interesting idea, I'll look into it!  One problem might be that many STAR(s) only have altitude ranges associated with the waypoint.

 

-Roland

Hello Roland, Thank you for the speed of your advice and fabulous software. I'll try and I'll let you know.

Regards Jimmy.

Will check this out tommorow...

Hello!

Thank you very much from spain for your AISIDSTAR software. Its amazing to see how aitraffic becomes something realistic.

 I have a question i would like to ask to you.

To test this program, Im flying around Canary islands. I have compiled all the sidstars with "aiconv" for GCXO (Airport of tenerife island). When i fly, i discover that all planes that takes off from there, join to the same SID (ARAC1J) although  there are almost 30 sids to choose (depending of the destination). That means that, for example, a plane that goes from GCXO to Madrid, takes a terrible  route and not the logical one. (loosing 30 minutes to go in the opposite direction). Those planes go to another island to finish the pattern of this SID, and after take their destination). When i saw this i ask to myslef: why dont they depart with the other at least 7 SIDs more on the way?? (BIMB4J, KORA5K, etc...).

 

With the stars, when i put al them, the planes use them, buy when they arrive to final approach, they decide to go elsewhere. why?...

 

Im using Prepar3d V2.2,

my combination of settings is this:

 

AIVectorSortPeriod = 1
AIMaxHolding = 100
AIReleaseTimerMax = 180
AIDecreasingTimedRelease = 0
AIForcedReleasePriority = 0
AITargetLandingRate = 0
AICircleUntilAssignedRunway = 3000
AICirclingTimeNoRunway = 120
AIHoldForRunwayPattern = 1
AIAllowPiston = 1
AITurboPropSpeedAdjust= 1
AIPistonSpeedAdjust= 1
AIFinalApproachTooLow = 0
AIFinalApproachTooHigh = 0
AIClimbOutHeight = 600

 

(also AIholdingallowed=4, AIseparationdistance=5.0 on the default menu...)

could it be maybe the:  AImaxspawndistancefromsid or AImaxspawndistancefromstar?

 

Really thanks for reading and congratoulations again: i cant fly if there is not life around me:)

 

abraham. ^_^

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 did a little test sitting on an airport, running voxatc and using the aicull=2

I made a little video of it:

http://youtu.be/oRRKQekiyr0

 

As you can see in the video AISIDSTAR keeps fighting with a couple of VFR flights that has no departure/arrival information. The problem is that there is no way of knowing if those planes are going to land or are just passing through.

 

Let me know if I can do something else.

When i fly, i discover that all planes that takes off from there, join to the same SID (ARAC1J) although  there are almost 30 sids to choose (depending of the destination). That means that, for example, a plane that goes from GCXO to Madrid, takes a terrible  route and not the logical one. (loosing 30 minutes to go in the opposite direction). Those planes go to another island to finish the pattern of this SID, and after take their destination). When i saw this i ask to myslef: why dont they depart with the other at least 7 SIDs more on the way?? (BIMB4J, KORA5K, etc...).

 

Abraham,

 

The SIDs are selected based on the weighting the distance (including turn angle) from the AI to the SID entry point and from the SID exit point to  the destination.  So, a SID that has an entry point close and straight ahead of the AI and an exit that's "close" to the AI's destination may get selected even the the middle waypoints in the SID take the AI on a circuitous path.

 

I would just remove some of the SIDs you don't like (de-activate).  This is a problem when generating SID/STARs from nav data, sometimes to just get too many of them.  You mention that you have 8 active SIDs now for that runway...I would deactivate about 4 or 5 of them (you can copy the files you don't want to used into a subfolder of the SID directory called "inactive" or the like).

 

 

 

With the stars, when i put al them, the planes use them, buy when they arrive to final approach, they decide to go elsewhere. why?...

 

AICircleUntilAssignedRunway = 3000, AICirclingTimeNoRunway = 120, and AIHoldForRunwayPattern = 1 will cause AI that has exited a STAR, but not been assigned a landing runway by FSX, to begin a circular holding pattern in an attempt to eventually get a landing assignment.  The circular pattern seems to help the AI's chances of getting assigned a landing runway.

 

If you don't like the circular pattern, just remove those options and the AI will perform a downwind, base and final pattern after STAR exit.

 

 

 

(also AIholdingallowed=4, AIseparationdistance=5.0 on the default menu...)

 

Yikes, that a huge separation distance, I would recommend =2  (the program is pretty strict about the separation distance in holdings modes 2-4 (AIholdingallowed) when the AI(s) join final, so a 5 nm separation distance will cut down landing rates dramatically.  I actually think a 1 nm separation works pretty well.

 

 

As you can see in the video AISIDSTAR keeps fighting with a couple of VFR flights that has no departure/arrival information. The problem is that there is no way of knowing if those planes are going to land or are just passing through.

 

Yep, one video is worth a million words....oh well...but thanks for looking at it.  I wish VoxATC had an option to turn off their airborne traffic (or at least the arriving VFR traffic lacking departure/destination data), but an option like that may be difficult and time-consuming to implement.

 

-Roland

Clipper Ocean Spray...thanks! for your quick and kind answers. Now i understand a little bit better your program. Im going to do it now! It seems better than before!

i would like to ask another thing, and i hope not being disturbing a lot!...

 

1) do you think its possible to arrange the "ai taxi speed?"..like this, im sure many "go-arounds" would die. Before, in fsx, the software "flusifix" did it, but now, prepar3d v2 uses an "aiplayer.dll" differente from fsx.

 

2) is there a way that AISIDSTAR manage only the planes under an alttitude specific?. i know you have "aicull", but the problem is that i like to see the other planes flying to their destinations although they are not going to the same airport than me. "AIcull" deletes them. Is there a way to use AISIDSTAR ignoring the planes that are flying high?....

 

3) if for example, i go to "lemd" but i even dont have any folder with sidstars of "lemd" in the main AISIDSTAR, (and aisidstar.ini) will the program manage those planes?

 

really thank you again for reading me and for you great program!

abraham.

Hi everyone,

 

I've just made available the latest beta version 1.3A, which now support AI jet routes and includes Matias's SID/STAR conversion utility.  

 

The program now controls the AI through all phases of flight from takeoff, SIDs, jet routes (new), STARs, final approach and landing.  The old name (AISIDSTAR) gave a limiting impression of the program's capabilities.  Thus, I've renamed my AI control utility from AISIDSTAR to AIController.

 

I've started a new beta thread under the new name to avoid confusion:  http://forum.avsim.net/topic/447974-ai-controller-sid-jet-route-star-and-final-approach-beta/

 

The old thread was very long too.  Thanks everyone for your help and I hope you give a look and continue sending me excellent feedback and suggestions.

 

The final released "old" AISIDSTAR version 1.2QR19 can be found in the avsim library under the file name:  aisidstar12.zip

 

-Roland