Dave_YVR

Not a clue, I don't really follow those threads in their forums.

No offense, but it's not the program. Most likely something to do with your system or setup. I've installed both UTL and UT2 to test on 4 different builds and many many OS installs over the years and it's never been an issue. Waiting in line to taxi and take off also has NOTHING to do with the traffic program (UTL, TG, MyT6, UT2), it's just part of the poor ATC engine of the sim.

Did you change your res to 1920x1080 and try installing it? TONS of threads about this on the actual UTL forums, should be the first place to check.

It's pretty simple compared to many parts of FSUIPC. Being able to remove specific ai is exactly what you were looking for. Just edit to the dll.xml file located C:\ProgramData\Lockheed Martin\Prepar3D v4. <Launch.Addon> <Name>Traffic Toolbox</Name> <Path>E:\Lockheed Martin\Prepar3D v4 SDK 4.3.29.25520\World\Traffic\TrafficToolbox.dll</Path> </Launch.Addon> Ensuring that the path leads to your TrafficToolbox.dll. After that load up the sim and you will have Traffic Toolbox in the tools tab of your sim, select explorer and it will show you all of the AI loaded within your traffic bubble. Right-click on any and select delete.

Actually, it is possible. Using the Traffic Explorer from the SDK as mentioned above.

You can delete specific aircraft using the Traffic Explorer included in the P3d SDK. It's easier though imo to just turn off the crash detection, the AI engine is incredibly stupid was never meant to simulate real world operations let alone the amount of traffic we try and make it work with.

Similar to Dave's reply, but most commonly it's user error where they've added scenery and not removed conflicting airport files or followed/searched for compatibility threads about those addons.

It's just the inefficiencies of the ATC system of the sim. Unchanged for over a decade. You could at some airports shorten the runway link to where the runway entry point is so that the AI will no longer backtrack, or just live with it at those smaller airports.

In those cases, it's not a layering issue, you need to disable the orbx ade and object files for those duplicate airports.

It could also be a particular model and it's bounding box I think it's called, where the sim thinks the aircraft is much larger than it is. What model have you noticed this happening with?

Why use the WoAI at all these days with P3D? The models for the most part don't work in p3dv4. Much much easier to use the FLai collection alongside PSXseecontraffic or using aifp and plans from AIG etc.

What command are you using to get the jetways to attach to your aircraft?

All good, it's just always a good idea to check the developer's forums first. With FlyTampa's you don't even need to register to have full access.

People have wondered that since shortly after P3d V4 was released and only FT can answer that. The only airport they have advertised as V4 ready from the installer is Boston, but it's easy enough to go grab the updates/fixes ourselves as they have been available for a year and a half on their forum.

At 10% UTL traffic, what was it that didn't work? GSX on its own will show you ALL parking even if it is occupied or too big or small for your aircraft. Is it GSX that isn't giving you options to park or is it the default ATC? Are the spots that you say are occupied, done so by UK2000 static aircraft or from UTL?