Clipper Ocean Spray

AI Controller 2.0 (Gate-to-Gate https://www.avsim.com/forums/topic/498931-ai-controller-20-gate-to-gate-control-open-beta/Control) Open Beta

Recommended Posts

It's not ..........'canned chatter'

canned chatter, a great description.

 

i thought that was what vololiberista was writing about. AI pilot/controller i call comms.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I didn't come up with the description :sad:

 

Canned chatter are samples of whole ATC transmissions, most of the time not fitting the situation in the game. PF3 has that option, but it also offers chatter that is put together with small samples, like FSX' built-in ATC. Not as smooth, but pertinent to what's happening out there. But this is getting off-topic...

Share this post


Link to post
Share on other sites

team

 

am a novice with AIC ...

 

using UT2 @ KSFOHD, I notice AI traffic taxy out to the holding point, then when lining up for take-off, they start going in circles about the runway "start".

 

can't see a similar user experience listed here on avsim.

 

any clues would help.

 

Have seen the same behavior and also at Flightbeam's KSFOhd. Most of the AI went their merry way to the runway but some indeed were going in small circles, sometimes even direct after pushback. But I do not use UT2.

 

Worse was that my Aivlasoft got currepted after install of AI-controller 2.0. Got advice on their forum and some files had to be removed in order to rebuild.

 

Hope these bugs can be wrinkled out !

 

thx / Dick

=

Share this post


Link to post
Share on other sites

Anyone know what this means?

 

The AI Controller has connected to Flight Simulator or P3D

FSUIPC Link Established

 

AICONTROLLER STARTING OR RESUMING.......

 

AICONTROLLER has encountered an error, please note the following error information.

 

***** Exception = 9 SendID = 107 Index=1cbData = 24

 

 

P3Dv3 in Win10  AIController networked from a win7 PC  AIC14B was running fine.

 

Roland opened a separate thread for P3D issues/discussions http://www.avsim.com/topic/498933-ai-controller-20-gate-to-gate-control-open-beta-prepar3d/

Share this post


Link to post
Share on other sites

canned chatter, a great description.

 

i thought that was what vololiberista was writing about. AI pilot/controller i call comms.

Canned chatter refers to pre-recorded live ATC. For example while you are in contact with Kai Tak Approach etc what you would hear is for example Manchester Tower which has nothing to do with Kai Tak at all and is as unrealistic as you can get. PF3 on the other hand creates "chatter" from the AI surrounding you. Both on the ground and in the air. So from the sim point of view they are real a/c. They show up on your TCAS and you will hear them in their local accents including ATC. That is more realisitic because I can identify who is talking to who.

Share this post


Link to post
Share on other sites

PF3 on the other hand creates "chatter" from the AI surrounding you...

yes I know .... but call it comms (or anything other than chatter, chatter reminds me of ....) !

Have seen the same behavior and also at Flightbeam's KSFOhd. Most of the AI went their merry way to the runway but some indeed were going in small circles, sometimes even direct after pushback.

dick / marcel

 

problem solved (i think) ... start AIM / AIC after fsx situation / weather etc. & all's well !!

Share this post


Link to post
Share on other sites

For the users with UT2 compatibility questions - it does seem to be missing in the GUI however you can still set it manually in the ini file as:  UT2Compatibility=1 

 

Not sure if this actually does anything and also needs to be set before every launch of the program.  Hopefully Roland will provide further guidance.

 

Ilya

 

You could set the AIController.ini file to read only in Windows. AiMonitor will throw a .net error when exiting, saying it can´t write to AIController.ini . Not a fix, but a workaround. Hopefully the great Roland will look into this :) 

 

Thank you for your brilliant contribution and hard work Roland! 

Share this post


Link to post
Share on other sites

Hi,

Ive been using the previous version of AI Controller with no issues at all.

 

Since trying this version departing aircraft depart with no issues at all except the throttle spooling up and down. But the following issues happen to aircraft on approach and final.....

 

1. Not one aircraft has landed at the airports....They all nosedive at approx 3 miles from runway to around 400ft above ground. they then do 1 of 2 things.

a. they land 3 miles short and taxi down the motorway or side roads and crash through the fence to get to the gate.

b. they climb to 15000ft and go around never to be seen again, just heading out to sea......

 

2. When there is a conflict in air the aircraft instructed to slow by ai controller reduces to 0 kts and doesnt move any further. I investigated this by changing camera to one of the aircraft in question only to find it was attempting to leave the earth completely. Nose up, tail down and throttling to the max......I kid you not.......

 

I have 2 screenshots but cant figure out how to upload them here.

 

I have tried at 3 uk airports all with the same result.

 

 

 

 

Whilst i have found this quite amusing to watch for the past 2 hours there is a serious bug with this new version and my FSX

 

Tell me what info you need from me and ill try and oblige.

 

Danny Smith

 

 

 

 

 

Share this post


Link to post
Share on other sites

Just as an update to my above post,

 

EasyJet has just done an inverted flyby at Glasgow (egpf)

 

None of the above issues were present in the previous version but I updated this software and the gsx beta at the same time. Having said that the aircraft fly and land normally without ai controller active .

 

Ps if someone can tell me how to post pictures here I'll show you the above issues.

 

Danny smith

Share this post


Link to post
Share on other sites

Hi,

Yesterday evening, I installed AIController V2. I had already v14B.

I desinstalled the old version then run again my computer.

I installed V2 like written in readme1st.txt.

All was perfect. I converted all PMDG's SIDSTAR then installed in AIController V2.

I was time to sleep ;O)

This morning, I wanted to contnue the installation and try  it in FSX.

 

When I ran AImonitor.exe, the program opened but directly in Task bar.. I can nothing do.

I desinstalled, ran Cleaner, the problem is the same....

I tried with other program and the v14B .. all run correctly... only V2

 

My config is :

Windows 8.1 on laptop

8Go RAM

FSX+Acceleration on Desktop with windows 7 Pro

 

Have you a idea which can help me ?

 

Thanks in advance

 

Best regards

 

Yvan Muster

 

PS : sorry for my english ;O)

  • Upvote 1

Share this post


Link to post
Share on other sites

Hi,

finally , I found a solution. I had again a few place on my disk C:  . I desinstalled from disk D: and re-installed on disk C:

It seem it's ok.... I hope tomorrow it will again ok ;)

Share this post


Link to post
Share on other sites

I finally found a solution to my problems posted above.

 

The version of SID/STAR converter included in the download is version 1.1.

 

for some reason this version did not convert the approaches....only the SID and STAR data was converted.

 

I found after some searching a version 1.3 which converted everything including the approaches and have not had any issues since.

 

 

Not sure if i downloaded the wrong archive for AI Controller V2 but it was from the link on the first page, or if there is an incompatibility with my system and SID/STAR converter. but 1.3 worked...

 

Danny Smith

Share this post


Link to post
Share on other sites

Thanks Jay,

Was trying to find the link again to post here but couldn't find it.

 

Danny smith

Share this post


Link to post
Share on other sites

Was trying to find the link again to post here but couldn't find it.

 

Thanks for catching that!  I'm uploading an update later today, I'll make sure to include ver. 1.3 of the SIDSTAR Converter.

 

-Roland

Share this post


Link to post
Share on other sites

No approach files caused by the old version of AIConv.exe (AISIDSTAR Converter Ver. 1.2Q rev. 2) included with current AI Controller 2.0 build. Version that I'm get from 1.4B do this work fine.

Share this post


Link to post
Share on other sites

Roland,

 

          I forgot in all the excitement to say thank you for what to me has been a really useful flight sim addition and your continued support of the community.

 

Danny Smith

Share this post


Link to post
Share on other sites

Hi all,

I cant seem to get this version to run.

The link with FSUIPC is established and then Ai Controller is starting or resuming......

Imediately a window pops up stating Ai Controller V 2.0 has stopped working. All I can then do is close it.

Running on networked Win 7 32bit.

V1.4 works fine

Any ideas would be appreciated. Many thanks

Steve

Share this post


Link to post
Share on other sites

Hi,

Yesterday evening, I installed AIController V2. I had already v14B.

I desinstalled the old version then run again my computer.

I installed V2 like written in readme1st.txt.

All was perfect. I converted all PMDG's SIDSTAR then installed in AIController V2.

I was time to sleep ;O)

This morning, I wanted to contnue the installation and try it in FSX.

 

When I ran AImonitor.exe, the program opened but directly in Task bar.. I can nothing do.

I desinstalled, ran Cleaner, the problem is the same....

I tried with other program and the v14B .. all run correctly... only V2

 

My config is :

Windows 8.1 on laptop

8Go RAM

FSX+Acceleration on Desktop with windows 7 Pro

 

Have you a idea which can help me ?

 

Thanks in advance

 

Best regards

 

Yvan Muster

 

PS : sorry for my english ;O)

Yvan I think you are refering to the program being minimized. On the task bar right click on AImonitor and press maximize.

Share this post


Link to post
Share on other sites
Here's the links to the latest update:

 


 

Normally I would include a .zip file with only the changed files, but this hotfix affects a lot of files.  I strongly recommend uninstalling the initial version and installing the new version.  Sorry...but these things happen in an open beta!

 

Fixed:  Included STAR samples didn't include "close-in" variations.  For those new to the program, the "close-in" version of a STAR takes into account that the entry point of many STARs is outside the FSX/P3D reality bubble.  The close-in variation allows the AI to join the STAR within the reality bubble to avoid being vectored outside the bubble, which results in the AI being deleted.  For those who noticed the approach traffic was light at supposedly busy airports...this was probably the culprit.

 


Fixed:  Wrong version of SIDSTAR converter and AIConve.exe utility.  If you converted any SID, STAR or Approach files using the old versions, I would recommend reconverting using the latest version.  Remember to remove the old version of the SIDSTAR Converter and install the latest ver 1.3 included in the hot fix.  Sorry, a pain, but beta!


 


Fixed:  Now something that makes things much easier!  AIController now recurses through subdirectories when specifying a SID, STAR, approach directory.  Thus, adding converted files is a lot easier (i.e., adding additional SID,STAR and approach files is now consistent with the "Installation and Basic Usage" video describing the addition of converted Mexican SID, STAR and Approach files).

 

Fixed:  Better control of AI when departing and arriving in the same reality bubble (e.g., a short hop from KORD to KMDW).

 

Fixed:  Less engine thrust variation during taxi and takeoff (e.g., idle to high thrust back to idle).

 

Fixed:  Sometimes AI wasn't getting assigned final approaches in a timely fashion (this might have been the cause of some "force arrival/landing runway" issues some users reported, but still evaluating that issue).

 

Fixed:  AI circling around jetroute waypoints.

 

Fixed:  "AI Jet Route Only" option fixed.

 

Fixed:  Tear-drop procedure when AI approaching final approach fix at obtuse angle.

 

Fixed:  Some stability issues (AIController crashing).

 

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

  • Upvote 2

Share this post


Link to post
Share on other sites

 

 


Any AI craft after assigning jet route proceeds to active waypoint shown in AI Monitor in “Waypoint” column. After passing active waypoint there is no switching to next waypoint. AI plane flies along large circle and tries to pass same point again. And this continues until AI Controller stopped.

 

Please try the update, there were some fixes to the jetroute coding.


 


There are two options listed in the AICONTROLLER text document that I am unable to find a menu option for:

 

Compatibility mode for UT2 aircraft and provide interface for external programs. Am I just missing them or hoe do they get set.

 

Thanks for bringing that to my attention...UT2 compatibility mode is no longer needed since AIController controls the AI during all phases of flight.  The interface for external programs is listed as output pipe and telemetry file in settings/options/general.  I'll revise the documentation.


 

 


Are there any options to control push back?

 

Not yet, but I've definitely considered it!

Share this post


Link to post
Share on other sites

Please try the update, there were some fixes to the jetroute coding.

Hi Roland.

Thank you very much for you fix. But problem remains the same except when AIJetRoutesOnly=1. In this case AI crafts fly jet routes correct. If AIJetRoutesOnly=0 AI make circling around jetroutes WP.

 

Thanks!          Edward.

Share this post


Link to post
Share on other sites

1. minor ui bug on the SID/STAR/approaches menu...selecting paths checkboxes require 2 clicks instead of a single click as is normal for this type of interface
 
2. in the same menu..it would be nice if it could recurse through directorys. adding an entry for every country will take a lot of clicking, even more if you add the states/provinces. or is it unusual to just convert the whole navdata folder? so far i have just been doing the airports i am flying between but that is a hassle, eventually i'll want to just do it once a month when i update navdata..
 
3.question...what are the optimal settings to use for sid/star converter? is the defaults correct? if pattern altitude is 0000 what does that mean? shouldn't it be 1000?  i changed the speed to 280 since that seems a common speed limit in usa stars anyway. should the minimum waypoint size be lower than 5nm if the stars and approaches have a lot of closely spaced points?
 
4.minor ui bug..the double popup boxes during taxi-graph update are confusing and pop up on top of eachother. not sure it's necessary to require a separate 'ok' click just to do the 2nd half of the process...
 
5. so this is definitely a finicky part of the process... taxi_graph update generated a 0kb file for me the first time. it seems that fsAeroData layers confusing things, i'm guessing because it only checks the topmost bgl for that airport and they contain only updated data not the actual taxiways and layout. it also gets confused by default airports that have mytraffic bgl files.  so anytime i import taxi data i have to go into fsx, disable mytraffic and aerodata layers, exit out, run the taxi graph builder, then reload fsx and reenable them, and ignore the complaint it makes for having changed the scenery when you re-enable those layers. wouldn't it be easier to have it skip a bgl file if it doesn't contain taxiway data? i don't know if there is a way to step down them in order of priority but that's how the sim does it..
 
6. seems like it detects broken runway links at a huge amount of airports. is this normal or suposed to be a rare case? i discovered some of that was related possibly to re-enabling mytraffic, it may be trying to extract those links from the wrong bgl also, i'm not sure exactly if this runway link thing is happening only at runtime or as part of the taxi graph building process.
 
6a....startup is really slow when there are broken links, it pauses for several seconds on each one..this takes 3-4 minutes to start with only a handful of airports.  maybe this is because i put it in verbose mode?
 
7. not really having good luck with the cull mode ..nukes all the aircraft at my airport right away. starting at KSJC there is 1 plane but like 15 at KSFO and 10 at KOAK. it seems like it does not delete farther aircraft prioritized over closer ones. it worked pretty well for me in an area where the only airport being monitored was the one i was at, but in the bay area using the included files it was difficult to cap the aircraft total while still having any near my starting position.. here's the settings i was using..

 

I think the defaults are okay, but if you come across settings that seem to work better, please let me know!  I really haven't had a lot of time to spend tweaking all the various settings...I'm putting them in there for the user and making sure they work, but finding the optimum settings is a whole other endeavor.

 

Regarding double popups....they represent two different parallel threads, so that's how that came about...no doubt I could just have one though.

 

Thanks for heads up regarding fsAeroData layers...yeah it probably is checking only the top most scenery layer for an airport.  It should scan the MyTraffic bgls though...I'm using MyTraffic for FSX.

 

I get a lot of broken runway links too.  It just is something that wasn't checked before because there was no need to.  Usually it is okay...I think AIC is probably generating too much information regarding this issue..I think I'll cut it back.   The one you really have to watch out for are when AIC states no landing or taxiing are possible at the airport.

 

Looking into startup time.  EDIT:  I would not recommend verbose mode unless you're trouble-shooting a problem.

 

Thanks for the report on AICull mode 4...I will look into this!

 

 

Here are the things I noticed (P3D v3.3):

The aircraft don't always push back "in an orderly fashion", sometimes the don't turn onto the taxiway and do the FSX pushback, sometimes they push back further away from the taxiway centreline, which can look odd when it happens in a narrow space.

When taxiing the AI accelerates, then it slows down harshly, stops, and then accelerates again. When there is a turn, it slows down and takes it with 2 kts and then accelerates again. I tried to reduce the acceleration scalar, which helped a bit, but the turns are extremely slow and the complete stops are frequent.

Anti collision between AI does not seem to work. They taxi into each other all the time. Ideal would be if they gave way to other AI by stopping before intersections (but I don't know if that is implemented).

I changed the AFCAD to honour taxiway directions and tested the function in AI Controller 2, but it did not seem to work (maybe that has to do with the taxi_graph file not being populated, I will check that today).

On their way to the runway 2 out of 5 aircraft end up taxiing on the grass, i.e. not following the taxiway centreline, taking short cuts and then make lots of turns to come back.

Take off and SID seems to be fine.

Approaches and Landings: 2 out of 5 approaches are erratic and end up somewhere in the vicinity of the airport. After landing the aircraft slow down almost to a complete stop and then seem to look for the exit. Maybe I will have to fiddle with the according parameter.

Gate assignments doe not seem to work properly, almost all landing AI aircraft are sent to the same (remote) area, regardless of airline and gate assignments.

Apart from that, I see this version as a big improvement and as I said before, for me, it's a milestone in FS to be able to use runway 18 in Frankfurt.

 

Cheers

 

Nizar, are you using Mega Airport Frankfurt...also what approaches did you see this behavior.  I fixed the teardrop procedure, which was causing erratic turns and loss of altitude...might be what you were seeing.

 

As of now there is no anti-collision between arriving and departing ground traffic, however you should see the departing AI avoid each other and the arriving AI avoid each other.

 

Taxi smoothness will be an area of focus next.  Probably will never be as smooth as default AI because default AI gets "slewed" around on the ground while my program actually drives the AI (moves the tiller, hits the brakes, changes the throttle).  Still there is a lot of improvements that can be made.

 

Regarding taxi directions, the scenery has to be designed for it.  Since FSX/P3D never honored the direction of the AFCAD taxi links, I don't think there is any scenery designed that way (yet).

 

Oh man not gate assignments again!   :wink:  I didn't touch that from the version 1.4.  Is there a FSX/P3D AI config. path that needs to be specified in the Program Config Paths/Advance Path Options ?

Share this post


Link to post
Share on other sites

UT2 compatibility mode is no longer needed since AIController controls the AI during all phases of flight.

 

Perhaps this is not a very good idea. AI in UT2 has long and close to real world flight plans. I think it's better to let them follow it.

Also UT2 mode automatically disable "inject departing AI at monitored airports to maintain..."

  • Upvote 1

Share this post


Link to post
Share on other sites

Regarding taxi directions, the scenery has to be designed for it.  Since FSX/P3D never honored the direction of the AFCAD taxi links, I don't think there is any scenery designed that way (yet).

 

Oh man not gate assignments again!   :wink:  I didn't touch that from the version 1.4.  Is there a FSX/P3D AI config. path that needs to be specified in the Program Config Paths/Advance Path Options ?

 

The gate assignments seem to work now.

 

I changed the AFCAD and  reconfigured the paths to align the directions, but AI Controller is not honouring them. Or do you mean something else by "the scenery has to be designed for it"? 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now