Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

AI Aircraft SID and STAR Controller

Featured Replies

There's no reason RC4 and AISidStar can't work together. RC doesn't touch AI in flight, and AISidStar doesn't touch them on the ground, so they complement each other, no conflicts.

 

Alrighty. Thanks, Pete!

7950X3D + 7900 XT + 64 GB + Linux | 4800H + RTX2060 + 32 GB + Linux
My add-ons from my FS9/FSX days

  • Replies 593
  • Views 138.6k
  • Created
  • Last Reply

Top Posters In This Topic

Posted Images

#1: Well, I was thinking more about a generic solution. While having text files is all fine and dandy, setting them up is a major endeavour.

 

#3: Does that include multiple SIDs/STARs, i.e. will planes eparting to, say the north use SID x while planes departing to the south use SID y?

 

#4: Okay, good to hear.

 

 

Thanks for the anwers!

Well the hard part for me was trying to get the AIConv.exe to find the PMDG SIDSTARS folder and then having it point to the right directory when they were converted. Now that I took all the airports in the US that have SIDS and STARS and converted them to an AISIDSTAR format it's just a matter of going to my conversion folder, searching the airport code and cntrl A and C then paste into my active folder.

 

Certain SID and STARS are assigned to certain runways. In an airport that has multiple crossing runways there are going to be some procedures that won't apply to the other runways. So if you have the program set up to only use procedures based on active runways then yes AI should only use procedures that are assigned to those active runways.

How did you get AIConv.exe to work?  I can't get it to work, ever.

I converted some files using your program for the airport that I normally use.

 

The minute the AI reach the first waypoint of a STAR the plane slows down to about 52kts. I noticed the same for all the outgoing AI as well.

 

The files were converted using the default settings. I compared the output files with the ones you included and I cannot see any obvious errors.

I'm away from my FSX computer right now, but are you using the latest revision F with the AI holding? http://www.mediafire.com/?rajm9829d21rf01

 

If so, turn off AI holding and set separation to zero to see if that changes anything. Also bump up the AI speed scalar.

 

Also, can you tell me what versions of the simconnect.dll you're using?

 

Also, someone up thread did a lot of troubleshooting on a different issue and solved it by backing up their old fsx.cfg file and regenerating a new one. They sent me the problematic cfg file, which I'll analyze once I get back.

 

Roland.

How did you get AIConv.exe to work? I can't get it to work, ever.

What error are you getting?

I am using the latest version 1.2F

 

Recreated a new fsx.cfg file, still getting the slow AI issue.

 

Changing the speed scalar to something higher than 1.0 does speed the planes up a little, not sure how high one can go with this parameter.

 

The AI holding value was already set to zero.

 

 

Also, can you tell me what versions of the simconnect.dll you're using?

 

 

I have the same three versions of simconnect.dll as the others have reported, 61637, 61355 and 60905.

 

 

Mark Smedley

I keep getting a error that AIconv.exe cannot read the source file or airport data.  I followed the manual exactly.  I like the program and it is working well.  I am frustrated trying to make my own sidstars files using AIconv.exe because it doesn't work.  I am trying to convert my PMDG sidstars.

I keep getting a error that AIconv.exe cannot read the source file or airport data.  I followed the manual exactly.  I like the program and it is working well.  I am frustrated trying to make my own sidstars files using AIconv.exe because it doesn't work.  I am trying to convert my PMDG sidstars.

 

(1) copy aiconv.exe and airports.dat into a temp directory (c:\temp)

(2) copy your SIDSTARS subdirectory to a temp directory (c:\temp\sidstars).

(3) make another new subdirectory under temp called converted (c:\temp\converted).

(4) start a command line and change to the temp directory.

(5) enter the command:  aiconv   .\sidstars\*.*   .\converted

(6) answer the series of questions aiconv.exe asks you.

(7) aiconv will warn you about smaller airports not being found in the database, keep pressing enter.

(8) pick out the files from the converted directory you want to use (they begin with the icao).

(9) put them into an AISIDSTAR working subdirectory (e.g., c:\aisidstar12\all us airports).    

(10) create an AIDISTAR.ini file to point to the new working subdirectory (e.g., STAR=.\all us airports\*.* SID=.\all us airports\*.*).

 

 

I am using the latest version 1.2F

 

Recreated a new fsx.cfg file, still getting the slow AI issue.

 

Changing the speed scalar to something higher than 1.0 does speed the planes up a little, not sure how high one can go with this parameter.

 

The AI holding value was already set to zero.

 

 

 

 

I have the same three versions of simconnect.dll as the others have reported, 61637, 61355 and 60905.

 

The only limit to the speed scalar is the internal FSX slew limit, which FSX imposes automatically, so you can crank the scalar up pretty high (as an interim fix or personal preference).  

 

About 10 minutes after AISIDSTAR starts, it outputs a calibration value to the screen called "speed constant."  Can you email that value to me along with your FSX config at the support email address?  The speed constant allows for the calculation of the correct slew value to achieve target speeds unique to each computer.   

 

-Roland 

Thank you.  Working as we speak.

About 10 minutes after AISIDSTAR starts, it outputs a calibration value to the screen called "speed constant."

 

 

Does it output it to the console window or the FSX screen. I sat there for half an hour and did not notice it.

 

I tried playing with the speed scalar. It seems to multiply the planes speed by the amount set in the ini file. I noticed not all planes are told to move at the very slow speed, some AI planes move at the expected speed. The problem with the speed scalar is that it applies the value to all aircraft, I now have planes flying at almost 2000kts.

 

Another thing I noticed is that the rate of climb/descent is also not being applied to all aircraft. Some are changing altitude at the expected rate, whilst others are basically staying at the same flight level, then crashing into terrain. I even had one plane crash into the sea.

 

I will try disabling any exe files that FSX loads on startup, maybe one of them is interfering.

Mark Smedley

The problem I am having is that it seems that AI are taking A LONG TIME to be vectored, follow the STARS and then released onto the approach. I have holding off and separation set to 6 NM. I would think that with 6 miles and about 10-15 aircraft in the 40 NM area from airport that they would be lined up like ducks. It seems that I get about 1  landing every 5+ minutes. Here are my settings:

 

 

//AISIDSTAR OPERATING PARAMETERS
//**********************************************
//**********************************************
//
//**********************************************
//Distance in NM that AI is allowed to miss
//waypoint before going onto the next waypoint.
//Default=2 NM
//
distMOE=2.0
//
//*********************************************
//
//*********************************************
//Degrees that AI is allowed to veer of target
//while heading to waypoint.
//Default=1
//
degreesMOE=1.0
//
//*********************************************
//
//*********************************************
//Scalar applied to AI turn rate.
//Too high and AI will overshoot expecially
//during long turns.
//Too low and AI might be too slow to acquire
//desired heading.
//Default=1
//
AIturnscalar=1.0
//
//*********************************************
//
//*********************************************
//Scalar applied to AI speed.
//Default=1
//
AIspeedscalar=1.0
//
//*********************************************
//
//*********************************************
//Alitude in feet above ground level (AGL)
//the AI will obtain after exiting last
//waypoint in SID before being handed
//over to FSX ATC for final vectors to final.
//Default=3000 ft.
//
AIpatternalt=3000
//
//**********************************************
//
//*********************************************
//Scalar applied to AI rates of ascent and descent
//Default=1
//
AIascentdescentscalar=1.0
//
//**********************************************
//
//*********************************************
//Radius in meters to monitor AI for control
//
//Default (and SimConnect Max) = 200000 meters
// (i.e., about 108 NM).
//
//WARNING:  Max = 200000 exceeding which will
//cause Simconnect to return an exception.
//
AImonitorradius=200000
//
//**********************************************
//
//*********************************************
//Separation distance between AI aircraft (in nautical miles)
//Default=5
//
AIseparationdistance=6.0
//
//**********************************************
//
//*********************************************
//AI allowed to hold at stepped alttitudes at STAR entry point
//in order to maintain AI separation distance.
//Default=0 (false)
//
AIholdingallowed=0
//
//**********************************************
//
//*********************************************
//"Going around" (missed approach) vectoring.
//0=No, 1=Yes  (Default = 1)
//If 1 (Yes), AI will be assigned SID to fly.  After exiting SID,
//AI aircraft will leave the //monitored area permanently.   
//If 0 (No), FSX will vector AI aircraft going around using its
//typical VFR like pattern.
//
//
AIgoaroundleavearea=0
//
//**********************************************
//
//
//*********************************************
//Automatic Selection of STARs based on landing runways in use
//0=No, 1=Yes  (Default = 1)
//
//If 1 (Yes), AI will be assigned a STAR with entry point closest
//to the AI *and* specific to one of the landing runways in use
//
//Note: A STAR file with specific runway data must exist (e.g., runway
//data present in STAR file for the montiored airport).
//
//Note: FSX landing data must also be AVAILABLE for the monitored
//airport when the STAR is chosen (sometimes it will not be).
//
//Note: If a STAR specific to landing runways in use is not found,
//AISIDSTAR will only select a STAR with the closest entry point.
//
//If 0 (No), STAR with entry point closest to AI will be selected.
//
//
AIautostar=1
//
//**********************************************
//
//**********************************************
//AISIDSTAR.exe status output to SimConnect console
//screen is more verbose.  0=No, 1=Yes (Default = 0)
//
//
verbose=0
//
//**********************************************
//
//**********************************************
//AISIDSTAR.exe status output to SimConnect console
//screen is at debug level (only for bug tracking).  0=No, 1=Yes.
//(Default = 0)
//
//
debug=0
//
//**********************************************



 


I also want to mention that I have some aircraft that have been assigned a runway but they seems stuck. I have a United flight that is assigned runway 25L at LAS but is 5 nm from the airport at 10,000ft and seems to just be stuck there.

 Dont know if this would help but i figure i share it anyways .. Back when i was working on a similar software we find out that it was alot better to write software that was a bit more complex and also required AI planes files to be modified so that our software could better  comunicate and let us have better control over speed, altitudes and route following so that AI traffic , the first attemp was a simpler setup and wont allow us to control traffic from start to finish . things got even harder when we tried to control ground traffic . 

Image removed as image is no longer available.

I have let my sim run for over 2+ hours at LAS. The are a few flights that have not been assigned runways. Seems to still be a large gap between landing planes.

 

To the above: I am all in favor for manipulation of air traffic to mirror a more realistic standard. On the ground I think FS does as good of job as it gets. Which can also be aided by either increasing or decreasing taxi speed or by changing around taxi routes and adding or omitting taxiways.

Does it output it to the console window or the FSX screen. I sat there for half an hour and did not notice it.

 

I tried playing with the speed scalar. It seems to multiply the planes speed by the amount set in the ini file. I noticed not all planes are told to move at the very slow speed, some AI planes move at the expected speed. The problem with the speed scalar is that it applies the value to all aircraft, I now have planes flying at almost 2000kts.

 

Another thing I noticed is that the rate of climb/descent is also not being applied to all aircraft. Some are changing altitude at the expected rate, whilst others are basically staying at the same flight level, then crashing into terrain. I even had one plane crash into the sea.

 

I will try disabling any exe files that FSX loads on startup, maybe one of them is interfering.

Yes, to the console window. Make sure you are in verbose=0 mode (if you are not already).

 

Are you running Pro-ATC and/or OpusFSX? I've had two other users report strange AI behavior running these at the same time as my program. To try to address this issue, I just finished a program update that stores its FSX control data in reserved memory space on the FSX server, which allows me to force read access only to other simconnect programs. Theoretically at least there's no way any other simconnect program will be able to interfere with commands sent by AISIDSTAR to FSX, unless they're both trying to control the same AI. The updated program also checks for incompatible (earlier) simconnect versions. I'll get the version posted shortly, I'm doing basic testing of it now.

 

The problem I am having is that it seems that AI are taking A LONG TIME to be vectored, follow the STARS and then released onto the approach.

I just added your earlier request (a hold option at the STAR exit point and additional spacing for turbo-props). I'm doing basic testing of it now. I'll take a look at KLAS, I know you've been testing there a bit. I'll assume you developed the STAR files using default options for AIConv.exe (let me know if you did not).

 

-Roland

Hi Tried it for the 1st time now am flying YUL-YYZ, DEP from YUL most of AI speed are below 100kt now arriving YYZ the samething for the arriving Acfts. am using the basic INI latest version.

Arslan Nouar

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.