Howto:Understand console output: Difference between revisions

Howto:Understand console output (view source)

Revision as of 21:12, 21 November 2019

38 bytes removed , 21 November 2019

+-link: Interactive traffic → AI Traffic

Johan G

Administrators

13,208

edits

@@ Line 137: / Line 137: @@
 === Gate ... doesn't seem to have routes associated with it ===
-A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.
+A startup location in the [[AI Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.
 === glLinkProgram "" Failed ===
@@ Line 226: / Line 226: @@
 === Traffic manager could not find airport ===
-There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.
+There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[AI Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.
 === Unable to choose requested pixel format ===
@@ Line 232: / Line 232: @@
 === Unable to find airport details for .... in FGTower::Init() ===
-This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].
+This error can be surpressed by disabling [[AI Traffic]], via the AI/ATC [[menu]].
 The error appears when an airport in <tt>[[$FG ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG ROOT]]/ATC/default.tower</tt> and <tt>[[$FG ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.