I also noticed another odd thing. If a FlyTampa airport package (St. Maarten for example) has associated animated boats , they are considered as AI Traffic and are "taking off and landing" at some nearby fictitious airport.

Hi Roland

 

Now I have this weird problem AImonitor won't start up at all  :unsure:

 

I made a complete re-install and made all the path's and so.. but now it won't start up..

 

Dennis

Solved:

 

I just re-installed the program in a new directory.. Now it works and AImonitor starts up 

AIController is only searching the aircraft subfolder for aircraft.cfg files.

 

Thanks Roland, You've hit it !

 

I've copied my AI-aircratfs into the Airplanes-folder, made a data update and deleted after that the files as Jim has proposed. Now my AI_cfg_data.txt is complete and the aircrafts don't disapear after landing.

 

 

BTW, are you using a AI aircraft package?

 

No, I have collected tons of single nice AI-aircrafts by AIA, FSP. PAI, Evolve-AI, TFS, UTT etc., which were kindly provided by the developer.

 

However, looking forward, to discover the new features of AIC now.

 

Thanks again !

    Dietmar

In the options menu of AIMonitor, add the path to the folder in departure/approach paths, select the folder(s) you want active, then apply (and force update if you want to be safe).

I tired the Force update feature and AI Controller starts, configures, but just says FSX is PAused - AI Controller is Restarting and continually does so. Nothing else happens???

 

 

Another question....does the console state any reason why the go-arounds are happening (e.g,. incursion with AI taking off same runway)? 

 

I changed the value for detecting AI near the active down to 0.5 miles, and that seemed to make a difference. 

 

I am also having a problem getting the AI_config file to update - it's only gathering data on UI aircraft - and as a result, AI planes are being deleted at the end of their landing run. Could AI Monitor have an extra field added to show the location of AI aircraft? I had tried a work around, of searching my AI aircraft folder for all aircraft.cfgs, then copying them into \Simobjects\Airplanes and using Win 7s ability to rename multiple copies of the same filename. This didn't work.

 

I'm also not convinced version 1.4B is working well in my networked configuration, as it still only finds default taxiway information when searching scenery.cfg. I've worked around this by running AI Monitor on my FSX machine, then copying the relevant cfgs over to my server machine, and renaming paths contained therein as per UNC. I think this works, but it's quite a clunky way of getting there.

 

Now I can see what AI Controller can do, it's very impressive, and hopefully these little niggles listed above can be sorted out.

Rob

Hi Roland

 

Now again I have this weird problem AImonitor won't start up at all after i shut it down correctly.

 

I don't know why this happens.. Perhaps there is a bug in the program..

 

Dennis

No, it was the very first force I ever tried. A restart of FSX fixed this, but then I went to default KFSO and tried to force 28R, but planes continued to land on 28L. Yes I waited a very long time, like 45 minutes.

 

For the next hotfix, I'm trying to figure out how to implement this option while minimizing the chances of mishaps.  The problem is, if this option is accidentally left enabled at an airport the user is observing, things can appear to go haywire quickly.  For example, when the option is accidentally left enabled at an airport that doesn't have the runways specified in the force landing runway option, in a matter of minutes AIController can release dozens of AI back to FSX control because AIController can't find a runway matching the forced entry (it doesn't countermand the forced runway entry).

 

This is probably what you (and the other go-around reports) noticed.  Even when you entered 28L, the AI were probably already released back to FSX control, where they did their normal FSX go-around specialty.

 

 

 

Something else I noticed today: the data on the AIM screen never updates. I watched planes for an hour that were in the air but their data never changed. No, FSX was not paused!!

 

Did you try pressing "2. Start Data Collection" again?  Either that or AIController wasn't running.  In the hotfix, I'm limiting the number of menu options that stop data collection.  This could be related to the issue above, especially if AIController wasn't running.

 

-Roland

 

 

I also noticed another odd thing. If a FlyTampa airport package (St. Maarten for example) has associated animated boats , they are considered as AI Traffic and are "taking off and landing" at some nearby fictitious airport.

 

Did you happen to reduce the AIclimboutheight option?  I ask because a low AIclimboutheight in combination with the AI being in water may cause the behavior you're seeing.

 

-Roland 

 

 

Now I have this weird problem AImonitor won't start up at all 

 

Does AIMonitor start minimized (see the NOTAM in the readme) or does it not start at all?  If it doesn't start at all, what does the Microsoft application log say at the moment you attempted to start?

 

-Roland

 

 

I tired the Force update feature and AI Controller starts, configures, but just says FSX is PAused - AI Controller is Restarting and continually does so. Nothing else happens???

 

Seems like you have two AIController sessions running simultaneously, which won't work.   Either that or FSX was paused or a FSX menu open.

 

-Roland

 

 

I had tried a work around, of searching my AI aircraft folder for all aircraft.cfgs, then copying them into \Simobjects\Airplanes and using Win 7s ability to rename multiple copies of the same filename. This didn't work.

 

Yes, renaming multiple copies of the same filename won't work (contrary to my earlier instructions), you have to copy the entire folder structure into a temp folder as mentioned by Jim.

 

Anyway, the fix is almost ready, so might as well hold off any workarounds.

 

-Roland

Looking forward to the hotfix Roland.  Thanks for your efforts.

A new beta version of AIController v1.14B (full version including hot fix 2) is available at the following link:

 

http://www.mediafire.com/download/uk3zphsbz02u7mg/AIController14B.zip

 

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

 

http://www.mediafire.com/download/2hwd0lqsoqdbbsz/AIController14BHotFix2.zip

 

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

 

New for version 1.4B:

 

NEW:  Manual Landing Runway 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.

 

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.

 

Fixed for Version 1.4B:

 

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:  Repetitive repetitive "VARIABLE WINDS or TIMEOUT waiting for wind direction data" message in AIController.  Fixed repetitive "Scenery Change Detected" when AIMonitor started for first time. 

 

FIXED: 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).   

 

FIXED: Duplicate line added to AIControllerPath.txt file.

 

FIXED: 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.

 

FIXED: Sometime AI didn't park at gate at correct heading.  This has been fixed.

 

FIXED:  Generic left and right base pattern names reversed.  This has been fixed.

 

FIXED:  Pattern entry points (enhanced generic left-right patterns) sometimes not the closest to AI's present position.

 

FIXED:  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.

 

FIXED:  Addon/scenery folder not being scanned when active in FSX/P3D (this is where use-generated ADE files typically reside!).

 

FIXED:  AI's landing runway displayed more consistently on AIMonitor.

 

FIXED:  Departing AI not being auto-injected at some airports.

 

FIXED:  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.

 

FIXED: 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

Hi Roland

 

I don't get any error in the Microsoft App log.

 

AIMonitor starts minimized on the procesline with the icon.

 

When i click on the icon nothing happens..

 

BTW: The links above for the new hotfix is broken.. It says the files is deleted

Great stuff - thanks Roland, I'll give the latest version a try.

Hi Roland

 

I don't get any error in the Microsoft App log.

 

AIMonitor starts minimized on the procesline with the icon.

 

When i click on the icon nothing happens..

 

BTW: The links above for the new hotfix is broken.. It says the files is deleted

 

Like Roland says, read the NOTAM readme he included with the package.  It tells you how to fix it.  I'm not at home now, but it involves hitting Alt-Space if I remember correctly.

BTW: The links above for the new hotfix is broken.. It says the files is deleted

 

Thanks, unfortunately I am going to have to re-post the whole message (with the new links) because the edit time has expired.  Regarding AIController starting minimized (as Devin mentioned) press Alt + Space to get a menu.  Then select the option to maximize the Window.

 

-Roland