I think the dynamic ones work pretty well now though. It will use whatever is defined or create them dynamically for parking defs without fixed ground routes. DynamicTaxiRoutesOnly field added - normally set to 1 (true) but can be set to 0 if the airport creator still wants to use some custom ground routes.Can set data you want in the labels like telemetry info, airport info, aircraft type.Can set min and max draw distances for labels.Can turn labels on or off as well for planes on the ground.Color/brightness options for arriving traffic, departing traffic, or transiting traffic.Labels for AI aircraft which you can turn on and off to identify aircraft near you.Aircraft base file format modified to include particle placement x/y/z fields for particle emitters.Particle effects for contrails (wing/engine), tire smoke, afterburner flame.allows for user-defined VFR airspace exit points so ATC can vector VFR flights to these positions.has interface for other 3rd party ATC products.user may be required to make speed changes or enter holding patterns to maintain separation.requires that users use valid ATC frequencies with frequencies listed on display.
I defined special cases to deal with the taxi network lines extending to parking spots or cases where the plane just has to back up to the taxi network. Unless you want to give them priorities or assign some as for international terminals or modify push-back but even the latter should mostly work now in this update. And you shouldn't need to define parking defs I've tried to make things be as automatic as possible now in WT 3.5 so you shouldn't need to define ground routes.
0 kommentar(er)
