![]() (They are computed from some properties of the aircraft, not flight testing.) Flow Problemsįrom my examination of the small set of airports that I run across while debugging (with something like 3000 airports, I am at best “sampling” the gateway airports), it appears that authors don’t understand how ATC flows work. Note that currently the takeoff/landing requirements for the aircraft tend to be inaccurate. If an AI isn’t placed at an airport, you’ll see exactly why. After it is set, future spawning decisions will be heavily logged under the “ATC” log tag. Starting with beta 7, you can now debug ATC AI placement decisions by setting the art control atc/debug/log_spawn to 1. We also do not limit landing by taxi route width the assumption is that if you have a width-E parking spot, you have a width-E route to the active runway somewhere on your layout. Once static aircraft have been deployed and authors update their airports to use them, the equipment codes should become much more accurate, and at that point we can prevent the AI from landing if it can’t find an equipment code match on a parking spot. So if we start requiring equipment code matches to land an aircraft, we may end up with no AI aircraft at lots of airports. So if you have an airport with a 11,000 foot runway and no size-E or F parking spots, the 747 would have landed in 10.45 but will not land in 10.50.ĪI aircraft will land even if the parking spots don’t match the needed aircraft type – in other words, if you have a size E parking spot for helicopters only, the 747 will still land (and try to park there). Here’s why I didn’t stop this case: without static aircraft, the equipment codes on parking spots is likely to have errors it’s hard to know you get everything right. X-Plane 10.50 adds a new rule: AI aircraft will not be born or land at airports where there isn’t a parking spot wide enough for the aircraft to park. If there are still bugs in X-Plane’s handling of the new apt.dat data, then you have no way of knowing what your airport will look like after we fix those bugs. ![]() WED 1.5 beta 1 is out please do not upload revised airports with WED 1.5 yet. We have a fix in the works for tall buildings blocking the approach path at KLAX I’m hoping to get that into beta 8 some time next week. There are a few fixes that I hope make this finally a “solid beta”: no more flashing airport lights during the day, normal maps back on aircraft, and liveries should work correctly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |