![]() So then, why did Traffic X and Traffic 360 include AFCADs? The answer is because those AFCADS included, amongst other things, parking spot improvements and enhancements to particular default FSX airports for situations where the airport perhaps didn't have sufficient parking spots for the AI planes that Just Flight wanted to fly to that airport. They just need to provide the AI planes, and the jetways in FSX will work. The same applies to Traffic X and Traffic 360, or any of the AI packages for that matter. With that in mind, UT2 doesn't need to include "specially modified" AFCADs to have the jetways work they just need to provide the AI planes. In other words, jetways work at ANY AND ALL airports (whether they be FSX default airports or modified airports) provided an AI plane has an EXITS and doors section in its config file. The jetways in FSX are natively programmed to work for any AI plane that has an EXITS section and appropriate doors configurations in its aircraft.cfg file. Only half an hour? Well that's not as bad as I might have thought then.
0 Comments
Leave a Reply. |