Broadway

Members
  • Content count

    15
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Broadway

  • Rank
    Flight Student - Groundwork
  1. This is how it looks now, after the latest AIRAC-Update:
  2. In the manual you have copied in your answer you see the Command "DIRECT TO AND JOIN". This in fact addresses what I have answered you in my very first answer above. You direct your plane to LIMKO and there it automatically joins a given procedure. My second answer addresses the "JOIN PROCEDURE" command, used to command a procedure explicitly. The manual indeed only gives an example of a procedure name. In both cases it is important to route the plane to LIMKO, as this is the initial fix for the procedure starting there. The reason for the exchange of the "R" with an "H" is the different AIRAC. Procedure names have changed with the AIRAC that is valid since yesterday. While in AIRAC 1703/1704 "R30_X-LIMKO" has been the name of this RNP-procedure, the name changed with AIRAC 1706 to "H30_X-LIMKO". When you update your AIRAC data, you will no longer find "R30_X-LIMKO" in the procedures, but "H30_X-LIMKO" instead. You can easily verify this by inspecting and comparing the procedure file (LLBG.txt in the PROC subdirectory). It is of course easier to verify it by looking into the charts, in case you have access to them. So the procedure name to command is always identical to the one listed in the PROCEDURES-tab. HTH
  3. There is no ILS on Runway 30 at LLBG. The Approach Procedure selected above is the RNP. Anyway, to explicitly command the procedure, you can do it like this: (See the command examples in the Manual, page 12.) In the attached animation you can see how the plane confirms the destination LIMKO first and then confirms the procedure. Just watch the command line and the information on the screen. HTH :-) (Edit: Please not that I am already on AIRAC 1706 and the procedure name has slightly changed.)
  4. The attached image shows what happened after giving the command ACA5894 D LIMKO So this works just fine. Alternatively you could just mouse-drag the plane to LIMKO to get the same result. HTH
  5. LIDO charts here to stay?

    Why do you (or anyone) consider the LIDO charts being superior over the Jeppesen charts? I am just curious and have not decided for either LIDO or Jeppesen... Thank your for any insights...
  6. Airfield Creation for Trainee ATC'er

    I am not sure this is in the AIRAC data... However you can set the Initial Climb Altitude in the 'Procedures' on the right panel. Or you can set it using the Airport Editor. However this setting appears to be dependent on the elevation of the airport. For example at Schiphol (EHAM=-11 ft AMSL) you can set an Initial Climb Altitude of 1500 ft, while at Innsbruck (LOWI=1907 ft AMSL) you obviously can't. HTH :-)
  7. Airfield Creation for Trainee ATC'er

    Hey James, good to hear that you have managed it so far! One question concerning your additional issue: Are you talking about the "Initial Climb Altitude"? Best Broadway
  8. Airfield Creation for Trainee ATC'er

    Not sure, if this meets your needs, but here are at least some tips: - In the airports.txt file of Navigraph AIRAC 1702 you will find 974 Airports with a runway 07/25 - In the airports.txt file of NavDataPro AIRAC 1701 there are 681 Airports with a runway 07/25 I don't know about the surrounding terrain of course, but what you can of course do is search all of them until you find flat land around. You can edit every file using a capable text editor. So even if you find an airport with multiple runways you can remove or comment out the runways that you don't need. Just take a look at the files inside the NavDataPro directory and it's PROC subdirectory. You will find a lot of interesting information inside. Also there is an airport editor within the software that might be useful. HTH :-)
  9. GATC Server List

    Assuming you are looking for a multiplayer game please see the manual (page 13). It is stated there that multiplayer games can only be played via LAN and not via the Internet. So it appears that there are no public servers for multiplayer games, sorry.
  10. GATC 1.1.12 with Airac 1701

    Sure. Find NavDataPro AIRAC cycles here: http://en.shop.aerosoft.com/eshop.php?action=article_detail&s_supplier_aid=11688&s_design=DEFAULT&shopfilter_category=Flight Simulation&s_language=english Or from the competitor NaviGraph here: https://www.navigraph.com/FmsData.aspx You can purchase either only one cycle, 4 cycles a year or 13 cycles a year.
  11. GATC 1.1.12 with Airac 1701

    I have found the reason for this irritation: Inside the NavDataPro/PROC - folder you will find the file KORD.txt, containing lines as follows: This is the reason why every departure has to be directed to "ORD", using ID D ORD Now, to prevent this and make the simulation realistic again just comment these two lines out, as follows: As a consequence the departures will have to be directed to other and different fixes, now. So you need to inspect the NavDataPro - Proc file carefully, in case you experience problems like this. For comparing purposes I bought AIRAC 1701 from Navigraph, too. Those two lines mentioned above are not included in the respective KORD.txt from Navigraph, so you don't experience this surprising behaviour with it.
  12. GATC 1.1.12 mit Airac 1701

    Ich habe die Ursache gefunden. In der Procedure-Datei KORD.txt (zu finden im NavDataPro/PROC - Verzeichnis) findet man folgende Zeilen: Diese bewirken, dass jeder Start über den Fix "ORD" abzuwickeln ist. Somit muss jedes Flugzeug tatsächlich nach dem Takeoff mit ID D ORD kommandiert werden, also zum Flughafen geschickt werden, damit es übergeben werden kann. Die Lösung: Einfach diese beiden Zeilen auskommentieren, also Dies bewirkt, dass die startenden Flugzeuge nicht mehr alle nach ORD geschickt werden, sondern zu anderen Fixes. Man muss sich also die NavDataPro Proc-Dateien gut ansehen, wenn man solcherlei Dinge bemerkt. In der enstprechenden Navigraph AIRAC 1701 - Datei (habe ich mir zu Vergleichszwecken NavDataPro - Navigraph einmal gekauft) ist der oben genannte Eintrag gar nicht erst enthalten. Damit erlebt man diese Überraschung also nicht...
  13. I need your help, please: I have just updated GATC Airac data from the shipped 1309 to the latest version 1701 (NavDataPro). Now I find some airports turn out as being partly unplayable. For example Chicago O'Hare (KORD): There are no more SIDs to clear starting planes to. Well almost, as there is one SID for all, called "ORD2", that is in fact "ORD". So in order to handle starting planes over, they have to fly right to the airport they started from after the start.... that's strange isn't it? This is for every starting plane. No other point to direct them to... planes will hold at any other points. It was different with 1309 data, for sure. What is buggy? The simulation or the data or am I missing something (being quite new to this...)? Thanks for any insights....
  14. GATC wird ja mit den Daten Airac 1309 ausgeliefert. Um die Daten zu aktualisieren habe ich also ein Abo NavdataPro abgeschlossen und auf Airac 1701 upgedated. An einigen Flughäfen stelle ich Veränderungen fest, die die Simulation unspielbar machen. Ein krasses Beispiel ist Chicago O'Hare (KORD): Dort gibt es keine SIDs mehr, bzw. alle Starts sind tatsächlich über ORD2 (=Waypoint ORD) zu clearen. Jedes startende Flugzeug muss also zur Übergabe nach dem Verlassen der Startbahn über den Flughafen fliegen.... das kann nicht realistisch sein. Das war mit Airac 1309 noch anders. Passen die neuen Airac-Daten also (zumindest teilweise) nicht mehr zu GATC? Ist das ein Bug oder ein Feature?
  15. Was macht man in dieser Zeile?

    Dort gibt man die Kommandos in Textform ein. Im Handbuch stehen alle möglichen Kommandos, oder auch im Programm unter Help - Commands.