regulate

Version 3.3 is out! Go get it........

The TFS 772LR/F was converted and posted a couple days ago. Not sure which aircraft they are working on right now. The TFS Dash 8 series, Saabs and other misc planes have been done so far.

We have some people working on conversions of the TFS (Fruit Stand) models at AIG, so if they are updated, you will be able to use the 777's etc. FSP has also released the 777/A330 series and others as payware (it's pretty cheap and P3D native, looks great) that are available on Sim Market. The recent FSP and all of FAIB work great in V4. FAIB will also be releasing a new 767 series soon to replace the very dated AIA models. Some AIG models have required conversions, and they work, but are not completely native to all of the correct AI native functions with lighting etc, but they will do for now.

How many runways will you be able to control for landing (breaking up into %). I believe the last version was 3. Up to 4 would be awesome......Thanks for everything.

Roland, P3D 2.5 has come out with their third hot fix today. One of the items of note is this: *Fixed an issue where AI aircraft would not correctly clear navigation settings. This would cause the AI to constantly overwrite control surface values being set by the user through Sim Connect. How is this relevant to AI Controller? Thanks Brian

The Latin VFR runways list the following: ID Heading Length Meters Width Meters Surface Cross Wind Comments 08R/26L 087.4 3180.1 61.0 CONCRETE No 08L/26R 087.4 2621.3 45.8 CONCRETE No 09/27 087.4 3960.3 45.7 CONCRETE No 10R/28L 095.2 3.0 3.0 ICE Yes 10L/28R 103.0 3.0 3.0 ICE Yes 11R/29L 110.8 3.0 3.0 ICE Yes 11L/29R 118.6 3.0 3.0 ICE Yes 12/30 119.6 2880.0 45.7 CONCRETE No The runways listed as ICE have an X next to them, I assume means closed or false (hidden) runways, the Concrete runways all of a runway drawing next to them signifying they are present in the sim. Brian

Roland and Matias, Thanks for your help. I purchased updated data from Navigraph (3/5/15) and all of the states converted just fine except for one, Oklahoma. My outdated data was the culprit with the conversion of the data. Brian

Roland, Mine says 1.4.1.1 in the properties of the file. I suspect because I converted the PMDG nav data from the newly released (patched PMDG 737 NGX) that maybe the navdata is old? EDIT: I just looked, the navdata in the fresh install of the PMDG is from 2011.

Matias, The error box says "SID,STAR and Final Approach Conversion Utility (AIConv.exe) for use with AI Controller. has stopped working." Then it gives me the option to close the program, at which point the program starts with the next state that is not corrupted. I ran the conversion with the AI Controller.exe boxed checked. In the window in AIConv.exe (which by default does not open all the way so it's difficult to read the full message) stopped in California at airport KL71. The message within AiConv.exe box says "The user should manually insepct the converted SID files and remove waypoints to......", message cut off on my screen shot so I don't know what the rest says. Anyway, you asked if I can try and only convert the state by itself, but I am not sure how to do that? Can you give me a little run through? Not sure if that would change anything though. I have run through the complete conversion process three times. Every country converts fine except the following U.S. states. CA, CO, GA, IL, MD, MA, TX and WA. There are a lot of airport missing in each of those states that received the error message. Did anyone else experience this? If not, maybe it's me but I don't understand the issue. Also, is the Runway.xml Path line mandatory to fill in? I don't believe I have the makerunways utility. Thanks Brian

Matias, When converting the SID/Star from my PMDG nav data (latest version of SID/STAR convertor), I get an error message on several US states, such as California and Texas. Most states compile fine, but several stop, for example, California only compiles the data to KL71, every airport after that there is no data. Texas only goes to KDAL. I have tried twice, same results. If you click close when the error message comes up, it starts in the next state. Seems like all other nations were fine. Thanks Brian

Roland, Thank you again for this great program. I have some feedback and thoughts. So far, love the ability to have AI be forced to land at specific runways, splitting up the runway workload for people like me who run 100% custom AI based on up-to-date real-world schedules. That feature is working well, and go-arounds are non-existent so far. And to push the envelope, would it be feasible to even have a 4th runway forcing option for those that want it? Just checking. Also, is it possible to have an option to turn off the warning pop-up, telling the user that you are forcing the runway choice. To be honest, that is driving me a little crazy when spotting. I added KSLC as an airport using the SIDSTAR convertor, and the aircraft seem to be following the SIDS and Stars just fine and splitting into three landing runways as I directed. On the AI Controller Log, it reads Read STAR32 filename = G:\AICONTROLLER\AICONTROLLERV14B\KSLC\*.* and Read SID33 filename = G:\AICONTROLLER\AICONTROLLERV14B\KSLC\*.* I have verified via a search that I do not have a duplicate AFCAD. The AI Controller path file has this entry TAXI=KSLC,G:\Ultimate VFR Utah\Ultimate VFR\Ultimate VFR Utah Imagery\scenery\KSLC_ADEP2_BCS.BGL However, for a reason that I cannot figure out, my custom AFCAD is not being adhered to by the enhanced taxi feature. Lots of issues. Half of the aircraft vanish on the runway when the roll out is complete. Aircraft that do taxi park where ever they wish, not according to parking codes, including in the same parking space as AI that is already parked. This specific custom KSLC ADE AFCAD works fine in P3D without AI controller. The only things I changed in AI controller taxi in procedure is for the taxi roll-out, changing the speed to 18 knots and I turned off collisions since it makes aircraft disappear. I am at a loss about what I am doing wrong. I would add that the aircraft that do park, park at odd angles, not adhering to the ADE parking spot cleanly. Is there a file or log I could check on this, verifying I have everything installed properly? Other thoughts, I really like how the aircraft on final approach seems to waver a little (realistically) as they come in for a landing. Nice touch. The landing animation though is rough. The main landing gear touch down fine (not very smooth though), but then the animation for the front gear is very abrupt and instantaneous. Not sure if the AIR file or AI controller is causing that. I am using AIA, AIG, TFS, OSP, and FAIB models primarily. Just thinking out loud here. The custom ADE AFCADS work great in P3D or FSX. The way the aircraft taxi, and park at the correct gates per our parking codes, and hold for other AI aircraft work just fine. Is is possible to give the user the option to have AI Controller completely release the AI aircraft to the default or custom ADE AFCAD once the roll-out is completed? Or another thought, release AI Controller to P3D with the ADE or default AFCAD with only the taxi speed and turning radius options being utilized by the taxi feature. Not sure if that is even technically possible. One last note. The departing AI traffic taxis out to the runways and take off correctly. Thanks for your consideration. Brian S.

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

Thank you Roland. Not to push the issue, but is it possible to have force the AI to land on three parallel runways simultaneously at really busy airports , like at KDFW or KATL? Inquiring minds over on our AI boards are interested if that is something that can be done within the limits of FSX/P3D. Appreciate your efforts.

Roland, thanks so much for the update. Really appreciate you allowing us to have our custom AFCAD parking back, in addition to the FDE's for the AI aircraft taking control of the rollout. A nice bonus breaking the 5 parking code restriction. Can't wait to see if you can do the 50/50 breakup of the AI aircraft on parallel runways. Amazing work.

Roland, if you can make it so that the traffic load is balanced between parallel landing runways that would be amazing. LAX is a great example of the problem of landing runway workloads on parallel runways, and would be a great testing ground. After the initial overwheming AI traffic load settles down when you start the sim, about 75% of the traffic goes to 24R, about 25% to 25L, obviously based upon where the planes originally departed from creating the inbalance. It would be amazing if the workload and aircraft spacing were balanced to eliminate most go arounds, and then have the aircraft taxi to the appropirate gate based upon our ADE custom AFCADS. Thanks for all of your efforts.