Clipper Ocean Spray

MDFlier and Dimitrios, thanks for the suggestions, very good point, here's a link to a fix: https://www.mediafire.com/file/63z47i50t4mdsh9/AIGround_v110HF1.zip/file

I thought I noticed a tango during earlier development, but I couldn't reproduce it when I went back to double check. Thanks for confirming it. I've spent a day trying to reproduce it at EGLL with insane traffic densities, but I just haven't be able to. Here's a link to a fix I'm pretty sure will work, unfortunately as mentioned, I can't reproduce the situation the new code is designed to fix. 😉 Please give it a try, maybe you'll have better luck. One situation the new code won't handle: the first AI causes a second AI to hold, and then a significant amount of time later the second AI causes the first AI to hold (rationale: good chance there will be a new traffic situation at that point instead of the earlier tango). https://www.mediafire.com/file/n5gc9pwpug70fk2/AIFlow_v110HF1.zip/file

Re: 1, that's in the latest version (110) that I linked to in the thread. Re: 2, to do that right I would need to know the taxi nodes and links. My prior AIController read all that data from the bgl(s), but it was a lot more complicated program and I wasn't sure it was worth all the extra fuss. Maybe there is a way I can do it using a bare bones approach. What would you think if the AI pushed back to its normal point, then sort of did a tear drop 180 so that the AI ended up in approx. the same location, but pointed out to the apron?

The versions linked above (1.10) also have some new features described in the readme.

Sorry guys, been sort of slow getting out the updates. I'm "unofficially" providing a link to the latest revisions, which should provide a fix to the go-around issue in heavy approach traffic. I haven't tested as much as I want to yet (I usually do a lot of routine flights with no code changes before I upload to the lib), but I'm providing them to get the go-around fix out there. If you download and something doesn't work, please let me know here or via my email contact (readme.pdf) because these files are essentially beta. Thanks! https://www.mediafire.com/file/rqrgmvnhy7nv4up/AIFlow_v110.zip/file https://www.mediafire.com/file/zutcuqua4sqhnvj/AIGround_v110.zip/file

Lol...thanks for the report, I'll look into it. It is possible. Is there any chance it was a v5 "highway in the sky" type issue?

Re: lined up landing traffic not giving you room for takeoff, squawk 1234 briefly and the AI will stop landing (except for AI already established on short final). Within a minute or two, a slot should open up. Interesting graphic, thanks for that. What program did you use?

Thanks, let me think about the first item. The second item, I've put into the revision I'm working on, which should be out soon.

My earlier AIController utility did that, but it was a substitute AI movement system, which was very complicated, plus once you do that, a substitute communications system is also needed, which isn't my area (although I really enjoy that aspect of the sim and hats off to anyone who is working on something like that). I hope LM will eventually support runway selection. If not, maybe someone can figure out an unsupported way to do it using the existing P3D code.

Yep, I've been able to replicate this issue with the FSPXAI 787. The 737 NG doesn't even activate the spoilers at all during control checks. The MD-11 seems to work fine. I'm email the author and give him a heads up...I'm just sending standard simconnect commands to the AI (simobject). However, the author might have some extra logic associated with the AI, so I'll also add an option to disable control checks in the next revision of AIGround (it might be good to just let the advanced payware AI models do their thing).

Unfortunately no, it is just a barebones utility, it doesn't get into modifying communications or anything like that.

Thanks everyone for the encouraging feedback. Vincent, if you want to turn off separation between the user's aircraft and AI, add this line to AIFlow.ini: USERAISEPARATIONDISTANCE=0 The program will still separate the AI. Regards, Roland.

Just a quick followup: problem is with the default trafficAircraft.bgl (traffic schedule file) in scenery/world/scenery. Temp workaround: replace with P3Dv4 default trafficAircraft.bgl file (backup P3Dv5 original and store OUTSIDE scenery/world/scenery directory) or use a custom/add-on schedule.

Thanks. I haven't gotten around to installing any add ons yet. I haven't seen one default AI jet push back from a gate (after hearing them get clearance) at the many different default airports I checked. It is really strange.

On my rig, all the departing AI are getting stuck in the "clearance" state and not pushing back (stuck at the gate). Is anyone else seeing that?

I think you just need to go into "Settings\SID STARs Approaches and Finals and select the German airports, then apply. Alternatively, you can also go into "Settings\Generic Approaches..." and just enter the ICAO for Munich and Frankfurt, then apply. Is this still at EDDF using the custom files you emailed me and also the generic approach option? Regarding being on crosswind when AIMonitor states the AI is lining up on final, AIMonitor is showing the waypoint the AI is currently intercepting (e.g., the AI is on the crosswind, but it is in the process of intercepting the lineup waypoint). That is sort of confusing, perhaps I'll change it. Did you try to slew-mode approach option? Any better results with that? Does it convert any files? If so, what were the last few things AIController says in the command window (will give an indication as to what file was causing it a problem). There should be an error window that pops up in AIMonitor giving more info. Regarding YSSY, this may be related to the first error. Is 11/29 a real runway at YSSY? Movement processing is independent from FSX, but not sure how much it improves FPS. Regards, -Roland

Haven't heard about the file hosting site Mediafire being compromised, probably ESET is being too aggressive (false positive). Here's the CRC (md5) for the Hot Fix 4 file I uploaded to Mediafire: d8483e78926a3761ce589e732010724d -Roland

Thanks...I'll look into it. The SIDSTAR converter should not affect taxi data though. Re: the SIDSTAR Converter not completing, since someone else gave me feedback that the latest PMDG navdata...I did a test conversion of the latest cycle (1702 Feb. 2) using just AIConv.exe. It did convert all the files so you might want to give that utility a try (e.g., aiconv .\sidstars\*.* .\converted) as a test that bypasses SIDSTAR Converter.

This should be fixed with hot fix 4...however I'm getting so much feedback with this option that it is disabled by default. It is the "Settings\Options\Additional Final Options and Anti-Incursion\Anti-Incursion Threshold Alt for User-AI Conflicts". Default is now zero (off). Also takeoff thrust limit is working now too, which drastically affects takeoff length. Yes, that's correct, although if you have any SID with an extremely early entry point, the increased climbout height could cause a problem (makes the takeoff phase longer and delays the SID-finding phase). If you're using generic patterns only, I would recommend exactly what you did. There were some CTD issues fixed with hot fix 4, please give that a try. Yes, this is probably a bug that was fixed in Hot Fix 4. It was caused by a parallel thread issue when jetroutes were active. Also the takeoff thrust limits now work for Hot Fix 4.

Thanks! Good to hear. Hot Fix 4 should hopefully be even better. Re: no departures...for now AIController relies on the default FSX/P3D system to take AI parked at the gate out of sleep status and I have noticed that sometimes this default system stalls regardless whether AIController is running or not. I usually have to reload FSX/P3D and that clears the problem. Re: taxi half into gate should be better with hot fix 4.

I think both of these issues were fixed for hot fix 4, please give it a try. See the feed in my profile for links to the files.

Yes, once AIController takes control of the AI (e.g., taxi-out, takeoff, then the SID) it cannot be handed back to P3D/FSX's default control (for flying UT2 jetroutes). However, this shouldn't be a big issue because the AI will quickly depart the user's reality bubble, so the user will not really notice. If the user's reality bubble is moving (e.g., the user if flying an aircraft), then with the UT2 option enabled, enroute AI around the user (that the user notices) will continue to use UT2 jetroutes.

You can try using the included aiconv.exe utility as a test to bypass SIDSTAR converter. Since you're only converting one directory, it should be easy to use. Shift right mouse click in the directory where AIController is installed to bring up a command window, then enter aiconv.exe for usage instructions.