Clipper Ocean Spray

Unfortunately that feature has gone away with the forum upgrade. Not sure what to do to get the latest hot fix link front and center?

Re: 2 and 4, give the latest hotfix a try. For 2, I think this was caused by excessive banking at too slow of an approach speed. For 4, throttle takeoff percent setting in AIMonitor was broken, should be working now. For 4, yes, I need to look at that section of the code again...I've seen it too. -Roland

Okay, thanks for clearing it up. -Regards, Roland

Hi, I have a couple of active support threads going for a freeware beta I'm conducting (AIController). Does anyone know how to mark "best answer" using the new forum software so that it appears at the top of the thread? When I make the latest version available, I post a message and mark it as "best answer" so that users can get to it easily without having to search deep into the thread. Apologies in advance if this is a well-known feature of the new software. Thanks! -Roland Foster

HOT FIX 4 - IMPORTANT - Lots of new stuff in this hotfix...after installing "Reset Options to Default" under "Settings"! AIController Hot Fix 4 Only Link: http://www.mediafire.com/file/2km63lj55byv501/AIControllerV2OnlyHF4.zip New Features Added third party ATC support: See "AIMonitor 3rd Party Output" in general options. Also added "AIMonitor Monitor Table Update Interval" in same location to reduce CPU resources of the AIMonitor when writing to both the display table and to 3rd party program. Also improved multi-threading in AIMonitor. Added option to "slew" AI during flight (similar to the old ver. 1.4), which some users prefer ("Provide Slew for ALL Approaches and Departures" in "Settings/Options/General Options" window). Provides better AI flight path precision at the expense of realistic flight characteristics (the AI will not be "flown"). New go-around mode (based on improved detection of AI circling way points described below) that detects unstable approaches to way points on short final (e.g., the typical 500 ft way point just before touch down). Improved Much less porpoising during banks and pitch changes (for certain AI with less than ideal flight characteristics). Improvements due to: (1) pitch and bank angle fast centering (which can be turned off - see the "Bank and Fast Pitch" option under "Settings\Options\Flight Dynamics"); and (2) improved aileron and elevator dampening (note: not used in crosswind landings of greater than 10 knots) (note: bank and pitch dampening will gradually calibrate as AIController learns the flight dynamics of each particular AI...AI should exhibit a very stable final approach unless crosswinds in which case excessive control authority is maintained to get AI onto runway). Improved detection of AI circling way points due to the way points being poorly placed (e.g, too close together at too great an angle) and corrective action (applicable during all phases of flight). Better emergency terrain avoidance added. Fixed AI not holding to service ceilings ("Flight Dynamics" options window) when there are no waypoint altitude constraints. AI sometimes landed on runways considered too short according to runway length restrictions by AI type ("Approach and Final Options" window). AI rarely performed straight-in approach (if generic approach patterns used) even when appropriate AI push back sometimes taking too long. Departing AI stall on runway (just before takeoff roll out) when jet routes are active. Jetroutes option enabled sometimes causes AIController to crash. "Engine Type Wrong for Landing Runway" message was sometimes repeating. "Parking Found ...." message was sometimes repeating after AI finished landing roll out causing AI not to taxi in. AI stopping too long after turns when using the AI turn slew assist option ("Assist AI with Slew During Sharp Turns" option in the "Taxi Performance" options window). AI sometimes taxi into each other when going in same direction. (Note: no collision detection yet for AI going in different directions, e.g., taxi out v. taxi in)). AI circling sometimes around jet route waypoints. AI Controller gives too many broken link warnings (e.g., "failed to build approach for...) when a large number of airports are monitored. Fix is after five of the same type errors only summary info. Wile given. AI Cull Mode 4 does not work. UT2 compatibility fixed. If enabled prevents AI not departing from or arriving at monotone during airport from being vectored by AI Controller(I.e. preserves UT2 jet Routes). AI lands or takes off while other AI on runway (can't say it is completely fixed but should be better). User aircraft causing AI to be deleted even when user's landing lights are off (user-AI anti-incursion option in "Additional Final Options and Anti-Incursion"). AI sometimes landing on nose wheel. AI losing altitude between STAR exit and IAF point. "Both" option in "Force Landing Runways" option not working for departing AI. Enhanced generic approach improperly selected even when a NAV data based approach (e.g., STAR) was active. AI too slow when AI commanded to slow down in generic pattern (causing altitude loss and lack of control authority during turns). "Throttle Takeoff as Percent of Max" option under "AI Flight Dynamics" wasn't working (used to adjust length of takeoff roll). Landing rollout distance too short. AIController memory leak (under certain circumstances) Speed loss during final approach during transition to landing configuration (e.g., deploying gear and landing flaps). AI sometimes turns too late during taxi. AI not descending to holding alt during holding turns. Tear-drop procedure causing too many go-arounds with other AI not conflicting (this was due to the circling procedure the AI used during the tear drop). Unidirection taxi links given more weighting for better effect (see "Enable Taxi Direction Links" in "Taxi Options" window) (note: must be supported by scenery or unpredictable results may occur!). Modifications Changed these default taxi values in the "Settings\Options\Taxi Options" menu (be sure to apply "Reset Options to Default" after updating to this hot fix!). "Taxi Minimum Angle Difference (deg.) Before Possible collision Detect": 45 deg. "Taxi Minimum Separation (feet) Before Possible Collision Detect": 350 meters "Max. Bearing to Runway Exit Waypoint to Trigger Runway Exit (degrees)": 95 "Min. Distance to Rwy Exit Waypoint to Trigger Runway Exit (feet)": 25 Changes these default user-AI anti-incursion options in the "Settings\Options\Additional Final Options and Anti Incursion" menu (be sure to apply "Reset Options to Default" after updating to this hot fix!). "Anti-Incursion Threshold Altitude": 0 (i.e., disabled - I much prefer this feature enabled myself, but I get too many questions about why AI is getting deleted on short final). Important NOTAMS! DO NOT OVERLAY a second window for an extended period of time while watching AI. Use one of the AI view options. For best results, start AIController BEFORE loading flight especially if you experience taxi issues (e.g., AI's wheels don't rotate). 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 If installing ver. 2 for the first time, be sure to uninstall all prior version of AIController before installing this version (backup first). If installing hot fix only, simply overwrite the older files with the newer files. After installing "Reset Options to Default" under "Settings"! Read the ReadMe1st.txt file (quick) and optionally the ReadMe.pdf file (more details). Also, see the Installation and Basic Usage Video for Version 2 (below): https://youtu.be/DeTe3LK_q4Y -Roland

HOT FIX 4 - IMPORTANT - Lots of new stuff in this hotfix...after installing "Reset Options to Default" under "Settings"! AIController Hot Fix 4 Only Link: http://www.mediafire.com/file/2km63lj55byv501/AIControllerV2OnlyHF4.zip New Features Added third party ATC support: See "AIMonitor 3rd Party Output" in general options. Also added "AIMonitor Monitor Table Update Interval" in same location to reduce CPU resources of the AIMonitor when writing to both the display table and to 3rd party program. Also improved multi-threading in AIMonitor. Added option to "slew" AI during flight (similar to the old ver. 1.4), which some users prefer ("Provide Slew for ALL Approaches and Departures" in "Settings/Options/General Options" window). Provides better AI flight path precision at the expense of realistic flight characteristics (the AI will not be "flown"). New go-around mode (based on improved detection of AI circling way points described below) that detects unstable approaches to way points on short final (e.g., the typical 500 ft way point just before touch down). Improved Much less porpoising during banks and pitch changes (for certain AI with less than ideal flight characteristics). Improvements due to: (1) pitch and bank angle fast centering (which can be turned off - see the "Bank and Fast Pitch" option under "Settings\Options\Flight Dynamics"); and (2) improved aileron and elevator dampening (note: not used in crosswind landings of greater than 10 knots) (note: bank and pitch dampening will gradually calibrate as AIController learns the flight dynamics of each particular AI...AI should exhibit a very stable final approach unless crosswinds in which case excessive control authority is maintained to get AI onto runway). Improved detection of AI circling way points due to the way points being poorly placed (e.g, too close together at too great an angle) and corrective action (applicable during all phases of flight). Better emergency terrain avoidance added. Fixed AI not holding to service ceilings ("Flight Dynamics" options window) when there are no waypoint altitude constraints. AI sometimes landed on runways considered too short according to runway length restrictions by AI type ("Approach and Final Options" window). AI rarely performed straight-in approach (if generic approach patterns used) even when appropriate AI push back sometimes taking too long. Departing AI stall on runway (just before takeoff roll out) when jet routes are active. Jetroutes option enabled sometimes causes AIController to crash. "Engine Type Wrong for Landing Runway" message was sometimes repeating. "Parking Found ...." message was sometimes repeating after AI finished landing roll out causing AI not to taxi in. AI stopping too long after turns when using the AI turn slew assist option ("Assist AI with Slew During Sharp Turns" option in the "Taxi Performance" options window). AI sometimes taxi into each other when going in same direction. (Note: no collision detection yet for AI going in different directions, e.g., taxi out v. taxi in)). AI circling sometimes around jet route waypoints. AI Controller gives too many broken link warnings (e.g., "failed to build approach for...) when a large number of airports are monitored. Fix is after five of the same type errors only summary info. Wile given. AI Cull Mode 4 does not work. UT2 compatibility fixed. If enabled prevents AI not departing from or arriving at monotone during airport from being vectored by AI Controller(I.e. preserves UT2 jet Routes). AI lands or takes off while other AI on runway (can't say it is completely fixed but should be better). User aircraft causing AI to be deleted even when user's landing lights are off (user-AI anti-incursion option in "Additional Final Options and Anti-Incursion"). AI sometimes landing on nose wheel. AI losing altitude between STAR exit and IAF point. "Both" option in "Force Landing Runways" option not working for departing AI. Enhanced generic approach improperly selected even when a NAV data based approach (e.g., STAR) was active. AI too slow when AI commanded to slow down in generic pattern (causing altitude loss and lack of control authority during turns). "Throttle Takeoff as Percent of Max" option under "AI Flight Dynamics" wasn't working (used to adjust length of takeoff roll). Landing rollout distance too short. AIController memory leak (under certain circumstances) Speed loss during final approach during transition to landing configuration (e.g., deploying gear and landing flaps). AI sometimes turns too late during taxi. AI not descending to holding alt during holding turns. Tear-drop procedure causing too many go-arounds with other AI not conflicting (this was due to the circling procedure the AI used during the tear drop). Unidirection taxi links given more weighting for better effect (see "Enable Taxi Direction Links" in "Taxi Options" window) (note: must be supported by scenery or unpredictable results may occur!). Modifications Changed these default taxi values in the "Settings\Options\Taxi Options" menu (be sure to apply "Reset Options to Default" after updating to this hot fix!). "Taxi Minimum Angle Difference (deg.) Before Possible collision Detect": 45 deg. "Taxi Minimum Separation (feet) Before Possible Collision Detect": 350 meters "Max. Bearing to Runway Exit Waypoint to Trigger Runway Exit (degrees)": 95 "Min. Distance to Rwy Exit Waypoint to Trigger Runway Exit (feet)": 25 Changes these default user-AI anti-incursion options in the "Settings\Options\Additional Final Options and Anti Incursion" menu (be sure to apply "Reset Options to Default" after updating to this hot fix!). "Anti-Incursion Threshold Altitude": 0 (i.e., disabled - I much prefer this feature enabled myself, but I get too many questions about why AI is getting deleted on short final). Important NOTAMS! DO NOT OVERLAY a second window for an extended period of time while watching AI. Use one of the AI view options. For best results, start AIController BEFORE loading flight especially if you experience taxi issues (e.g., AI's wheels don't rotate). 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 If installing ver. 2 for the first time, be sure to uninstall all prior version of AIController before installing this version (backup first). If installing hot fix only, simply overwrite the older files with the newer files. After installing "Reset Options to Default" under "Settings"! Read the ReadMe1st.txt file (quick) and optionally the ReadMe.pdf file (more details). Also, see the Installation and Basic Usage Video for Version 2 (below): https://youtu.be/DeTe3LK_q4Y -Roland

Bob, the P3Dv3 machine is the server and the client is the computer where AIController is installed. Check out the readme.pdf file, which has some tips about how to get it up an running. You only need to install the client installer (found in the P3D Simconnect SDK folder) on the client machine, not full simconnect. Here's a good rundown: http://nimbus.hifitechinc.com/ASNInfo/ASN_User_Guide.pdf#page=81

1) will check this. What AI set are you using? 2) good idea, thanks. 3) perhaps look for Aircraft Airfile Manager by Karl-Heinz Klotz 4) you can adjust "Throttle Takeoff as Percent of Max" downward in AI Flight Dynamics to increase the takeoff roll.

Hey guys, I would suggest using ver. 2 as I'm actively supporting that version and eventually it should have similar capabilities to ver. 1.4. http://www.avsim.com/topic/498931-ai-controller-20-gate-to-gate-control-open-beta/

I have FSDT JKFv2, but I haven't seen this. However, you mentioned that the AI was slewing so perhaps it was one of the extreme approaches (e.g,. visual 13L or 13R) where slew mode is enabled on the approach. If you disable the slew approaches (you can move them into a subdirectory named "inactive" and they won't be read) do you still see this? Anything better with HF3?

Ahh...I see...thanks for posting that. Unfortunately AIConverter only converts waypoint-based procedures. So a procedure that states climb heading X until altitude Y with no waypoints is not recognized. A work around is to program your own procedure using waypoints to approximate the general location where the AI should be at a certain altitude, then add another waypoint that causes them to turn to a particular heading. Hopefully the first and third issues are improved with HF3. Regarding the second issue, are you starting AIController before or immediately after the session is loaded? If there is a delay, some AI will push-back and start their taxi before AIController can start controlling them. Once that happens, they will not be controlled even when AIController loads. This might be something I can improve in a later version, I'll look into it. HF3 was targeted to many of these issues, can you give me an update using HF3? As it stands now, the AI's wheels may clip the grass here or there but it should not be a big problem. They should roll through the corners better. Understood regarding cull method 4, haven't got to the fix for that yet, but will. Sorry, one of the links was bad...try again and it should work.

Would it just be easier not to have AIController monitor the airport? BTW...what airport (hopefully stock) is this happening, I can take a look. I've noticed this too for certain aircraft. I'll have to revisit that code and account for this. In the meantime you can turn the anti-incursion options off or increase the minimum distance. Yes, I'll probably add the full slew option back (as mentioned above), but the "fly" mode should be getting better both in the air and on the ground using Hot Fix 3. As it stand now (HF3) on the ground, when AIController is using engine power/brakes/tiller (non-slew) to taxi, the AI may clip the grass now and then and go wide on turns, but you should not be seeing any wholesale taxiing on the grass or looping. If you are, please let me know the airport (preferably stock) and the location and I will try to replicate it. I don't think that feature of SIDSTAR Converter is used anymore. Just use the SIDSTAR Converter "organize by state/provinces/regions," option, then you can easily point to the state/province/region top-level folder in AIMonitor and it will automatically read all the subdirectories. The AI stability on final and early runway exit after landing should be improved in HF3, please give that a try. I've had other reports of the AI sometimes getting stuck before entry onto the runway in use...I'm looking into it.

Thanks for the update. Yes, there is some stuff happening regarding this. The most immediate action I'm taking will be to add an output option that replicates FSX/P3D traffic manager so that the traffic states of AI under control of my program can be determined in a standard way by any 3rd party program that wants to read it. Anyone else seeing this (using HF3)? I didn't mention it in the update by a made a small stability fix that sometimes caused AIController to crash (but not FSX/P3D as far as I can tell). Wow, it takes 30 minutes to start? You might want to monitor only airports in the area of the world where you are currently flying. It isn't necessarily an error, some stock airports in FSX/P3D don't have any taxiways others have taxiway link errors. Others have complained into there's too much info. about this issue when AIController loads. The original idea was to warn the user that some monitored airports will not be monitored because of taxi link issues, but I undertsand that if you're monitoring hundreds of airports, this info. quickly starts to get repetitive and not useful. I'm looking into it. Okay, I'll look into it. There's a backend way for doing it now, by making sure slew assist is ticked and modifying other taxi options so that slew assist kicks in quickly. Also, all STARs and finals can be directed to use slew mode by adding the slew override to the files (e.g., see the KDCA example files) Obviously right now I'm spending a lot of development time getting the fly mode more precise, what are your thoughts regarding HF3, do you see improvements?

Note: edited for bad file download link. Here's the links to the latest update (Hot Fix 3 only): HOT FIX 3: http://www.mediafire.com/file/01s3vke6qjqhi50/AIControllerV2OnlyHF3.zip If anyone needs the full install (Hot Fix 1), it is available at: HOT FIX 1 (full): http://www.mediafire.com/file/5vk15b44rl5vd1m/AIControllerV2FullHF1.zip Again, I'm in-and-out the next week due to personal reasons, but I will try to catch up on the questions. Fixed: Tear-drop procedure (when intercepting final approach fix at obtuse angles) works better. E.g., no altitude loss, less go-arounds. New/Improved: AI chooses better off-ramp after landing rollout, taxiing faster and evacuating runway more quickly. New/Improved: Better flight characteristics and smoother landings (due to better capabilities of autopilot to self-calibrate to individual AI flight characteristics). New/Improved: Increased throttle smoothness including better speed control. Changed: AI will taxi under control of throttle, brakes and steering at all times (no slew assist) is now default setting - be sure to reset options to default if unsure how to change this. Fixed: Other minor items. If you reported a bug or suggestion and it is not included here, I probably just haven't got to it yet. Please feel free to raise the same issue if you feel something is falling through the cracks. The next update will focus on taxi smoothness. -Roland

Here's the links to the latest update (Hot Fix 3 only): HOT FIX 3: http://www.mediafire.com/file/01s3vke6qjqhi50/AIControllerV2OnlyHF3.zip If anyone needs Hot Fix 1, which has the full install, is available at: HOT FIX 1 (full): http://www.mediafire.com/file/5vk15b44rl5vd1m/AIControllerV2FullHF1.zip Again, I'm in-and-out the next week due to personal reasons, but I will try to catch up on the questions. Fixed: Tear-drop procedure (when intercepting final approach fix at obtuse angles) works better. E.g., no altitude loss, less go-arounds. New/Improved: AI chooses better off-ramp after landing rollout, taxiing faster and evacuating runway more quickly. New/Improved: Better flight characteristics and smoother landings (due to better capabilities of autopilot to self-calibrate to individual AI flight characteristics). New/Improved: Increased throttle smoothness including better speed control. Changed: AI will taxi under control of throttle, brakes and steering at all times (no slew assist) is now default setting - be sure to reset options to default if unsure how to change this. Fixed: Other minor items. If you reported a bug or suggestion and it is not included here, I probably just haven't got to it yet. Please feel free to raise the same issue if you feel something is falling through the cracks. The next update will focus on taxi smoothness. -Roland

Here's the links to the latest update (Hot Fix 3 only): HOT FIX 3: http://www.mediafire...erV2FullHF1.zip Again, I'm in-and-out the next week due to personal reasons, but I will try to catch up on the questions. Fixed: Tear-drop procedure (when intercepting final approach fix at obtuse angles) works better. E.g., no altitude loss, less go-arounds. New/Improved: AI chooses better off-ramp after landing rollout, taxiing faster and excavating runway more quickly. New/Improved: Better flight characteristics and smoother landings (due to better capabilities of autopilot to self-calibrate to individual AI flight characteristics). New/Improved: Increased throttle smoothness including better speed control. Changed: AI will taxi under control of throttle, brakes and steering at all times (no slew assist) is not default setting - be sure to reset options to default if unsure how to change this. Fixed: Other minor items. If you reported a bug or suggestion and it is not included here, I probably just haven't got to it yet. Please feel free to raise the same issue if you feel something is falling through the cracks. The next update will focus on taxi smoothness. -Roland

Here's the links to the latest update (Hot Fix 3 only): HOT FIX 3: http://www.mediafire...erV2FullHF1.zip Again, I'm in-and-out the next week due to personal reasons, but I will try to catch up on the questions. Fixed: Tear-drop procedure (when intercepting final approach fix at obtuse angles) works better. E.g., no altitude loss, less go-arounds. New/Improved: AI chooses better off-ramp after landing rollout, taxiing faster and excavating runway more quickly. New/Improved: Better flight characteristics and smoother landings (due to better capabilities of autopilot to self-calibrate to individual AI flight characteristics). New/Improved: Increased throttle smoothness including better speed control. Changed: AI will taxi under control of throttle, brakes and steering at all times (no slew assist) is not default setting - be sure to reset options to default if unsure how to change this. Fixed: Other minor items. If you reported a bug or suggestion and it is not included here, I probably just haven't got to it yet. Please feel free to raise the same issue if you feel something is falling through the cracks. The next update will focus on taxi smoothness. -Roland

Just to follow up based on what another user reported (he actually reminded me)...this could be caused by the user aircraft near the AI in a takeoff config (e.g., landing lights and strobe lights on and less than on 10 kts). This option can also be changed/disabled in the Anti-incursion window. No...I'll look into it (I know I'm saying "I'll look into" a lot..but it helps me document issues I need to look into at a later time!).

Thanks for passing that info. along, will check it out Could be a problem with one of the SID/STAR files, start in verbose mode (AIMonitor) and see if it crashes while reading a particular file. Noted...yes some options are intentionally not configurable in AIMonitor. Is this KSLC default? I'll take a look. Thanks for taking a look at this...can you email me your custom final file? I do have the Aerosoft EDDF airport I can test it at.

(1) Yes, you define a monitored airport in AIMonitor by (1) entering the ICAO for the airport (for generic patterns) or specifying a SID/STAR/approach/final files for the airport (e.g., files generated by the SIDSTAR Converter after converting nav data). (2) What were the options you entered (from top to bottom)? I'll check it out. Could be a bug in the AICull feature. Quite alright...seems like it could be an AICull bug...what AICull settings were you using? Were you using any of the FSUIPC cull features? I have both of those airports, so we should be able to get to the bottom of this.

No, I would use the "force arrival and departure" runways feature in AIMonitor for complex airports with more than one crosswind runway. Regarding (1), please check out hot fix 2 (make sure to turn slew-assisted turns off and reset any taxi performance tweaks). Regarding (2) and (3), I have received several reports of this, will look into this for the next fix. Regarding (4), throttle variation should be much improved for hot fix 2. Thanks, will look into it. Yes, is there a stock UK airport this is happening at (I ask because it is easier for me to test)? Is AIController outputting any text to the console window regarding the problematic AI when the nose-dive occurs? One way to track this more easily is to reduce AI traffic density so that it is easier to track AI status (less text to track in the AI console window). Also, please zip up and send the AIControll.ini, AIControllerPath.txt, AIControllerList.txt and taxi-graph.txt file to me at AIController2 (at) gmail.com Regarding (1), not familiar with the new traffic cull feature of FSUIPC, but glad to hear it, I'll have to check it out! I would say whichever cull feature (FSUIPC or AIC) suits your needs better, use that and turn the other one off. Regarding (2), probably these settings (from top-to-bottom in the AI Custom Traffic Density window): 2,40,0,1,0 Regarding (3), in the Options\General Options window, increase AI Climbout Height for Vectors (feet AGL) from the default value of 500 to something higher. Regarding (4), I would use the SIDSTAR Converter program and click the "Organize procedures into State/Provinces Folders" to make it all easier to organize. Then disable those States/Provences in AIMonitor that you're flying nowhere near. Although you can enable everything...it will use a lot of main memory (which your computer probably has plenty of - it will not consume any extra FSX/P3D virtual address space) and more CPU occupancy (due to increase table lookups). If you're running on a network computer, it won't be a problem. I would just say for your favorite airports, I would spend some time to see how the traffic flows and tweak accordingly (e.g., modify/delete the converted procedures you don't like).

Yes, I could have swore AIMonitor used to do that (support nothing for enabled and "//" for disabled for the very same reasons you mentioned ). I'll check and try to add this feature. Network configuration is difficult....the most complaints I receive are due to absolute paths (e.g., C:\P3D Apps\....) being used in scenery config. I have an absolute path-to-UNC translator in the advanced path options, but it is still tedious to get everything translated. A problem with just relying on the computer name (e.g,. //SIM2) for UNC is that people tend to give shared folders short names (e.g., \\SIM2\P3D) that don't correspond to their actual local path (e.g., C:\P3D Apps\Lockheed Martin\Prepar3D v3). Yes, just watch the video linked in the original post. That makes it seem like AIController isn't reading the correct scenery file...what is listed for the "TAXI=LTBA,...." entry in AIControllerPath.txt? Also, make sure you're not watching AI using an overlayed window (e.g., a second window). Regarding (1), hopefully hotfix 2 improves this situation. Regarding (2) and (3), is there landing traffic nearby? Departing AI less than the runway anti-incursion distance (default is 2.5 nm) from arriving AI will prevent that departing AI from crossing any hold-shorts. The AIController command window will output updates like "The AI on the ground will be commanded to STOP until incursion cleared." If so, reduce the default distance to see if that helps. Probably need to clarify this in AIMonitor, which suggests anti-incursion only applies to AI vying for the same runway. Regarding (4)...got it, will fix. This should be a lot better with hot fix 2 (make sure to turn off "slew-assisted turns" in the taxi options though and you may also need to reset you taxi settings -- after exporting/saving your old settings -- back to default). If I grow confident with the new taxi capabilities I may eventually make slew-assisted turns default off.

Here's the links to the latest update (Hot Fix 2 only): HOT FIX 2: http://www.mediafire.com/file/65kg2tan235c9an/AIControllerV2OnlyHF2.zip If anyone still needs Hot Fix 1 (full install), it is available at: HOT FIX 1 (full): http://www.mediafire...erV2FullHF1.zip I'm pushing this hot fix out a little early as I'm in-and-out the next week or so due to holidays and wanted to get an update out. Many changes under the hood having to do with taxi and throttle smoothness. However, I'm aware that the AI on average is landing a little harder with this hot fix (I'll get around to tweaking that). New/Improved: AI will now taxi more smoothly including rolling through turns. Must use the new "option" to disable all slewing during taxi options in "Settings/Options/Taxi Options/Assist AI with Slew during Sharp Turns." This option must be disabled to make the AI taxi under engine power/brakes/tiller during all phases of taxi. New/Improved: Increased throttle smoothness including better speed control. Fixed: Better runway selection based on wind direction (sometimes selected runway did not best match wind direction). Fixed: Sometimes AI would fly too high when using the optional generic approach patterns. Fixed: Other minor items. If you reported a bug or suggestion and it is not included here, I probably just haven't got to it yet. Please feel free to raise the same issue if you feel something is falling through the cracks. The next update will focus on taxi smoothness. -Roland

Here's the links to the latest update (Hot Fix 2 only): HOT FIX 2: http://www.mediafire.com/file/65kg2tan235c9an/AIControllerV2OnlyHF2.zip If anyone still needs Hot Fix 1 (full install), it is available at: HOT FIX 1 (full): http://www.mediafire...erV2FullHF1.zip I'm pushing this hot fix out a little early as I'm in-and-out the next week or so due to holidays and wanted to get an update out. Many changes under the hood having to do with taxi and throttle smoothness. However, I'm aware that the AI on average is landing a little harder with this hot fix (I'll get around to tweaking that). New/Improved: AI will now taxi more smoothly including rolling through turns. Must use the new "option" to disable all slewing during taxi options in "Settings/Options/Taxi Options/Assist AI with Slew during Sharp Turns." This option must be disabled to make the AI taxi under engine power/brakes/tiller during all phases of taxi. New/Improved: Increased throttle smoothness including better speed control. Fixed: Better runway selection based on wind direction (sometimes selected runway did not best match wind direction). Fixed: Sometimes AI would fly too high when using the optional generic approach patterns. Fixed: Other minor items. If you reported a bug or suggestion and it is not included here, I probably just haven't got to it yet. Please feel free to raise the same issue if you feel something is falling through the cracks. The next update will focus on taxi smoothness. -Roland

1. Okay, I'll look into engine oscillations some more. Any luck experimenting with the Throttle Gain, Lag, and Max options? 2. This will tend to happen more at the beginning, when the situation is first loaded and arriving AI are spawned very close to the airport. Also, if this seems to be happening for a particular nav-data based approach, it could be the approach itself wasn't a good conversion. You could try to manually tweak it or delete it relying on another nav-data based approach for the same runway. Also, there was a bug in the original version when AI perform a tear-drop to join final when approaching the fix at an obtuse angle...part of the bug involved the AI losing alt. 3. Yes, I've seen this and will get it fixed. Good idea...AIC is heavily multi-threaded, so could be very useful to users who want to make sure these threads stay on certain non-sim processors.