FSX-MS AI Controller 1.4 (SID, Jet Route, STAR and Final Approach) (New) Beta

[Clipper Ocean Spray 189]

Here's a central list of the issues so far with 1.4A in one list for anyone experiencing problems and wondering about fixes/status.  Please press the "Full Post" button below for the program description and download link.

 

AI on Ground Freezing When I Fly (or Slew) Around the Airport Observing AI Movements:  This is not a bug, but a normal option enabled by default.  Make sure the freezing AI is not cause by the "Detect User Landing - AI taking Off - Freeze AI" in Options/Final Options (Standard).  I'm probably going to either change the default value to 0 (disabled) to bump up the AGL to 2000. The intent of this option was a "last line of defense" to prevent AI from lumbering onto the landing runway while you, the user aircraft, are on short final after having managed to complete a meticulously planned flight.   I'm finding that users, quite naturally after installing AIController, are flying (or possibly slewing) around the field at low altitude to observe AI movements, which triggers the feature (freezes some AI on the ground) creating the impression of a problem.

 

AIController Not Working on a Network Machine (Simconnect Client):  Temporary fix:  (1) you do NOT have to setup a network drive as mentioned in the readme, (2) instead in the AIMonitor config paths menu, browse the shared network folder pointing to FSX, (3) add it, (4) then add a slash to the end, and then (5) apply. To specify the path of the WPNAVRTE.txt file (for jetroutes) on a networked machine in "Options\Config Paths", first (1) manually copy the WPNAVRTE.txt file from the FSX machine to a temp folder on your networked machine, (2) then press the "Change" in AIMonitor to select the path to the temp folder, then (3) press "COPY."  You will then be able to (4) press the "Yes" button to merge with oceanic data.

 

Directory with No STAR File Error:  For some user machines, AIController is reading subfolders holding inactive patterns as a file, causing this error.  You will see the AIcontroller error statement "THIS ERROR USUALLY INDICATES ONE OF THE STAR PATH STATEMENTS ACCIDENTALLY POINTS TO A DIRECTORY WITH NO STAR FILE."  To fix, just delete all the subdirectories that AIController complains about, some of them are called "inactive", some are called other names.  Since the intent was for these sub-folders to hold inactive patterns, you're not losing much. Looking into this issue.

 

Scenery Decompile Taking a Long Time (for some Users, e.g., 24 minutes):  Currently looking into this issue.  Go ahead and let the decompile complete.  You only have to decompile once per scenery change.  Looking into this issue.

 

Enabling UT2 Compatiblity Flag Makes It Seem as If NO Jetroutes are being Assigned:  enabling UT2 compatibility prevents AIController from assigning jet routes so as to not interfere with the UT2 jet routes function.  Unfortunately, AIMonitor is a bit misleading about this as it indicates in the special comments field "Unable to 

Assign Jet Route - Path Solution Not Found - Will Recheck in one minute" which creates the impression of a problem.  I'll revise the text in the next version to indicate something like "UT2 Option Enabled - UT2 Jetroutes Only." 

 

AIController Can't Continue Because No Taxi Data for Monitored ICAO:  Latest navdata may include airports not in FSX/P3D stock scenery.  For example, PMDG's up to date AIRAC data includes an airport in Spain, 'LEDA'. This is a new airport that was opened in late 2010, and as such is not included in stock FSX. So when I am starting up AIController, it comes up with an error there is no taxi data found and it cannot continue. Unless you want to go ahead and add the scenery yourself (there is a freeware version in the Avsim library for those who want to), I suggest simply deleting the SIDSTAR data for the airport. This issue may come up for a few airports that have been constructed since FSX was released e.g. Bangkok, new Doha etc.

 

Just After AIController Startup or During Windshifts at a Monitored Airport, AIController Recognizes some AI Are No Longer on the Correct STAR for the Landing Runway, However AIController Continues to Assign Wrong STAR for New AI.  Looking into this issue.  The STAR re-assignments may delay AI arrivals, but they will eventually arrive via the correct STAR.

 

AI Stop and Start a Lot While Taxiing In:  I'm using conservative values for the taxi-in parameters at default.  I haven't spent a lot of time optimizing these values, but increasing the "Taxi Turn Speed Scalar" to 1.50 and increasing the "Max Angle AI Off Target to Next Waypoint Before Stop" to 60 helps a lot.  You can tell your tweaks are not working if the AI veers off the taxiway too many times or if the AI starts circling a random taxi waypoint.  If anyone has a really good tweak of these parameters, please email me.  I would be very interested in trying them out as default values for the next version.

 

-Roland

[Clipper Ocean Spray 189]

 

 

No go, have to translate from dutch, but it says that the config beside each other is wrong..  

 

Unfortunately it seems you're getting a side-by-side configuration error, which basically is Microsoft's extremely  uninformative way of telling you a library you need is missing, has an incorrect version, or is corrupted.  

 

Please review these posts, especially since you're using P3D.  Hopefully all you need to do is install the P3D simconnect libraries:

 

http://forum.avsim.net/topic/447974-ai-controller-sid-jet-route-star-and-final-approach-beta/?p=3169748

http://forum.avsim.net/topic/447974-ai-controller-sid-jet-route-star-and-final-approach-beta/?p=3173232

http://forum.avsim.net/topic/447974-ai-controller-sid-jet-route-star-and-final-approach-beta/?p=3173650

 

-Roland

 

 

Does this not work worldwide, I mainly fly in Europe.

 

Yes, there's European samples included that can be activated.  Take a look at the install video, which may give you a better idea of how to activate these samples.

 

-Roland

[pilotter 248]

 

 

Unfortunately it seems you're getting a side-by-side configuration error, which basically is Microsoft's extremely  uninformative way of telling you a library you need is missing, has an incorrect version, or is corrupted.  
 
Please review these posts, especially since you're using P3D.  Hopefully all you need to do is install the P3D simconnect libraries:
 
http://forum.avsim.n...beta/?p=3169748
http://forum.avsim.n...beta/?p=3173232
http://forum.avsim.n...beta/?p=3173650

 

Ok Roland you are a genius... So it was my simconnect, needed I new install on my laptop taken from the p3d redist package. 

 

In Ai monitor I can now start AIController, howeve the new window with AIContoller ( The black with a lot of text ) is opening,  but after a period of nothing I get Roland IS NOT WORKING ANYMORE as an error message.

 

Slowly getting there. Any how here is the logging;

 

 

AI Controller Ver. 1.4A for FSX and P3D 

 

 

Read STAR0 filename = .\DALLAS METRO AREA AIRPORTS\KDFW\*.*

Read STAR1 filename = .\DALLAS METRO AREA AIRPORTS\KDAL\*.*

Read STAR2 filename = .\DALLAS METRO AREA AIRPORTS\KFTW\*.*

Read STAR3 filename = .\DALLAS METRO AREA AIRPORTS\KRBD\*.*

Read STAR4 filename = .\NYC METRO AREA AIRPORTS\KEWR\*.*

Read STAR5 filename = .\NYC METRO AREA AIRPORTS\KJFK\*.*

Read STAR6 filename = .\NYC METRO AREA AIRPORTS\KLGA\*.*

Read STAR7 filename = .\NYC METRO AREA AIRPORTS\KSWF\*.*

Read STAR8 filename = .\NYC METRO AREA AIRPORTS\KTEB\*.*

Read STAR9 filename = .\LA METRO AREA AIRPORTS\KBUR\*.*

Read STAR10 filename = .\LA METRO AREA AIRPORTS\KLAX\*.*

Read STAR11 filename = .\LA METRO AREA AIRPORTS\KLGB\*.*

Read STAR12 filename = .\LA METRO AREA AIRPORTS\KONT\*.*

Read STAR13 filename = .\LA METRO AREA AIRPORTS\KSMO\*.*

Read STAR14 filename = .\LA METRO AREA AIRPORTS\KSNA\*.*

Read STAR15 filename = .\LA METRO AREA AIRPORTS\KVNY\*.*

Read STAR16 filename = .\CHICAGO METRO AREA AIRPORTS\KORD\*.*

Read STAR17 filename = .\CHICAGO METRO AREA AIRPORTS\KMDW\*.*

Read STAR18 filename = .\CHICAGO METRO AREA AIRPORTS\KGYY\*.*

Read STAR19 filename = .\CHICAGO METRO AREA AIRPORTS\KIGQ\*.*

Read STAR20 filename = .\CHICAGO METRO AREA AIRPORTS\KUGN\*.*

Read STAR21 filename = .\NORCAL REGION AIRPORTS\BAY AREA HUBS\*.*

Read STAR22 filename = .\NORCAL REGION AIRPORTS\BAY AREA REGIONALS\*.*

Read STAR23 filename = .\NORCAL REGION AIRPORTS\CASCADE REGIONALS\*.*

Read STAR24 filename = .\NORCAL REGION AIRPORTS\CENTRAL COAST REGIONALS\*.*

Read STAR25 filename = .\NORCAL REGION AIRPORTS\NORTH BAY REGIONALS\*.*

Read STAR26 filename = .\NORCAL REGION AIRPORTS\NORTH COAST REGIONALS\*.*

Read STAR27 filename = .\NORCAL REGION AIRPORTS\SACRAMENTO CENTRAL VALLEY REGIONALS\*.*

Read STAR28 filename = .\NORCAL REGION AIRPORTS\SAN JOAQUIN CENTRAL VALLEY REGIONALS\*.*

Read STAR29 filename = .\NORCAL REGION AIRPORTS\SIERRA REGIONALS\*.*

Read STAR30 filename = .\PHNL\*.*

Read STAR31 filename = .\KDCA\*.*

Read SID0 filename = .\DALLAS METRO AREA AIRPORTS\KDFW\*.*

Read SID1 filename = .\DALLAS METRO AREA AIRPORTS\KDAL\*.*

Read SID2 filename = .\DALLAS METRO AREA AIRPORTS\KFTW\*.*

Read SID3 filename = .\DALLAS METRO AREA AIRPORTS\KRBD\*.*

Read SID4 filename = .\NYC METRO AREA AIRPORTS\KEWR\*.*

Read SID5 filename = .\NYC METRO AREA AIRPORTS\KJFK\*.*

Read SID6 filename = .\NYC METRO AREA AIRPORTS\KLGA\*.*

Read SID7 filename = .\NYC METRO AREA AIRPORTS\KTEB\*.*

Read SID8 filename = .\LA METRO AREA AIRPORTS\KBUR\*.*

Read SID9 filename = .\LA METRO AREA AIRPORTS\KLAX\*.*

Read SID10 filename = .\LA METRO AREA AIRPORTS\KLGB\*.*

Read SID11 filename = .\LA METRO AREA AIRPORTS\KONT\*.*

Read SID12 filename = .\LA METRO AREA AIRPORTS\KSMO\*.*

Read SID13 filename = .\LA METRO AREA AIRPORTS\KSNA\*.*

Read SID14 filename = .\LA METRO AREA AIRPORTS\KVNY\*.*

Read SID15 filename = .\CHICAGO METRO AREA AIRPORTS\KORD\*.*

Read SID16 filename = .\CHICAGO METRO AREA AIRPORTS\KMDW\*.*

Read SID17 filename = .\CHICAGO METRO AREA AIRPORTS\KARR\*.*

Read SID18 filename = .\CHICAGO METRO AREA AIRPORTS\KDPA\*.*

Read SID19 filename = .\CHICAGO METRO AREA AIRPORTS\KGYY\*.*

Read SID20 filename = .\CHICAGO METRO AREA AIRPORTS\KLOT\*.*

Read SID21 filename = .\CHICAGO METRO AREA AIRPORTS\KUGN\*.*

Read SID22 filename = .\NORCAL REGION AIRPORTS\BAY AREA HUBS\*.*

Read SID23 filename = .\NORCAL REGION AIRPORTS\BAY AREA REGIONALS\*.*

Read SID24 filename = .\NORCAL REGION AIRPORTS\CASCADE REGIONALS\*.*

Read SID25 filename = .\NORCAL REGION AIRPORTS\CENTRAL COAST REGIONALS\*.*

Read SID26 filename = .\NORCAL REGION AIRPORTS\NORTH BAY REGIONALS\*.*

Read SID27 filename = .\NORCAL REGION AIRPORTS\NORTH COAST REGIONALS\*.*

Read SID28 filename = .\NORCAL REGION AIRPORTS\SACRAMENTO CENTRAL VALLEY REGIONALS\*.*

Read SID29 filename = .\NORCAL REGION AIRPORTS\SAN JOAQUIN CENTRAL VALLEY REGIONALS\*.*

Read SID30 filename = .\NORCAL REGION AIRPORTS\SIERRA REGIONALS\*.*

Read SID31 filename = .\PHNL\*.*

Read SID32 filename = .\KDCA\*.*

Distance to Waypoint Margin of Error = 1 nautical mile(s).

Heading to Waypoint Margin of Error = 1 degree(s).

Altitude below which no AI approach vectoring occurs = 1500 feet.

Distance below which no AI approach vectoring occurs = 7 nautical mile(s).

Turn Scalar = 1.

Speed Scalar = 1.

Pattern Altitude after Leaving STAR = 3000 feet.

Ascent and Descent Rate Scalar = 1.

Monitor for AI within Radius = 200000 meters.

No SID if departing AI spawned farther away from airport than distance = 10 nautical mile(s).

No STAR UNTIL arriving AI closer to airport than distance = 200 nautical mile(s).

Minimum Separation Distance between AI = 1.5 nautical mile(s) (Note: =0 is off).

Minimum Separation Distance between User and AI = 1.5 nautical mile(s) (Note: =0 is off).

Allow Holding to Maintain Separation Distance between AI = 4 (No=0, STAR entry=1, STAR exit=2, Both=3, All=4).

Use Custom Hold Waypoints = 0 (No=0, Yes=1).

When Going Around AI Will Leave Area via SID = 1 (No=0, Yes=1).

Automatic STAR Selection Based on Landing Runways In Use = 1 (No=0, Yes=1).

Compatibility Mode for UT2 AI = 1 (No=0, Yes=1).

Provide Interface for External Programs = 1 (No=0, Yes=1).

Use High Sample Rate (Period) of 1 sec. = 0 (No=0, Yes=1).

AICONTROLLER Vectors Piston Aircraft at Monitored Airports = 0 (Off=0).

Turn Scalar During Holds = 1.2.

AI Traffic Speed Adjust Reduction Percentage = 0.7.

AI Turboprop Speed Reduction Percentage = 0.8.

AI Piston (E.g. General Avaiation) Speed Reduction Percentage = 0.4.

AI Jet Maximum Altitude = 32000 ft MSL.

AI Turbo Prop Maximum Altitude = 20000 ft MSL.

AI Piston Maximum Altitude = 9000 ft MSL.

Vector Distance Array Sort Period = 10.

Max. Number of AI Holding in Reality Bubble = 50.

Max. Time Allowed Before Longest Holding AI Released from Hold (Inactivity Timer) = 120 seconds.

Decrease Holding Time Inactivity Timer Based on Number of Holding AI = 1 (Off=0).

Landing Priority Given To AI Forced Released from Hold = 1 (Off=0).

AI Target Landing Rate at Monitored Airports (Number of AI Landing PER MINUTE, e.g., 0.25) = 0.75 planes/minute.

Max. Time AI Is Allowed to Wander During Approach (Without a Runway Assignment) = 240 (Off=0).

AI allowed to approach the destination airport at an unworkable angle = 1 (Off=0).

AI Circles Destination Airport Until Assigned Runway by FSX at this Initial Stacked Altitude 0 ft PLUS AGL (Default Off = 0).

AI Circles around Destination Airport Using Pattern = 1.

Max. Time AI Circles around Destination Airport Waiting for Runway Assignment by FSX  = 600 sec.

Force AI Released to FSX that Are Flying Too Low (Skimming along Ground) to Higher Altitude = 1 (No=0, Yes=1).

AI Final Approach TOO LOW Altitude (at 7 nm) = 1000 ft AGL (Off=0).

AI Final Approach TOO HIGH Altitude (at 7 nm) = 10000 ft AGL (Off=0).

AI Closer than this Value (AI Close Pair) Will be Deleted = 0.164 nm (=0 Disabled).

AI Approach Runway Incursion Height (ft) = 1000 (Default = 1000 ft).

Use Custom Final Approach Files when Forcing AI to Land = 1 (No=0, Yes=1).

Use Automatically Recorded Final Approach Files when Forcing AI to Land = 0 (No=0, Yes=1).

End Rollout Waypoint Recorded After Slowing Down To This Speed = 20 knots.

Maximum Time Program Will Attempt to Automatically Record a Particular AI Approach (Includes Taxi to Gate) = 600 seconds.

AI Speed on Final Approach Between the IAF and 1700 ft AGL When Being Forced to Land = 180 knots.

AI Speed on Final Approach Between 1000 and 1700 ft AGL When Being Forced to Land = 170 knots.

AI Speed on Final Approach Between 500 and 1000 ft When Being Forced to Land = 160 knots.

AI Speed on Final Approach Between Touchdown and 500 ft When Being Forced to Land = 150 knots.

AI Speed on Final Approach Between Touchdown and Rollout = 145 knots.

AI De-accelaration Scalar During Final Approach If Traffic Separation Conflict = 0.8.

AI De-accelaration Scalar During Rollout (Higher Number Means Longer Rollout) = 1.

Time AI Allowed to Slow Down During Roll Out = 90 seconds.

Amount of Time After Passing IAF the Program Will Delay Initiating Final Approach = 10 seconds.

Begin Final Approach Immediatlely After STAR Exit (May Cause AI to Land without Runway Assignments) = 0 (No=0, Yes=1).

AI Allowed to Perform Go-arounds When Forcing AI to Land = 0 (No=0, Yes=1).

Transfer Control of AI on Short Final at 300 (Adjusted) ft AGL back to FSX.

Altitude AGL (ft) at which AI Switches to High Precison Mode for Final Approach = 3000 ft AGL (Default = 3000).

Turn Scalar AI High Precison Mode Final Approach = 2.3 (Default = 2.3).

Ascent-Descent Scalar AI High Precison Mode Final Approach = 0.9 (Default = 1.0).

Try to Land AI That Has Not Received FSX Clearance at STAR Exit = 1 (No=0, Yes=1).

AI Must Asend to this Height Before Assigning SID = 900 ft AGL (default is 900).

No STAR at any time if arriving AI closer to airport than distance = 5 nautical mile(s) (default = 5 nm).

Per AI Calibration Routines = 1 (Off=0).

AI Will Perform Crosswind, Downwind, and Base to Line if with Runway (if Necessary) After Exiting STAR = 1 (No=0, Yes=1).

Straight-in Approach If Angle (in degrees) Between AI Bearing To Airport and Runway Heading Less than = 35 Degrees (Default = 35).

Enable AI Jet Routes (Airway) Enroute Vectoring = 0 (No=0, Yes=1).

Average Flight Level Wind Direction = 0 degrees at 0 knots (Default = 000 deg at 000 kts).

Altitude at which AI Departing or Arriving from UNMONITORED airports are Assigned a Jet Route = 18000 ft (Default = 18000).

Lower Limt Jet Route Altitude for Jet Equipped AI = 28000 ft (Default = 28000).

Upper Limit Jet Route Altitude for Jet Equipped AI = 38000 ft (Default = 38000).

Lower Limit Airway Altitude for Prop Equipped AI = 18000 ft (Disabled = 18000).

Upper Limit Airway Altitude for Prop Equipped AI = 220000 ft (Default = 22000).

NO Jet Route Assigned for Trip Length Below this Distance = 90 Nautical Miles (Default = 90).

Radius to Search for Jetroute Entry and Exit Nav Fixes = 70 Nautical Miles (Default = 70).

Preferred Jet Routes = J,U  (Default is J,U).

Disfavored Jet Routes =  (Default is None).

Scalar Applied Preferred Jetroute = 1.25 (Default = 1.25, Lower More Preferred).

Scalar Applied Disfavored Jetroute = 1.25 (Default = 1.25, Higher More Disfavored).

AIController Performs ONLY Jet Routes (Airway) Enroute Vectoring = 0 (No=0, Yes=1).

AI Jet Routes Computed from Departure Airport (Yes=1) OR from Current AI Position (No=0) = 1.

Delete AI that is NOT departing from or arriving at Monitored Airports = 0 (No=0, Ground=1, Air=2, Both=3).

No AI Cull Above this Height = 0 ft (Disabled = 0).

Enable Enhanced AI Approach Mode = 1  (No=0, Yes=1).

AI Final Leg Distance (Enhanced Mode) = 7 (Default = 7 nm).

AI Final Leg Approach Height (Enhanced Mode) = 3000 (Default = 3000 ft AGL).

AI Final Leg Approach Turn Angle Onto Final (Enhanced Mode) = 45 (Default = 45 Deg., Max = 75 Deg.).

AI Base Leg Distance (Enhanced Mode) = 7 (Default = 7 nm).

AI Max Runway Heading Deviation Angle for Straight-in Approach (Enhanced Mode) = 30 (Default = 30 Deg.).

AI Randoms Deviations from Specified Leg Distances and Altitudes = 0 (Default = 0.0) (Max = 1.0).

Separation Distance on Ground for AI Under Enhanced Control During Taxi-in to Gate (Enhanced Mode) = 250 (Default = 250 feet).

Taxi Speed for AI Under Enhanced Control During Taxi-in to Gate (Enhanced Mode) = 15 (Default = 15 knots).

Minimum Allowed Landing Length for Jet AI (Enhanced Mode) = 6500 ft. (Default = 6561 ft.).

Minimum Allowed Landing Length for Turboprop AI (Enhanced Mode) = 2900 ft. (Default = 2952 ft.).

Minimum Allowed Landing Length for Prop AI (Enhanced Mode) = 980 ft. (Default = 984 ft.).

Maximum Number of AI Landing or Departing Per Runway Before Load Balancing Attempted (Enhanced Mode) = 5 (Default = 5).

Maximum Runway Heading Difference from Wind Direction When Runway Load Balancing Occurs (Enhanced Mode) = 40 deg. (Default = 40 deg.).

Distance Departing or Landing AI Creates Incursion with Taxi AI at Hold Short Positions (Enhanced Mode) = 1 nm. (Default = 1 nm).

Time that AI Remains Parked After Gate (After Arrival) Before Being Deleted (Enhanced Mode) = 30 nm. (Default = 30 minutes).

AI Taxi-in Deaccelleration Scalar When Off Target to Next Waypoint (Enhanced Mode) = 0.93. (Default = 0.93).

AI Taxi-in Acelleration Scalar When On Target to Next Waypoint = 1.15. (Default = 1.15).

Max Angle Taxi-in AI Goes Off Target To Next Waypoint Before Slowdown (deg.) (Enhanced Mode) = 10. (Default = 10 deg.).

Max Angle Taxi-in AI Goes Off Target To Next Waypoint Before Stop (deg.) (Enhanced Mode) = 35. (Default = 35 deg.).

Distance Margin of Error to Next Taxi Waypoint (feet) (Enhanced Mode) = 20.0. (Default = 20.0 feet).

Degrees Margin of Error to Next Taxi Waypoint (degrees) (Enhanced Mode) = 0. (Default = 0 degree).

Min. Distance to Rwy Exit Waypoint to Trigger Runway Exit (feet) (Enhanced Mode) = 30. (Default = 30 feet).

Min. Bearing to Rwy Exit Waypoint to Trigger Runway Exit (degrees) (Enhanced Mode) = 65. (Default = 65 degrees).

AI Taxi-in Turn Rate Scalar (Enhanced Mode) = 1.25. (Default = 1.25).

AI Taxi-in Minimum Angle Difference (deg.) Before Possible Collision Detect (Enhanced Mode) = 15. (Default = 15 deg.).

Number of No-Collision Taxi Waypoints in Ramp Area during Taxi-in (Enhanced Mode) = 5. (Default = 5 (waypoints)).

Inject Departing AI to Maintain Departure Rates (Enhanced Mode) = 1. (Default = 1 (enabled)).

 

 

 

Status so far: Good, please note the above parameters read by AICONTROLLER.exe from the AICONTROLLER.ini file...

 

Override: Final Approach options enabled, but High Sample Rate disabled.

FORCING HIGH SAMPLE RATE ON.

Override: Inject AI to Maintain Departure Rates Enabled, but UT2 Compatibility also Enabled.

FORCING Inject Departing AI OFF.

Status so far: Good, please note the AIController.log file is closing.

For LOGGING specify verbose=1 and debug=1 in the AICONTROLLER.ini file.

 

 

 

***********************************************************

** NOTE:  Do NOT overlay a SECOND window in FSX/P3D      **

**        for an EXTENDED time while using AICONTROLLER. **

**        Doing so will cause AI control problems.       **

***********************************************************

[liketofly1 11]

Hi Roland,

 

Thanks for your anwer,

 

 

Thanks, what is a good download source in your opinion?

 

https://pilotweb.nas.faa.gov/common/nat.html

 

for NAT

 

and some info on PACOT

 

http://www.worldairops.com/PAC/docs/PAC_PAC_OTSTrackUsersGuideforDispatchers_atWorldAirOps.com.pdf

 

https://pilotweb.nas.faa.gov/PilotWeb/noticesAction.do?queryType=PACIFICTRACKS&formatType=ICAO

 

and some for Australia.....

 

http://www.airservicesaustralia.com/flextracks/text.asp?ver=1

 

 

 

Unfortunately I was not successful in getting AIController14A  to run on my machine....

P.S: Roland is not working anymore.....

 

1.)  AIConv.exe is crashing with this error:

 

Problem signature:

  Problem Event Name: APPCRASH

  Application Name: aicontroller.exe

  Application Version: 1.4.0.0

  Application Timestamp: 54e010da

  Fault Module Name: MSVCR120.dll

  Fault Module Version: 12.0.21005.1

  Fault Module Timestamp: 524f7ce6

  Exception Code: 40000015

  Exception Offset: 000a7676

  OS Version: 6.1.7601.2.1.0.256.1

  Locale ID: 3079

  Additional Information 1: 1620

  Additional Information 2: 1620dbaf8dc4c576293bbf0c81152d09

  Additional Information 3: 74f1

  Additional Information 4: 74f140e517e18b89070246aa49b0bfbf

 

this also happens with this version of SIDSTARConverter.....

 

if I copy the 13A version of the AIConv.exe to the SIDSTARConverter everything runs nicely, however I'm not shure it would produce the same data....

 

2.) The scenery decompiler does not like it if one path is missing - even if the product (in my case FSX) is not installed... I run P3Dv2.5 exclusivly.

 

further: sometimes AIConv.exe does not find my MSVCR.120.dll although i have Visual C++ 2013 Redistributable (86) installed and had it repaird....

 

Anyway - thanks for taking the effort to produce such a amazing tool....

 

kind regards

[Sportsfan23 2]

Not sure if this would be considered a "bug" or some random occurrence but during my preflight at KDFW I noticed that the UT2 traffic got stuck. Like there was a plane sitting on the runway and it didn't take off. There were no other planes that would interfere with this plane taking off. So because that plane didn't take off I noticed a plane landing had to do a go-around. The plane that was on the runway then "disappeared" and a couple more planes then took off and I taxied out to the runway. And again the same thing happened. I got stuck behind a plane that just sat on the runway for no reason. I eventually just "Reset" the UT2 traffic and took off. I have UT2 compatibility enabled as well as set the AI STAR SPAWN setting not exactly sure the name off the top of my head at 70. 

[pilotter 248]

 

 

1.)  AIConv.exe is crashing with this error:
 
Problem signature:
  Problem Event Name: APPCRASH
  Application Name: aicontroller.exe
  Application Version: 1.4.0.0
  Application Timestamp: 54e010da
  Fault Module Name: MSVCR120.dll
  Fault Module Version: 12.0.21005.1
  Fault Module Timestamp: 524f7ce6
  Exception Code: 40000015
  Exception Offset: 000a7676
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 3079
  Additional Information 1: 1620
  Additional Information 2: 1620dbaf8dc4c576293bbf0c81152d09
  Additional Information 3: 74f1
  Additional Information 4: 74f140e517e18b89070246aa49b0bfbf

 

exactly the same error here, running networked, windows 7 with SP1, reinstalled both x86 and x64microsoft visual ++2013redistritutables

[Clipper Ocean Spray 189]

 

 

MSVCR120.dll

 

Wait, are you guys getting this error for AIConv.exe, AIController.exe, or both?

 

-Roland

[r0drig0 1]

I am getting this problem too.

[Sportsfan23 2]

I think this was mentioned above but I have seen a couple planes taxiing through the grass. I did modify the numbers to what was posted above and while I did not notice planes taxiing in the grass before, after altering the numbers I did notice it. So maybe altering the numbers has reduced it from what it would of been? 

[Clipper Ocean Spray 189]

I am getting this problem too.

 

Do you have P3D 2.5 as well and this problem is occurring after AIController loads?

 

 

I think this was mentioned above but I have seen a couple planes taxiing through the grass. I did modify the numbers to what was posted above and while I did not notice planes taxiing in the grass before, after altering the numbers I did notice it. So maybe altering the numbers has reduced it from what it would of been? 

 

Thanks for letting me know, maybe it wasn't a good tweak.  I'll keep experimenting with values, I would like to see less stop and go.

 

-Roland

[pilotter 248]

 

 

Do you have P3D 2.5 as well and this problem is occurring after AIController loads?

 

Roland I am still using P3dV2.4, not all program are migrated yet etc. I get this error when I start AIController in AiMonitor. Error comes after AIcontroller loads. 

 

After all night searching on the net I found that it might has to do with the msvcr120.dll . Installed Visual C++ 2013 Redistributable (86 and 64 ). It seems that a lot of programs have had problems with this ( search msvcr120.dll Crash ) but I can't find a solution. 

 

Checked windows integrity with Command prompt sfc /scannow

 

http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/system-file-check-sfc-scan-and-repair-system-files/bc609315-da1f-4775-812c-695b60477a93

 

And checked also by DXDIAG that I am on windows built 7601 Service pack 1 installed. All windows updates done.

[Clipper Ocean Spray 189]

Error comes after AIcontroller loads. 

 

Based on the pictures you sent me (thanks, very helpful), the crash seems to occur about the time AIController attempts to establish a connection to P3D (in your case a network connection from the networked Simconnect client to the P3D Simconnect server).

 

You did install the Simconnect client software on the networked (client) machine and then configure the Simconnect client per the instructions in the "Networked Installation" of the readme.pdf, correct?  See especially the HiFi Technologies "Networked Confiuration with Simconnect" web page I linked to in the readme (they don't have anything to do with my program, but their network Simconnect instructions are very good).

 

If not, you may need to download the P3D Simconnect SDK to get the P3D Simconnect client:  http://www.prepar3d.com/support/sdk/   (if you happen to have the FSX Simconnect client, that will probably work as well because my FSX/Accel Simconnect client connects to the P3D Simconnect server).

 

-Roland

[pilotter 248]

Roland,

 

sorry about the pics, just starting to fresh install P3dV2.5 with the simconnect etc. I hope this is the latest install this year lol......

 

First priority is to get my UT2 transferred to P3dV2.5, When I have P3dv2.5 running I will try to make some pics and post them.

 

Thanks for the patience. But I am not the only one with this error.

[r0drig0 1]

I have MSVCR120.dll error with FSX. It happens when AiController loads.

[liketofly1 11]

Wait, are you guys getting this error for AIConv.exe, AIController.exe, or both?

 

-Roland

 

Hi i only get it for AIConv.exe......alos when running it with SIDSTARConverter, but I haven't tried it jet in combination with running P3D... up to now its only running stand-alone........not networked.....

 

regards