I'm not seeing this, a good way to double-check is look at the contents of the AIControllerPath.txt file.  The "TAXI" line will show you exactly what scenery the program is reading for waypoint data.

 

Here's an example:

 

TAXI=EDDF,C:\FSX Apps\Microsoft Flight Simulator X\scenery\0601\scenery\APX50140.bgl   --->  AIController is reading the default EDDF scenery file using the default folder paths.

 

TAXI=EDDF,C:\FSX Apps\Microsoft Flight Simulator X\Addon Scenery\Frankfurt_Airport_v5\scenery\KALB_ADEX_MWA16.BGL ---> AIController is reading the addon EDDF scenery file using the Addon scenery path.

 

If anyone else is having problems with AIController reading default waypoint data instead of waypoint data from active, addon scenery, please let me know right away as this is a critical issue.

 

-Roland

Hi Roland,

 

following line is three times in my Aicontrollerpath.txt file :

 

TAXI=KIAD,\\RICK-PC\P3D v2.5\scenery\0302\scenery\APX27180.bgl

 

However I use Kiad Flightbeam. 

 

Will try a rebuild.

 

edited:

 

did 2 rebuilds, and now  5 times kiad is in but not flightbeam. 

 

Have p3dv2.5 and only added  \\RICK-PC\P3D v2.5\ in the cofig paths. Will try to rebuild/force runway taxi update with a config path directing to the p3dv2.5 scenery.cfg in programData\Lockheed Martin\Prepar3Dv2\.

 

I think it's because in the scenery.cfg the scenery file map is not indicated as it should be for a networked system?

Edited February 26, 201511 yr by pilotter

 

 

If anyone else is having problems with AIController reading default waypoint data instead of waypoint data from active, addon scenery, please let me know right away as this is a critical issue.
 
-Roland

 

Hi Roland! I really appreciate for your great work on AI Controller.

Regarding the taxiway bgl data, it seems that AI Monitor is not reading Addon Scenery\Scenery folder of the sim.

 

I have modified bgl files of CYYC and CYEG in Addon Scenery\Scenery folder.

However in my AIControllerPath.txt, it seems to be reading the stock airport data as follows.

 

TAXI=CYYC,\\SUGITAKU-DESK\Lockheed Martin\Prepar3D v2\scenery\0201\scenery\APX17130.bgl

TAXI=CYEG,\\SUGITAKU-DESK\Lockheed Martin\Prepar3D v2\scenery\0201\scenery\APX17130.bgl

 

The correct bgl files should be

Addon Scenery\Scenery\CYYC_P3D_CW_RWC.bgl

Addon Scenery\Scenery\CYEG_CW_RS.bgl

 

It's curious because it reads my third party addon data correctly which creates its own folder like FlyTampa Toronto or FSDream Team Vancouver.

 

TAXI=CYYZ,\\SUGITAKU-DESK\Lockheed Martin\Prepar3D v2\Addon Scenery\FlyTampa-Toronto\scenery\CYYZ_ADEX_FLYTAMPA_TRIPLE_BASE.BGL

TAXI=CYVR,\\SUGITAKU-DESK\Lockheed Martin\Prepar3D v2\FsDreamTeam\CYVR\scenery\CYVR_AP.BGL

 

Therefore, I think one of the issue is that it fails to read Addon Scenery\Scenery folder, in which people put modified scenery bgl files.

 

Hope you'll find a fix for this issue.

Hi Roland,

 

Is there a way to tell AI which are the active landing and departing RW's for a monitored Airport?..

 

kind regards

Richi

Could that have caused the problem where sid/stars were not being assigned because I had not enabled the jet routes on the jet routes page?

 

No, I don't think those are related.  Are you having problems with STARs not being assigned?

 

 

following line is three times in my Aicontrollerpath.txt file :

 

TAXI=KIAD,\\RICK-PC\P3D v2.5\scenery\0302\scenery\APX27180.bgl

 

However I use Kiad Flightbeam.

 

I was able to replicate this, looks like a bug.  Thanks for finding it.  I think it is related to P3D mode.  I'll fix it for the next version.  As a workaround until then, delete the AIController.ini, AIControllerPath.txt, anda AIControllerList.txt, load AIMonitor, then enter the paths you want.

 

 

Therefore, I think one of the issue is that it fails to read Addon Scenery\Scenery folder, in which people put modified scenery bgl files.

 

Yep, thanks for the feedback.  Much appreciated.  Fixed for the next version.

 

 

I also notice that AI Monitor detects a scenery change every time it starts, despite my not having made any changes to scenery.cfg.

 

I've noticed that too, but I'm having a hard time replicating (predictably) on my development platform.  I'll keep investigating.

 

 

1)when planes land in the same airport than me: they dissapear on the runway. ¡pop! and anything there.

2) how could i accelerate the taxi after landing?

3) do you recommend the last star before landing at some distance from airport specific? sometimes the last star is very near the runway.

4) how could i make that an ATR42 could make his final approach at the same speed than a airbus346?

 

1) look at the console output, it will give you a reason why it happened

2) Enhanced Mode-Taxi In Screen --> Taxi Speed then Apply.

3) Yes, adjust the minimum STAR waypoint dist. option when using AIConv.exe

4) AI Performance Screen --> AI TurboProp Speed Adjust Scalar then Apply.

I really love this app. Roland you are a great man!

 

I have run into an issue though. The AImonitor has just stopped working. I run it as usual and have made no changes but it does not load at all. The app appears in the taskbar as if it is running but no actual windows show. I didn't make any changes and I can't find any error logs to help here. Any ideas?

 

Thanks for all the work.

 

Ken

 

Edit: I did a full reinstall twice and it didn't work. I then tried a new drive and it worked. Not sure what was up but back in business.

 

 

On the GUI for the departure and approach paths, could you implement folder structure in the list? and a search function.... having all the Navigraph AIRAC Cycle in there it gets quite time consuming to choose the SID/STAR approaches one would like to use.... 

 

Historical reasons...the first version supported STARs only, so when I added extra capability, I wanted to keep backward compatibility.

 

-Roland

 

Hello to all,

can anyone help me with this problem?

 

 

 

AIMonitor should be in the same folder as AIController.  This error could also mean AIController failed to launch at the outset, make sure you have VC++ 2013 installed (as mentioned in the readme files).  You can also load AIController by itself via a console window and see what happens.

 

-Roland

 

 

Is there a way to ignore the "taxi" control of SIDSTARCONTROLLER?.

 

Sure, just disable enhanced controller mode (0) in the enhanced mode options screen.

 

-Roland

No I'm seeing SIDS/STARS being assigned. I think I have it all working now!! Great program!!

I have run into an issue though. The AImonitor has just stopped working. I run it as usual and have made no changes but it does not load at all. The app appears in the taskbar as if it is running but no actual windows show. I didn't make any changes and I can't find any error logs to help here. Any ideas?

 

Thanks.  Sometimes the screen gets locked into a minimized state (not sure why).  While AIMonitor is running press Alt + Space to get a menu with the option to maximize the Window.

 

-Roland

 

 

Is there a way to tell AI which are the active landing and departing RW's for a monitored Airport?..

 

AIController tries to follow the departure patterns of FSX.  If an FSX runway is active departure, but no parallel runways, then AIController will use the same runway.  If parallel runways, then AIController will use a parallel runway not being used for departures.  If there is too much landing activity for runway however, it will start looking for other parallel runways or runways with similar headings for load-balancing (the load-balancing can be controlled in the options menu).

 

-Roland

No I'm seeing SIDS/STARS being assigned. I think I have it all working now!! Great program!!

 

 

Good to hear, the alpha version certainly had it share of bugs.  I'm getting close to revision B.  It will have a lot of bug fixes, plus new capabilities (e.g., ADE-compliant gate selection), much better touchdown animations (reliable touchdown smoke, no smoke at end of rollout, no strange landing-gear angles, etc.) and invidualized AI roll-out lengths based on each AI's aircraft.cfg properties.

 

-Roland

Hi Roland,

 

 

 

AIController tries to follow the departure patterns of FSX.  If an FSX runway is active departure, but no parallel runways, then AIController will use the same runway.  If parallel runways, then AIController will use a parallel runway not being used for departures.  If there is too much landing activity for runway however, it will start looking for other parallel runways or runways with similar headings for load-balancing (the load-balancing can be controlled in the options menu).
 
-Roland

 

Thanks for the answer - would it be possible to implement a sort of choice option in the future. One of the problems is that FSX is not very realistic when it comes to RW choice. It, as far as i know, only considers the wind... in real life also taxidistance and other parameters like Noise Abaitment come in to the decision which runways will be used.... Would be a really great addition to your already superb program. I'm really enjoing it!

 

 

 

liketofly1, on 25 Feb 2015 - 8:21 PM, said:

On the GUI for the departure and approach paths, could you implement folder structure in the list? and a search function.... having all the Navigraph AIRAC Cycle in there it gets quite time consuming to choose the SID/STAR approaches one would like to use.... 
 
Historical reasons...the first version supported STARs only, so when I added extra capability, I wanted to keep backward compatibility.
 
-Roland

 

Thanks for the answer. maybe in a new version - I'm not shure backward compatibility (from a user point of view) is so important, as it seems everybody here is eager to install the newest version anyway ;-))

 

kind regards

Richi

I am a happy user of V13a on a networked machine and will be staying with it.

 

I have tried to install 14a on a networked machine but cannot am unable to make it work.

 

I'll give it a rest for a while and may have another shot when I don't feel like smashing the screen

I am a happy user of V13a on a networked machine and will be staying with it.

 

I have tried to install 14a on a networked machine but cannot am unable to make it work.

 

I'll give it a rest for a while and may have another shot when I don't feel like smashing the screen

Followed the instructions to the letter on the FSX computer and the application installed flawlessly.

 

However, when loading to the networked PC continually received messages indicating and error and when continued the application appeared to load. When I selected the second option on the 'options' menu there were a number of bgls for timezone, mesh and vector files that created  errors and then when appeared completed clicking the button to start Aicontroller resulted in another error.

 

Has anyone got it to work over a network? 

 

I give up!!!!

 

 

Good to hear, the alpha version certainly had it share of bugs. I'm getting close to revision B. It will have a lot of bug fixes, plus new capabilities (e.g., ADE-compliant gate selection)...and invidualized AI roll-out lengths based on each AI's aircraft.cfg properties.

 

Instead of .cfg based roll outs, may it be possible that we get back the option to assign coordinates or better a taxinode at a exit as the end of rollout?

Like the final rollout in the older version?

 

I think, to keep the Takeoff/Approach frequency it is necessary to stop as close to the exit as possible to leave the runway.

I made the experience that the cfg based rollout finally don´t work. You can pimp it as much as you like, it works at a few airports, at the others you miss the exit and the ai turns back or taxi 1000 ft to the next. Both is too time consuming.

 

The only way is the "Brake to vacate" like the option of the A380. You choose the taxiway to leave, the rest works by autobrake.

It would be great if there would be a choice between small aircrafts and heavys, but in general, the system that the aircrafts stops randomly will cause problems all the time...

Someone asked if AI Controller worked with FSX SE, the answer is yes it does. It also works with:- ProATC X, Aivlasoft EFB, Traffic Manager and ASN. Once again, thank you Roland for an amazing addon.

AIMonitor should be in the same folder as AIController.  This error could also mean AIController failed to launch at the outset, make sure you have VC++ 2013 installed (as mentioned in the readme files).  You can also load AIController by itself via a console window and see what happens.

 

-Roland

 

Hi, Roland, first of all thank you for the great program!

 

my problem was solved by itself when I read the all topics from the beginning, everything works perfectly now.

Sorry for asked question, I had to do it right away.

Thanks.

I ran into another strange issue today that I thought was fixed. At FSDT KDFW I was just going to watch the traffic so I was sitting next to the runway and the planes started to taxi out. One plane took off but then the one that taxied into position just sat there. This then caused a landing plane to do this really odd like low fly by of the runway and it drifted into like the middle of the grass between the runways. I don't think it ever landed it just kinda kept gliding really close to the ground. I tried resetting the traffic but again only 1 plane was able to take off before the next just sat on the runway.