Wolkenschreck

The current version is 1.0.0.6 and can be downloaded here: https://www.dropbox.com/s/q22cfj9114id0te/ATCAPI 1-0-0-6..zip?dl=0 ATCAPI 1.0.0.6 was compiled for P3D 5.2 and does still work with P3D 5.3. And here is a brief, extended overview with all the functions that were so far added: ICAO: ICAO name if you are going to set Active Runways and Approaches is needed. Only one ICAO is allowed at the moment. ActiveTakeOffRunway: Name of the active runway for Takeoffs for the ICAO entered above. If more than one entry is present, the sim will assign to each a probability based on the number of entries (2 => 50%, 3 => 33%, and so on) ActiveLandingRunway: Name of the active runway for Landings for the ICAO entered above. If more than one entry is present, the sim will assign to each a probability based on the number of entries (2 => 50%, 3 => 33%, and so on) ApproachName: (Optional for ActiveLandingRunway) and ApproachType (Optional for ActiveLandingRunway): Name and Type of the approach to fly for that active runway. ApproachType: needs to be present if ApproachName is entered. You can get this from your ADE information. If BOTH not included, ILS approach for that runway will be selected. EnableFastTakeOff: will line up and then take off. Faster than the default hold. AllowTakeOffDistance: (in meters), will allow AI to take off if an AI is landing same runways when the distance is < AllowTakeOffDistance (ex 6000 meters, will let take off if landing AI is further than 6000 meters) TaxiSpeedLimiter: is the limit to the 20 knots default speed. you can increase it (taxi speed on runways is capped at 35 knots by default AI behaviour) RunwayTaxiSpeed: will apply a new taxi speed ONLY on AIs vacating runways enableRollthenTakeOff: will let the AI lineup while the AI which lands and vacates the runway minCrossingRny: (in meters). Lets AI cross runways/taxi intersections if blocking AI is > than minCrossingRny. There are also other ground algorithms that prevent non blocking situations with AIs and airport scenery/simobjects isGUIVisible: turns on or off the GUI. Just leave it in 1 = On for the moment. voidTimer: stands for non-reacting AI traffic disappears after xxx seconds EmptyWeightLimit: prevents AIs, which exceeds the set weight, from landing or taking off from a runway (units are in Pounds!) TaxiSeparationMultiplier: will increase spacing between AI that taxi on the ground ATCModel: force certain ATC Models to land/take off on assigned runways. For example, use <ATCModel>A321</ATCModel> to assign all A321 to that runway. Or use an ! exclamation mark <ATCModel>!A321</ATCModel> to prevent all A321 to use a specified runway. And if you only want to use the app without and runway configurations, and just benefit from the improved traffic flow features, use a similar configuration like mine. <?xml version='1.0' encoding='utf-8' ?> <Parameters> <enableFastTakeOffs>1</EnableFastTakeOffs> <allowTakeOffDistance>6000</AllowTakeOffDistance> <taxiSpeedLimiter>30</TaxiSpeedLimiter> <runwayTaxiSpeed>29</runwayTaxiSpeed> <enableRollthenTakeOff>1</enableRollthenTakeOff> <minCrossingRny>1000</minCrossingRny> <isGUIVisible>1</isGUIVisible> <voidTimer>600</voidTimer> <TaxiSeparationMultiplier>2.2</TaxiSeparationMultiplier> </Parameters>

Hi Ron! A minimum weight was something we had in our minds during the design and testing phase, but with limited time on Federico's side was the priority the maximum weight. Maybe something for a later update. Hey Alex! Never saw something similar during testing. Is there any airport where I could check the weird taxi patterns? The taxing into each other-issue could be related to the taxi speed. Most AI FDEs have too weak breaks, which will show such behavior on long and straight taxiways. But the config.xml you posted is outdated. Federico included a <TaxiSeparationMultiplier>2.3</TaxiSeparationMultiplier> for me, which increases the distances aircraft will keep between each other on the ground. This should help a bit to reduce the problem. I will need to take a deeper look into the FPS problem, as I could not recreate it on my end now or during testing. Could you or Balint give me a time and airport where I can recreate this? Thanks.

Thanks Guys! Glad I can help. The ATCMODEL entry does read the the atc_model line of the aircraft.cfg: [General] atc_type=BOEING atc_model=B744 Thus, for freighters you could change the line to atc_model=B74F and add it to your ATCAPI config.

Definitely Grzegorz! But I just got back to AIController myself and have not used since a few years. At the moment, I do also struggle a bit with the set-up and the program exits shortly after the connection is established. But perhaps will @fclaass post his ini settings when he is around here again? Tony, do you have a free copy of FSUIPC installed? FSUIPC is needed, as F.S: AI Separation was built before Simconnect. My pleasure Iván! The Traffic Toolbox is part of the P3D SDK and adds an explorer. I mainly use its explorer function to delete traffic if needed. Other tools might do the same job. Further, you can also send key commands with the explorer (e.g., thrust 70 %) to get waiting AI moving again. The AI_SlopedRunways.dll is another little tool by Federico (fs1). It allows AI to taxi on sloped structures that were made with hard platforms. Examples for that are the taxiway bridges in EDDF, EDDP, MMUN or the sloped runway in KFLL. You can download the latest version here: https://www.dropbox.com/s/9bu0eofms0k2cae/slopedrwyAI.zip?dl=0 For more information, please have a look here:

That's a nice combination! Any chance you could post your AIController ini? Thank you! PS: Are you running AI Controller v2 or version 1.4B from the Avsim library?

Well, the function was actually supposed to perform a flight control check. But it inferred with the flaps. Thus, adding the line AINOCONTROLCHECK=1 should prevent the flight control check and restore the normal flap behavior.

Here in the Avsim library 🙂 fsaisv1.1.zip Ah! I see, I see. That was exactly the reason why I urged Roland back then to make this an optional function. Subsequently, he added the following line to the ini: AINOCONTROLCHECK=1

That's a strange one! All I have done with P3Dv5 is updating the airport file with the one I linked to AIG. Everything else is running nicely with FSUIPCv6 and Windows 10. You could check for a NET Framework update just in case. But I uploaded you my airport files just in case, as the error is referring to an entry in the Airports_FS2004.csv. Try to replace it: https://drive.google.com/drive/folders/1uwR0iVCJm7HkY1DIE1_DgwGKixYNhbC3?usp=sharing Hey Tony! You can find AIGround in the AVSIM library: aiground_v110.zip Just make sure to deactivate the following features in AIFlow/AIGround for compatibility with ATCAPI: AILANDINGBRAKINGSCALAR=1.0 AILANDINGTARGETTIME=0

Sorry Guys for not getting back earlier! It was a very busy week. No Problem at all, Grzegorz! But I should point out that I fly on VATSIM if I do want control. The rest of the time, I do use the sim for AI spotting. If you fly with offline ATC and Ai, than AI Flow might could replace F.S. AI Separation. But as I said, I found the separation with AI Flow too aggressive. Aircraft will end up in the hold but do not get released. ATCAPI: F.S. AI Seperation: AI Flow: AI Ground: PS: And if you want to streamline things a bit, you can place all tools and configs in one folder, and register it with one add-on.xml:

No problem. 🙂 For P3Dv5 you can use the following tools for separation: AI Flow AI Aircraft SID and STAR Controller F.S. AI Separation (fsaisv1.1.zip) Feature wise, I do like AI Flow the most. However, the separation is a bit too aggressive. Thus, only few arrivals will reach the airport. Maybe Roland @Clipper Ocean Spray could have a look at this again in the future? For plain separation, I do like F.S. AI Separation the most. It does still work with P3Dv5 as long as you have a free copy of FSUIPC installed. Moreover, with many changes to ICAO identifiers it does make sense to update the airport database. A replacement can be downloaded here: https://www.alpha-india.net/forums/index.php?topic=21541.msg231340#msg231340 On my PC, I do use ATCAPI, AI Flow, AI Ground, and F.S. AI Separation at the same time for different purposes.

Well, the answer is just above your post. 😉 But yes, you will still need AIFlow or FS AI Separation, with the latter being a bit less aggressive and allowing more arrivals.

Hi vl1, Traffic separation for arrivals are not included yet.

Dan posted the link in the initial post of this thread but I do agree that it can be easily missed. You will find fixes in our official support forum but I do still try to convince the boss that uploading them to Simmarket/ORBX would be easier. 😄 http://forum.simrussia.com/index.php?/topic/2918-eddp-elevation-issue-in-p3d-v5/

Yes, that is correct. We could trace this problem back to ORBX Vector. This was in so far interesting as Vector for v5 does claim to not change any airport elevation. And thanks for bringing up our fix. Glad it does work for all of you here and let us know when you face any further problems.

@Juliett Alfa In addition, have a look at the probabilities. They have to be =1 (100%) each for the landing and takeoff category. Try something like: <Airport> <ICAO>KSFO</ICAO> <ActiveTakeOffRunway> <Runway>R01L</Runway> <Probability>0.4</Probability> </ActiveTakeOffRunway> <ActiveTakeOffRunway> <Runway>R01R</Runway> <Probability>0.3</Probability> </ActiveTakeOffRunway> <ActiveTakeOffRunway> <Runway>R28L</Runway> <Probability>0.3</Probability> </ActiveTakeOffRunway> <ActiveLandingRunway> <Runway>R28R</Runway> <Probability>0.6</Probability> </ActiveLandingRunway> <ActiveLandingRunway> <Runway>R28L</Runway> <Probability>0.4</Probability> </ActiveLandingRunway> </Airport>