Write the state of each vehicle to the logfile.Open a canvas map which shows the location of the vehicles and service points.Toggle auto movement of vehicles and auto service.The color of the groundnet lines should be yellow, but differs for some unknown reason (lighting effects?) from red to orange. Visualize the groundnet (which is implemented quite inefficiently by multiple models for each length due to the lack of dynamic model scaling).Launch catering and fuel service for an arrived aircraft.Launch an additional vehicle (select in combo box and button "Launch").The fuel truck from Gabriels 737-800 branch.The standard Goldhofert pushback truck with aircraft specific animations removed.When the distance to the airport exceeds 3 NM, GroundServices switches back to "standby" mode, removing all ground vehicles. Initialcount vehicles (scaled by airport size) of each type will be launched at their defined home location and move between the configured destinations (random groundnet nodes are used if nothing is configured).
It reads the corresponding groundnet.xml and ground vehicles are launched as defined in AI/groundservices.xml. When the distance is below 3 NM ( main.minairportrange), GroundService switches to "active" mode. Īfter starting FlightGear, GroundServices goes to "standby" mode, monitoring the distance of the main aircraft to the next airport. It is written completely in Nasal and is derived/inspired from the existing AI subsystem and tanker.nas (except for the way vehicles are moving). The addon currently moves ground vehicles along an airports taxiways and provides simple catering and fueling services. See also AI_Traffic#Ground_traffic_rendering for the modern approach to rendering ground traffic fast on both GPU and CPU.
0 kommentar(er)
