Search the Community

A new beta version of AIController v1.14A is available at the following link: http://www.mediafire.com/download/eabrmvqdt9kc62x/AIController14A.zip Please do not mix with any version of 1.3 or earlier. Instead, install into a separate directory for testing. Ver 1.4 contains significant new features and as a result, the windows-based AIMonitor.exe program was revamped to become the central point for managing these new features. I no longer recommend manually editing the .ini files. New: Ver 1.4 now reads taxi and runway data from installed default and add-on scenery (i.e., the "Enhanced" approach mode). It uses this data to automatically generate final approaches and taxi service to the gate. Thus, the prior and troublesome requirement that FSX AI intercept a generically placed approach fix waypoint no longer applies. As a result, the AI can now fly tight generic approachs (configurable by the user in AIMonitor) or real-world final approaches either converted from navdata (SIDSTAR converter) or custom-written by the user. These predictable final approches also provide for better separation control. Several options have been added to AIMontior to adjust enhanced approach and taxi operations. New: The SIDSTAR converter has been updated to convert APPROACH (as well as SID and STAR) data into a format readable by AIController. As a result, the AI can now be easily configured to fly published SIDs, jet routes, STARs and approaches (including the final portion) at monitored airports. New: Taxi to gate after arrival include basic collision avoidance with other AI and with AI landing on crossing runways. New: Taxi to gate after arrival selects based on airline code (from AI .cfg file) if possible. If not, AIController will make intelligent decisions as to where to park the AI. New: Grab parking codes utility to automatically read and store airline parking codes from all install AI .cfg for use by AIController (for parking operations). New: Crosswind AI correction effects have been added for AI on final approach during strong cross-wind conditions. New: AIController now recognizes "heavy" AI and will lengthen their rollout accordingly (note: rollout lengths can also be controlled in the AIMonitor as before). New: AIController performs load-balancing on multiple landing runways at busy airports when applicable. New: The AIMonitor now includes pop-up help text explaining each parameter. New: Most options can now be changed via the AIMonitor while AIController is running. For example, think the AI is taxiing too slowly to the gate? You can go into AIMonitor and adjust the taxi speed upward. The changes will take effect in the current FSX session. Path options (e.g., which airport to monitor cannot be changed during the FSX session because these relate to waypoints that must be read from the scenery before the FSX session begins). New: ICAO display filter added to AIMonitor in case you want to concentrate on just one airport. Improved: AI landing animation now includes spoiler deployment and smoke if a hard touchdown. Light operation is also correct for final approach, landing, taxi and parking. Improved: Crosswind AI correction effects have been added for AI on final approach during strong cross-wind conditions. Improved: While flying, AI groundspeed affected by winds aloft (e.g., headwinds) (i.e., indicated airspeed differs from groundspeed). Improved: Many bug fixes and performance improvements. 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 are 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. Installation and Basic Usage Video for Version 1.4: Demo (older AIController Version, but still useful): Link to old thread (ver 1.3B): http://forum.avsim.net/topic/447974-ai-controller-sid-jet-route-star-and-final-approach-beta/ Thanks! -Roland