86
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
Updated Base Groundnet Verification 7.4 & 7.5 Sections
mNo edit summary |
(Updated Base Groundnet Verification 7.4 & 7.5 Sections) |
||
| Line 432: | Line 432: | ||
Your groundnet does not need to cover 100% of the airport taxiways; certain areas (like De Icing stations or Engine Test Areas) will not be used by AI aircrafts. In essence draw just enough routes so that all gates and runways are connected. | Your groundnet does not need to cover 100% of the airport taxiways; certain areas (like De Icing stations or Engine Test Areas) will not be used by AI aircrafts. In essence draw just enough routes so that all gates and runways are connected. | ||
'''Step 4 : Visual Check''' | |||
Once your base groundnet complete, Check visually that your parking positions do not overlap, that nodes placed on physical runways are marked as such and that intersections are formed properly (no node unless the aircraft can turn here) | |||
[[File:Base GRoundnet Visual Check.jpg|border | center|1200px|Base Taxidraw Groundnet for SBGR]] | |||
'''Step 5 : Structural Check and Test''' | |||
Run the verification tool (available in both Taxidraw and FGAirports). Both programs will ensure at this stage that routes are valid and that nodes on runway are marked as such. | |||
Taxidraw does not check the routes structures individually but rather that a route solution exist: If an aircraft can use different path/routes to go from its ParkPos to a given runway threshold and even if one of these routes is "broken" (unconnected segments) no error will be reported, because the aircraft could use another (unbroken) route to get to the threshold and hence still has a routing solution. | |||
FGAirports will do the same routing check but will also signal any unconnected node (broken routes) | |||
Correct the errors found and re run the verification tools until no more problems are found. | |||
Time to test with 'real' traffic. Save your groundnet and export it to a custom scenery folder (NOT to the Terrasync Folder), usually something like F:\My Sceneries\Airports\S\B\SBGR.groundnet.xml. | |||
Startup Flightgear and add your custom scenery folder path (the parent of \Airports) to your extra sceneries list in the Add On screen. Select your Airport as Startup Location. Run | |||
What to expect (normal behaviour with base groundnet, if FG has AI traffic at the airport): | |||
* Parked aircraft will start appearing on the parking stands you have set. Departing aircrafts will light up (red/green nav lights on wing tips) | |||
* Upon ATC clearance (automatic) Departing aircrafts will roll forward into the terminal buildings then dance around a bit then join a taxiway and head for a threshold. The route they will use may not be the shortest nor the one you expected but it will be a route you have set. | |||
* Departing Aircrafts will queue up at the threshold. The first in line will enter the runway, accelerate (strobes lights activate) and take off. Aircraft will climb in a straight line and after +/- 10 seconds, change heading. At this point, the next aircraft in line will enter the runway and initiate its take off | |||
* After 10 minutes, arriving aircrafts will start landing. The touchdown position will depend on the type of aircraft. Arrivals are not spaced out and you can have more than one aircraft landing at once on a single runway. After slowing down, they will taxi all the way to the end of the runway, the the access route you have set then head for an available parking position. Again the route they will use may not be the shortest or the one you expected and they may not park where you wanted. Once parked Nav Lights will be turned off | |||
What to look for (abnormal behaviour with base groundnet, if FG has AI traffic at the airport): | |||
* Aircraft appearing in the middle of the airport and not following taxiways (not enough Parking Positions or not suitable in size or type CARGO/GATE) | |||
* No aircrafts (no AI traffic at this airport or not activated in FG options) | |||
* Aircrafts queue up at runway but do not take off (Misplaced Threshold in ICAO.threshold.xml) | |||
* Aircrafts queue up at taxiway intersections (intersection has more than 3 'branches") | |||
'''This Section is under revamp''' | |||
=== Refining the network: Routes, Circuits and Flow === | === Refining the network: Routes, Circuits and Flow === | ||