Hey Roland,

 

I have a question...perhaps bug...with some of the conversions I noticed with KLAS (just an airport I was testing) using the SIDSTAR converter. 

Specifically, the SIDs at KLAS are not converting properly.

For example, the COWBOY SID:  the way the converter did it, all runways head to the NAPSE intersection before routing to COWBOY, but by the chart (and PMDG data), only Rwy01L/01R should go to NAPSE.

The other runways have other waypoints associated to them (and these go in other directions) before heading to COWBOY.
 

Somehow, the converter is not converting the other 3 runways properly for the COWBOY SID.
 

It also happens with the other SIDs that have different waypoint routing for each runway with the same SID exit.
 

Just wanted to know if I'm doing something wrong (I use default settings) or if it was perhaps a bug?
 

Thanks again for the great program!!
 

Regards,

 

 

Perhaps a big message identifying the Sim for which it is being prepared could be incorporated at the start requiring a response before initiating the load routine. Just a thought.

 

Good point, I'll see if I can add a pop-up warning message.

Hi Roland,

 

I don't want to add any pressure but du you have an estimate when you'll be able to release 14B? and will the departure RW be selectable in that version?...

 

kind regards

 

 

Yep, I just noticed stock FSX doing this! I think the next AIController hot fix will have better runway-exit logic (at just one sample-per-second I always hasten to add B) ) and won't need to rely on broken links.

 

that's great to hear for that "backtracking" is some of the most annoying (and one of the hardest to fix) issues in FSX ground AI

if you need an airport with reproducable "strange" runway exit an taxiing you may try FSDT KIAH Rwy 33R

 

the aircraft turn about 120 deg and go straight through the scene ommitting all taxilines to the the southside terminal parking positions (FAIB 738, FAIB A32x, AIG E145, ....)

I think the issue has been addressed because in enhanced-mode the AI won't have to intercept the LOWI FSX-generated IAF(s), which caused problems with where the AI enterered  the custom approaches.  Still, could you refresh my memory?

 

 

So what was happening in 1.3B was, to land on runway 08 at LOWI, they fly over the airport and upto around 30 nm away from it before turning back again and coming in for the visual approach.

 

Cheers!

Good point, I'll see if I can add a pop-up warning message.

Hi Roland

 

Any way you could also add the ability for the user to disable these pop-up warnings after 1st run - such as a check box "Do not show message again" sort of thing or disabling in the menu options? The forced runway reminder gets a tad redundant after oh, say the 5th or 6th time (especially when on final)   :wink: 

 

Keep up the great work!  Thanks.

Roland,

 

As detailed in the thread here (http://forum.avsim.net/topic/465760-air-traffic-manager/) I'm no longer able to get the Air Traffic Manager programto run with my side-by-side FSX-SE installation. Your program still works perfectly, of course! And I'd like to take this chance to once again say thanks for such an amazing gift to our community. My question is this: any chance of adding a functionality like that of the Air Traffic Manager to AI Controller?

 

(It's different from the AICull function, because what ATM did was to basically delete all AI planes above a certain number (default is 100), starting with the furthest away from the user and working its way in--there's also the ability to preserve traffic at your starting or ending airports separately from the overall culling function. AICull is concerned only with monitored airports and planes coming or going, in air or on the ground--it's not looking to keep AI numbers to a certain numerical target.)

 

So, any chance of integrating that sort of "cull all planes above the 100th one" function with AI Controller?

 

Thanks,

James

Specifically, the SIDs at KLAS are not converting properly.

 

For example, the COWBOY SID:  the way the converter did it, all runways head to the NAPSE intersection before routing to COWBOY, but by the chart (and PMDG data), only Rwy01L/01R should go to NAPSE.

 

That was quite an error you uncovered!  The type of error that seems to be a hiccup, but the underlying problem is something much worse (in terms of re-work).  I think I have it fixed now and will include it in the hotfix.  The bad news...I can't state in certain terms which SIDs were affected by this error.  Thus, it wouldn't be a bad idea to re-convert any SIDs you may have from navdata using the new aiconv.exe included in the next hotfix.  Sorry guys....beta.   :(  On the other hand, if you're OK with the SIDs you already converted....then it probably isn't worth re-converting.   

 

I think it is a great idea (like you did) to double-check these converted Approaches, STARs and SIDs at airport the user frequents (fly-over airports less so).

Hi Roland,

 

I don't want to add any pressure but du you have an estimate when you'll be able to release 14B? and will the departure RW be selectable in that version?...

 

kind regards

 

There's still some basic issues (e.g., parking errors, taxi smoothness) I'm trying to take care of (and now a bug in AIConv.exe).  Once those are fixed and everything seems stable, I'll finish 14B.  The next version will have taxi-out and selectable departure runways.  Can you send me an email to AIController2 at gmail.com regarding your earlier user-interface suggestion for selecting landing/departure runways?

 

 

Any way you could also add the ability for the user to disable these pop-up warnings after 1st run - such as a check box "Do not show message again" sort of thing or disabling in the menu options?

 

I know they're annoying, but before I added the pop-up warnings even I had forgotten that I was forcing landing runways, which can result in extreme weirdness that is hard to diagnose unless you happen to remember you left it on (especially if you end up at an airport where you do NOT want to force the runways and where the forced runway selections don't correspond to actual runways).

 

 

As detailed in the thread here (http://forum.avsim.n...raffic-manager/) I'm no longer able to get the Air Traffic Manager programto run with my side-by-side FSX-SE installation. Your program still works perfectly, of course! And I'd like to take this chance to once again say thanks for such an amazing gift to our community. My question is this: any chance of adding a functionality like that of the Air Traffic Manager to AI Controller?
 
(It's different from the AICull function, because what ATM did was to basically delete all AI planes above a certain number (default is 100), starting with the furthest away from the user and working its way in--there's also the ability to preserve traffic at your starting or ending airports separately from the overall culling function. AICull is concerned only with monitored airports and planes coming or going, in air or on the ground--it's not looking to keep AI numbers to a certain numerical target.)
 
So, any chance of integrating that sort of "cull all planes above the 100th one" function with AI Controller?

 

 I'm sure the author will respond.  You're running FSX on the same OS as FSX-SE?  That seems a bit dicey, is that something a lot of people have been doing lately?  I read the thread and I second buying WideFS, it is so useful for moving as many utilities as you can off your flight sim machine and onto a networked client.

 

I'll consider adding that function, but it really does make sense being available in a separate program like Air Traffic Manager.  Example, the function is at cross-purposes a bit with AIController's STAR patterns in that farther-away AI gets deleted resulting in less AI established on a STAR (although I'm not sure the effect would really be that noticeable).  If you're monitoring a lot of airports with AIController, have you tried the stand-alone AICull utility in the lib?  You can preserve AI at airports distinct from AIController's monitored airports.  Simple example: preserve AI at just your departure and destination airport (except optionally normal enroute traffic above a specified flight level).

 

 

if you need an airport with reproducable "strange" runway exit an taxiing you may try FSDT KIAH Rwy 33R
 
the aircraft turn about 120 deg and go straight through the scene ommitting all taxilines to the the southside terminal parking positions (FAIB 738, FAIB A32x, AIG E145, ....)

 

That's good, actionable feedback.  Thanks!  Unfortunately that is one of the few FSDT sceneries I don't have.  Still, let's hope the next hotfix takes care of it.  I think it will...I haven't seen any 120 degree turns in my internal testing except of course if the AI must make a sharp-turn or U-turn to hit the last available exit (it was a bear to preserve this U-turn capability while eliminating sharp turns under normal conditions).

Hi Roland,

 

 

 

There's still some basic issues (e.g., parking errors, taxi smoothness) I'm trying to take care of (and now a bug in AIConv.exe).  Once those are fixed and everything seems stable, I'll finish 14B.  The next version will have taxi-out and selectable departure runways.  Can you send me an email to AIController2 at gmail.com regarding your earlier user-interface suggestion for selecting landing/departure runways?

 

the email just whent out the door....:-))

 

regards

Richi

Hi Roland,

 

I just saw a parking spot with two aircraft parked at the same spot in ENGM..... however, I didn't have AIController running yet, so P3D/FSX does sometimes do that on its own....;-)) 

 

and in regards to:

 

 

 

That's good, actionable feedback.  Thanks!  Unfortunately that is one of the few FSDT sceneries I don't have.  Still, let's hope the next hotfix takes care of it.  I think it will...I haven't seen any 120 degree turns in my internal testing except of course if the AI must make a sharp-turn or U-turn to hit the last available exit (it was a bear to preserve this U-turn capability while eliminating sharp turns under normal conditions).

 

Aerosoft ENGM v2 has the same problem.....you might have that scenery....

 

Just as a thought here.......

 

Maybe it would be more feasable, instead of using a fixed brake scalar for each aircraft slowing it down and then taxi to the next suitable exit, to use a sort of "brake to vacate" approach where AIController determines a suitable runway exit beforehand, depending on Aircraft type, and slows the AI to that exit? or a combination of aircraft.cfg break scalar and a brake to vacate scalar...??? 

 

regards

Richi

That's good, actionable feedback.  Thanks!  Unfortunately that is one of the few FSDT sceneries I don't have.  Still, let's hope the next hotfix takes care of it.  I think it will...I haven't seen any 120 degree turns in my internal testing except of course if the AI must make a sharp-turn or U-turn to hit the last available exit (it was a bear to preserve this U-turn capability while eliminating sharp turns under normal conditions).

 

I'm eagerly awaiting your next hotfix to test there (I'll try to test ENGM too) and give some feedback

Hi Roland,

 

could you explain (in some detail) the variables you use to to control leaving runway and taxiing.

I've some problems to completely understand what some of the parameters for taxiing in AI Controller really do.

 

maybe I just dont't know where to find the info - so some hint would be helpfull (thanks in advance)

 

 

That was quite an error you uncovered! The type of error that seems to be a hiccup, but the underlying problem is something much worse (in terms of re-work). I think I have it fixed now and will include it in the hotfix. The bad news...I can't state in certain terms which SIDs were affected by this error. Thus, it wouldn't be a bad idea to re-convert any SIDs you may have from navdata using the new aiconv.exe included in the next hotfix. Sorry guys....beta. On the other hand, if you're OK with the SIDs you already converted....then it probably isn't worth re-converting.



I think it is a great idea (like you did) to double-check these converted Approaches, STARs and SIDs at airport the user frequents (fly-over airports less so).

 

It was a fluke that I found it.  I was just testing, and picked KLAS for fun since I was there a few months back and was curious to see if the AI would follow the same paths I was observing while I was there.  That's when I noticed all AI were going to the same place!  That's when I took a closer look and noticed the discrepencies with those certain SIDS.

 

Looking forward to the next build!!  Awesome work Roland!

A new beta version of AIController v1.14B (full version including Hot Fix 7) is available at the following link:

 

http://www.mediafire.com/download/ciea8t8zcalor2h/AIController14BFullWithHF7.zip

 

Hot fix 7 by itself is available at the following link:

 

http://www.mediafire.com/download/gbe7cf31ffdwbyw/AIController14BOnlyHF7.zip

 

Please do not mix with any version of 1.4A or earlier.  Instead, install into a separate directory for testing.

 

IMPORTANT:  Hotfix 7 changes may default settings and data decompiled from scenery.  After installation, please select "Options\Reset Options to Default" otherwise the "old" default options may cause poor results.  Also, run a "Force Update Runway and Taxi Data".

 

 

Hot Fix 7 New Features:

 

NEW:  No sharp turns (90 degree OR LESS) when landing AI exits runway (if feasible) in contrast to stock FSX ATC control.

 

NEW:  AIController now checks for broken runway links.  Some scenery designers follow the practice of purposely BREAKING runway waypoint links (e.g., Latin VFR KMIA). AIController now detects broken runway links at startup and warns the user.  AIController will then use the "longest" unbroken link, which is most cases is satisfactory.  NOTE 1:  the root cause of this situation can be remedied by the user simply connecting up ALL of the runway waypoints in a utility like Airport Design Editor X.  However, the scenery designer probably decided to break the runway links in the first place to avoid the AI making sharp turns when exiting the runway, but as discussed above, AIController HF7 does not suffer this drawback.  NOTE 2: if there is any add-on airport where AIController failed to assign final approaches in the past or where the AI was acting strangely approaching or landing on the runway, this might have been the cause. Please run a "Force Update" after installing this hot fix and try it again.

 

NEW:  AIController now warns the user if AIController is unable to create landing data for a particular runway.  Typically this is due to a purposeful decision by the scenery designer when creating the runway (e.g., a "fake" runway to create multiple crosswind landing runways).  Note: AIController does NOT need to rely upon "fake" runways to provide cross-wind landings -- use the Force Landing Runways option instead).

 

NEW:  AIMonitor scenery decompile reads whether the primary and secondary (reciprocal) runways are closed to landings.  If so, no approaches/finals will be selected for that runway.  NOTE 1:  due to this new feature, AIMonitor now includes additional information in the taxi_graph.txt file, please perform a "Force Update of Runway and Taxi Data" in the options menu after installing this hotfix.  NOTE 2:  runway open/closed can be set by the user via the Airport Design Editor X.

 

NEW:  AIMonitor now also reads the left-pattern/right-pattern flags from scenery.  Thus, a new enhanced approach mode "2" has been added.  Mode 2 is the same as the old mode 1, except the configurable left-hand pattern *OR* right-hand pattern is chosen for each landing runway based on the scenery pattern flags (in contrast, the default mode 1 makes both the left-hand *AND* right-hand pattern available for each runway).  As always though, approaches converted from nav data (using the SIDSTAR converter) and user-written custom final approaches always take precedence over the generic (but configurable) left-hand/right-hand approaches regardless of mode.  NOTE 1:  due to this new feature, AIMonitor now includes additional information in the taxi_graph.txt file, please perform a "Force Update of Runway and Taxi Data" in the options menu after installing this hotfix.  NOTE 2:  pattern flags can be set by the user via the Airport Design Editor X.

 

NEW:  More gradual speed transitions on climb-out (especially when AIController takes over from FSX after takeoff) and descent.

 

NEW:  STAR/SID path statements in AIControllerList.txt are no longer required to contain "X" or "O" designators.  Instead, they can contain straight STAR= or SID= statements (interpreted as "X" or selected).  This will better facilitate bulk pasting of path statements, such as those generated by the SIDSTARConverter utility.

 

NEW:  User aircraft-AI anti-incursion feature highlighted to better remind user this option will help prevent incursions (e.g., preventing AI from landing on runway user is taking off from) BUT will also FREEZE AI and cause landing AI to GO-AROUND if necessary.

 

NEW:  No longer possible to run dual instances of AIController (prevents accidentially running more than one program at the same time).

 

NEW:  Additional absolute-paths (e.g., containing drive letter) to UNC network-path translation boxes added to Advanced Path Options menu (useful for networked AIMonitor installations).

 

Hot Fix 7 Fixes:

 

FIXED:  AI "turns" during taxi-in now much smoother.  Now the AI will roll through most turns (including rolling through a much faster runway exit).  AI will also slow down approach gate/parking.  IMPORTANT NOTE:  due to this fix, the default taxi-in options have been substantially changed.  After installation, please select "Options\Reset Options to Default" otherwise the "old" default options may cause poor results.

 

FIXED:  MT6 Scenery Issue - AI getting deleted at end of rollout.   AIMonitor decompiling older scenery incorrectly due to different parking codes being used in that scenery.  This affected some of the MT6 included .bgl files for various airports.  IMPORTANT NOTE: if affected by this bug, run a "Force Update" in AIMonitor after installing this hot fix to decompile the scenery with the correct parking codes.

 

FIXED:  Sometimes STAR-transition-approaches not working (i.e., preference was not given to selecting an approach having the same entry transition waypoint as the STAR exit waypoint the AI was assigned to) .

 

FIXED:  Sometimes AI was parking AI at gates already occupied by AI that previously taxi-in and parked.  Note: there is still a chance that FSX will inject a departure AI into the gate while the landed AI  is taxiing in.  In such a case, the taxi-in AI will now perform one last occupancy check when getting close to the assigned gate.  If AIController detects an AI has been injected into the gate, AIController will re-assign the gate for the taxi-in AI.  Finally, if for some reason the taxi-in AI ends up parked at the same gate as an injected "sleeping" AI, the taxi-in AI will be  deleted after parking at the gate for 60 seconds to clear the way for the injected AI to depart.

 

FIXED:  AI turns toward airport after being released from STAR.  After fix, AI will head directly to the assigned approach (enhanced mode only).

 

FIXED:  Speed additives due to wind were subtracted instead of added.

 

FIXED:  Some scenery designers insert inconsistent statements into the scenery.cfg file causing AIController to misinterpret scenery configuration (i.e., approaches not available).  

 

FIXED:  Some AI "freezing" after jetroute exit.

 

FIXED:  Fixed repetitive "Arriving AI is jet, but all STARs are for prop" message in non-enhanced mode.

 

FIXED:  Jetroutes sometimes not getting assigned between monitored airports.  STARs sometimes not getting assigned after jetroute exit when AI approaces a monitored airport.  NOTE:  Reduce the "No STAR if arriving AI further than this distance" in the basic options screen down from the default 200 nm to 75 nm (or so) if you wish arriving AI to fly the last portion of a jetroute before being assigned a STAR.

 

FIXED:  Minimum runway landing lengths (default) set too high.  This caused AIController to deem too many runways "too short" for the AI type (e.g., jet, tubroprop) making final approach unavailable.  Minimums (default) have been drastically reduced.  Perform "Reset Options to Default" to activate the new defaults.  The minimums are now probably unrealistically short, however it is easier to the user to increase them than wonder why final approaches aren't being selected (e.g., KMDW !!).

 

FIXED:  Sometimes the go-around pattern was not rectangular.

 

FIXED:  AIConv.exe utility sometimes not converting SIDs correctly.  A new AIConv.exe is included.  The full install version with hot fix 7 includes corrected SIDs (using the new version of AIConv.exe).  However, the hot-fix only version doesn't.  If you install the hot-fix only version, you may want to re-convert from nav data using the correct AIConv.exe (unless you're satisfied with the SIDs as is).  If you're using the SIDSTAR conveter utility, make sure to link it to the new AIConv.exe version.

 

FIXED:  Non-enhanced mode only:  Fixed several significant bugs, such as AI not lining up on final properly and making erratic movements after touchdown.  Also, short final release back to FSX (for normal animation) not working.

 

FIXED:  Verbose and Debug modes could not be set via AIMonitor or the .ini file.

 

New for Version 1.4B (Prior Revisions)

 

NEW:  Each AI's individual cruising speed during jetroute portion of flight determined from AI's aircraft.cfg data.

 

NEW:  Progress bar added for aircraft.cfg scan during update process.  Over a network connection, the AI aircraft.cfg scan may take longer than the actual scenery decompile process.  This discrepancy may lead the user to believe the "update" process has completed, when actually the aircraft.cfg data is still being written.  Thus, the new progress bar will help keep the user appraised.  Note:  If you had any problems with AI not getting assigned the correct gates in earlier versions, an incomplete aircraft.cfg scan might have been one of the causes.  Please install this hot fix and retry. 

 

NEW:  Specific support for My Traffic 6, including the non-ascii characters used in the ATC-IDs.

 

NEW:  Support for coordinated STAR-transition-approaches added (i.e., preference is given to selecting an approach having the same transition waypoint as the STAR exit waypoint the AI was assigned to). 

 

NEW:  Short-final go-around mode changed to standard left-base go-around pattern to make go-around patterns more coherent, reduce holding, and aid AI spacing. 

 

NEW:  Manually delete AI (or a group of AI(s)) by highlighting them in AIMonitor.  Highlight the AI(s) in the AIMonitor window, right-click, then choose delete.  This is similar to the old AI Traffic Explorer utility.  Good for deleting pesky AI that you can't get to with the FSUIPC zapper, but you can identify on the AIMonitor. 

 

NEW:  Persistent highlighting of selected AIMonitor rows.  This feature was added to support the delete option above, but has actually been requested several times by itself!  I presume the persistent highlighting will allow the user to better track particular aircraft. 

 

NEW:  Specify AI install directories outside of the FSX/P3D path.  In the config menu, advanced options.  Useful if an AI package has been installed to location outside the SimObject path.

 

NEW:  Absolute path to UNC path translator for Scenery.cfg.  In the config menu, advanced options.  Useful for when AIController is running on a networked client.  You can tell AIController the corresponding UNC path for any absolute path (e.g., a path containing a drive letter) appearing in the scenery.cfg.  As always, relative scenery paths (relative to the main FSX/P3D installation directory) are not a problem for AIController, so I recommend using relative paths if possible.  However, absolute paths are very useful for sharing scenery between different simulators (e.g., FSX and P3D).

 

NEW:  Manual Landing Runway(s) Selection:  If the user for whatever reason dislikes the current landing runway, which is based on prevailing winds, the user can instead enter up to three runways in AIMonitor to override all wind-based landing runway selections.  The AI will immediately switch to the new patterns, there will be no gradual transition.  When two runways are entered (e.g., 32L,32R), the load-balancing will be approx. 50-50.  When three runways are entered (e.g., 17C,18R, 18L), the load-balancing will be approx. 33-33-33.

 

NEW:  Max. Time Departing AI Remains Stopped on Taxiway Before Deletion.  Maximum time that AI taxiing OUT to the departure runway will be allowed to remained stopped on the taxiway before deletion (default 60 seconds).  Occasionally (even when not using AIController), departing AI becomes "stuck" just before runway entry holding up that AI and all the AI line-up behind it waiting.  This parameter will delete the AI that has become "stuck", allowing the AI behind it enter the runway and take off at a consistent rate.  The parameter cannot be used to increase waiting time higher than the FSX default value.  

 

NEW: AI Rollout Performance and Parking Based on AI's Aircraft.cfg File and ADE:  The AI rollout performance (e.g., braking distance) and parking preference (e.g., parking codes) are based on performance data in each AI's config file.  The parking algorithm has been revised to conform to typical FSX/P3D - ADE design methods (e.g., first AIController looks to gate radius, second AIControler looks to airline parking codes in the gate order as listed in the ADE parking list).  Version 1.4B automatically reads AI aircraft.cfg data to get each AI's braking, radius, airline code, etc. data, no user action is required.  Thus, the old GrabAIParkingCode utility is being retired.  An interesting note:  AIController will scan more than 5 airline codes per gate, thus eliminating the old FSX restraint.

 

NEW: Improved Landing Animations.  Consistent touchdown smoke, wheels (including nose-wheel) make firm contact with runway at correct angle, no more smoke effects when AI exits the runway and enters taxiway.  Touchdown smoke may be less prevalent at airports near sea level.

 

NEW: Special WinXP versions of AIController.exe and AIConv.exe are included in the distribution:  If you're running AIController in a networked configuration on an older laptop running WinXP, please use the AIController_WinXP.exe and AIConv_WinXP.exe files in the WinXP folder (see the readme in that folder for further instructions).

 

NEW: Latest version of SIDSTARConverter included, which allows you to select your preferred version of AIConv.exe.  The latest AIConv.exe is included in the AIController installation directory.

 

Prior Fixes for Version 1.4B:

 

HOTFIX 6:  (1) Incorrect parking assignments and double-parking based on duplicate gate numbers at different areas (terminals) of airports.  The fix also modifies AIController and AIMonitor to provide more detailed parking assignment information; (2) Gate radius data sometimes not processed correctly (AI-gate size mismatch); (3) Only one aircraft.cfg parking code being read (note: scenery gates typically have mulitple parkings codes, which was read by AIController, however the aircraft.cfg itself can also contain multiple parking codes, which is now being read and processed); (4) Parking alignment bug sometimes prevented AI from being designated "Parked at Gate" causing double-parking and preventing departure of same AI after waiting period (if auto-inject option enabled); (5) Sometimes AI obtaining high/low altitudes after being released from jetroute; (5) Turbojet Default Lower and Upper Jetroute Altitudes Bad.  Choose "Reset Options to Default" to activate corrected default values - OR - if you do NOT want to reset your customized options to default, go to "Options" - "Jetroutes" and change the "Turbojet Altitude Lower Range" to 18000 (or your own preferred value) and change the "Turbojet Altitude Upper Range" to 22000 (or your own preferred value), then press the "Apply" button.  Note: the bad default altitudes may have also caused-in-part the "AI obtaining high/low altitudes" bug above; (6) Scenery.cfg absolute-path TO UNC-network-path translator in Prepar3d mode isn't working.  Important for users running AIMonitor on a networked client machine because MyTraffic 6 places an absolute path (pointing to a folder shared by different FS programs) in the scenery.cfg; (7) Deletion routine for stalled taxi-out AI (i.e., AI not moving) fixed.  The routine was sometimes not deleting the longest waiting stalled AI (e.g., the stalled AI at the head of the line); (8) Sometimes AI not getting assigned jetroute after SID exit.

 

HOTFIX 5:  Not released (rolled into Hot Fix 6).

 

HOTFIX 4:  (1) Incomplete aircraft_cfg_data.txt file causing long rollouts and parking misassignments; (2)  AIController reading crosswind runways (Jim Vile-ADE technique) causing problems with final approach assignments after STAR exit.  Note: use force runway option in AIController to support crosswind and parallel operations; (3) High final approaches (AI was incorrectly and quickly transitioning from Jetroute to STAR to final leaving AI high on final close to airport); (4) AI parking alignment; (5) Not all AI parking codes being read causing parking misassignments; (6) AIController crashing reading some STAR/SIDS/Approaches converted from the latest navdata; (7) (Evaluating) AI start successively going-around for no apparent reason.

 

HOTFIX 3: (1) AI being deleted after rollout at some airports.  Problem was due to conversion error (parking radius stored in scenery files as meters, AI wingspan stored in aircraf.cfg files as feet); (2) AIController sometimes crashing because of bad taxi-graph read; (3) Multiple fixes for non-enhanced mode, including custom final approach/autogen files not being selected and AI disappearing/re-appearing in AIMonitor; (4) Waypoint updates can be made while FSX/P3D running.

 

HOT FIX 2:  (1) Expanded search for *.cfg files in all of the SimObjects subdirectories.  I don't have all AI add-on packages, so I suppose it is possible some package will have the AI reside outside Simobjects.  If so, let me know and I'll patch it up again; (2) Fixed continuing issue with repetitive "Scenery Change Detected" message and then AIMonitor attempting update waypoints at the same time it starts AIController; (3) Fixed bug where sometimes AIControllerPath.txt doesn't sometimes contain the "taxi=" paths even though the user just ran an update; (4) Revised code to support "My Document" paths to better support auto-injection of departing AI at monitored airport (to maintain departure rates if user remains at airport for long periods of time); (5) Extended "Force Landing Runway" to support 3 runways; and (6) Removed ability to keep the "Force Landing Runway" option to remain active across different AIMonitor sessions (to reduce the chance of accidentally keeping option enabled when switching airports). 

 

HOT FIX 1:  (1) Repetitive repetitive "VARIABLE WINDS or TIMEOUT waiting for wind direction data" message in AIController; (2) Fixed repetitive "Scenery Change Detected" when AIMonitor started for first time; (3) Jet, prop, and VFR ONLY STARs/SIDs not recognized.  This has been fixed, but jet, prop and VFR only patterns are now specified by "pattern type" instead of "pattern name" to maintain consistency with final approach pattern types.  Any custom user files that user the "pattern name" to specificy jet-only, prop-only, or VFR-only files will have to be modified so that "pattern type" is used instead (this should be an easy modification, see the readme.pdf for further details); (4) Duplicate line added to AIControllerPath.txt file; (5) Excessive error messages when attempting scenery scan, such as when program paths incorrect.  AIController will now limit the error messages to five when an unsuccessful scenery scan occurs; (6) Sometime AI didn't park at gate at correct heading.  This has been fixed; (7) Generic left and right base pattern names reversed.  This has been fixed; (8) Pattern entry points (enhanced generic left-right patterns) sometimes not the closest to AI's present position; (9) Some approach files converted from nav data contained missed approach data causing AI to perform missed approach procedure (go-around) when landing.  This has been fixed.  (10) Addon/scenery folder not being scanned when active in FSX/P3D (this is where use-generated ADE files typically reside!); (11) AI's landing runway displayed more consistently on AIMonitor; (12) Departing AI not being auto-injected at some airports; (13) Locale issue continuing to cause errors when comma-deliminated error.  For those users who switched affected by this error, please give this fix a try; (14) Quicker assignment of wind-based runway selection, less incorrect STARs that have to be re-assigned later

 

Important Revision:  A registered version (4.9x or later) of Peter Dowson's FSUIPC utility is recommended to use the full functionality of AIController.  For example, AIController will not be able to delete problematic AI targeted for removal (e.g., parked at gate after arrival for the specificed parking time).  For networked configuration users, Peter's WideFS (ver. 6.9) is also recommended.

 

Various other fixes/revisions were also made.

 

Important New NOTAMS!

 

ENTERING FINAL APPROACH COORDINATES.  Do not use FSX when entering final approach coordinates for runway positions (e.g., touchdown, rollout) as the FSX in-game coordinate display (shift-Z) lacks the necessary precision (significant digits).  Use the freeware Airport Design Editor X (or similar) instead.

 

ENTERING RUNWAY DATA.   Ensure the runway number corresponds to the FSX runway description (for whatever airport scenery you are using).  Often, the latest FMS data will reference changed runway numbers that do not correspond to stock FSX runway descriptions.  For STAR files, if the runways do not match (STAR versus FSX), AIController will choose the STAR based on the waypoint having the closest entry point to the AI’s current position (i.e., not based on runway data), which often is satisfactory, but not always.  For Final Approach files, if the runways do not match, AIController might choose the final approach file having the incorrect runway data.

 

Please see the Original Thread Post for Additional Details Regarding Ver. 1.4 Including Installation Video.

 

Thanks!

-Roland