Jump to content

Jarkko

Members
  • Content Count

    725
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by Jarkko

  1. And please read my previous post again. ATC program AIRAC support and flight planning are two completely different things. VoxATC for example has no way to generate a route or a flight plan for you. You have to create it outside of VoxATC (just like PF3). But... Unlike PF3, VoxATC has full AIRAC support. After you have imported your flight plan, ATC will automatically know all the real world approaches, SIDs/STARs, transitions, speed and altitude restrictions. Real ATC should know these things and this is what VoxATC, Pilot2ATC and ProATC are able to do (because of the AIRAC support)
  2. AIRAC support and flight planning are two totally different things. Programs like VoxATC, Pilot2ATC and ProATC have true AIRAC support. This means that the ATC is aware of the current real world approaches, SIDS/STARs, transitions and all of their speed and altitude restrictions automatically (without user interaction). This is somethings that VoxATC users have gotten used to but something that PF3 is unable to provide.
  3. PF3 doesn't have AIRAC support so it might not be a suitable option for VoxATC users.
  4. You will have to start descending to FL070 and also keep flying the holding pattern.
  5. I took the plunge and upgraded from ASN to AS16. Only one flight done, but it was enjoyable. At least similar performance as ASN, maybe even better. Early days, but not buyers regret so far.
  6. My thoughts exactly I wonder if the SimAir contest winner are still simmers?
  7. This is not true. In the new version, you can add any airline to the database, real or fictional. I've even made instructions on the forums how to add Alaska Airlines to the database in the new version. Also the 3rd party voice sets have voice version of Alaska. Just add the correct ICAO code and callsign to the database and you are good to go. No need to hack your own wav files.
  8. The flight plan info is your digital ATIS (D-ATIS).
  9. European airports have started to support Constant Descent Operations in order to save fuel and reduce noise. So unlike STARs in US that end with vectors, STARs in Europe contain "merge points" that allow the aircraft calculate optimal descent profile and skip vectors. An example from ENGM: "ENGM STAR is based on Point Merge System (PMS) and accommodates Basic Continuous Descent Operations (B- CDO). Each STAR contains segments forming a curved sequencing leg equidistant from the Merge Point (MP). The sequencing leg shall be regarded as a delay manoeuvre for use during periods with heavy traffic. All STAR procedures are described from the start point via intermediate waypoints to the MP, from where an instrument approach procedure commences. Arriving aircraft established on the STAR can expect clearance direct to MP when traffic permits. Succeeding aircraft will subsequently be cleared direct to MP when sufficient spacing to preceding aircraft is obtained. Hence, a precise sequencing can be achieved whilst the aircraft maintain own navigation (LNAV). When cleared direct to MP and also having received an instrument approach clearance, the aircraft shall follow the transition from MP to final as stated in the relevant instrument approach procedure.” - ENGM AD 2.22 Flight Procedures" So if traffic permits, you won't receive vectors.
  10. I would advise that you would be join the official support forum. These questions have been covered there. Thanks!
  11. Like explained 7 posts up. This is not interaction between AI and ATC, but generic real world ATC chatter. User can choose to have the generic ATC chatter on or off (will not affect interaction between ATC and AI).
  12. As mentioned in this thread, there is no demo available for ProATC. Youtube videos are the next best thing.
  13. Time acceleration isn't officially supported as it may cause missed waypoints. Some users are using time acceleration, and here's how: Come out of time acceleration waypoint or two before your last enroute waypoint, check that you are on the correct frequency, if ATC isn't tracking to the same waypoint, request direct to the waypoint, the aircraft is flying to. PFPX and ProATC's flight planner are two different things. ProATC's "flight planner" is more like an IFR flight plan entry form with the added possibility of generating a route for you. I personally don't use routes generated by ProATC, because using real world routes gives you better results. Real routes have been validated and optimized by a human, which also makes ProATC work better. For fuel planning, takeoff and landing calculations, route validation, optimal flight level calculation and so on, PFPX is the tool you want (if the aircraft's that you fly are supported by PFPX).
  14. Just get you up and running faster, you could try copying my options that I've been happy with when flying advanced aircraft's: As for the co-pilot. It's only meant to work with aircraft that follow the sim's normal autopilot and system signals. It will not work PMDG aircraft. I'm personally extremely happy with FS2Crew co-pilot. As for the Johannesburg incident, you are not hearing ATC talk to AI, you are in fact hearing generic real world ATC chatter. It can be turned disabled if you want. (FWIW if no ATC chatter can be found for your area, ProATC will fallback UK chatter. You can also add your own regional chatter or purchase from 3rd party sources such as http://realatc.net/RealATC.htm)
  15. +1 I have been saying this for years. At the moment, there isn't one product that does it all. You have to choose the ATC product that does all the things right that are a must for you. This is also why I (have to) switch between 3 ATC programs depending on the type of flight I'm doing.
  16. Yes and no. ProATC can be configured to add SID/STAR waypoints to the default FSX flight plan (even during the flight). This way you can use ProATC even with the default aircraft that do not have AIRAC support. For advanced aircraft, like the Airbuses and the PMDG kind, SIDs and STARs are not exported in the flight plan.
  17. Thanks for posting the steps! The first item on the list is the same for VoxATC and Radar Contact, but... the challenge was: "No external programs allowed". SimBrief falls under external programs. For item 4, you will also have to use some program or source for the altitude restrictions and missed approach data. This is why it wouldn't fit the "use only the tools available in your ATC program" criteria. You are not doing anything wrong. AFAIK the data gets erased (from the flight plan display version) on purpose because the SID/STAR isn't always available for all runways (especially in Europe). This way the flight plans are re-usable. No need to create runway specific flight plans. Having said that, I do agree, that it would be nice if the entered SID/STAR would not be erased from the flight plan display version, because ATC could always override the flight plan SID/STAR if need be.
  18. Creating a flight plan can be fun when you can import your route in real world format. As far as I know, only ProATC (and maybe Pilot2ATC?) can do this. --- Here is an ATC program flight plan challenge: Let's use a simple test case (SID and STAR serving most wind direction, only one airway): http://flightaware.com/live/flight/DAL128/history/20161026/1658Z/KSEA/KLAX Describe the steps needed to import the flight linked above into your ATC program of choice. NOTE: No external programs allowed, use only the tools available in your ATC program. Also mention what kind of modification are needed for both KSEA and KLAX pretending that you haven't modified these in any way before. --- I'll go first with ProATC: 1. Choose: Flight Plan > New from copy/paste. 2. Enter (the route in the FlightAware link): KSEA SUMMA9 LKV DCT FRA J7 DERBB SADDE7 KLAX 3. Select aircraft type. 4. Select flight level FL330 (as per the link). 5. Click save. That is it. Your (real world) flight plan is now stored and ready to be used any time you like. No need to set transition altitudes, SID/STAR/airway/transition waypoints, safe altitudes and so on. All those things are read from the AIRAC. Also no need for external programs or hand made modifications to the airports.
  19. In my book, there aren't any ATC programs better than the default ATC, sound wise I mean. Having said that, it's also very limited in functionality and therefore doesn't require a large vocabulary.
  20. Like Glynn mentioned, Navigraph is one of the AIRAC providers, the other is Aerosoft, which is also supported. FSGlobalWeather is supported, as are ActiveSky and Opus for example.
  21. Did you even read the post? How is my EFHK example invalid? Please explain how my example is "absolute nonsense!". Did you also note my edit that I added to the post? EGLL STARs are the exception to the rule, not the norm. This is why I added the EDIT to the post you replied to. EDIT: So yes, my statement about BIG being the first waypoint was wrong. I realised this when I looked at the plates and noticed, that EGLL STARs are more like STAR transitions. My original argument still stands: It was claimed that weather can't surprise an ATC program if you check TAF before the flight. I explained how this can happen with programs that do not read the AIRAC data. I then added EFHK as an example so anyone can go and look up the plates and see how little there is similarity between STARs starting from your normal STAR entry point. So if you do not manually enter data for each runway and for each entry point (and update the values every 28 days for each AIRAC cycle), you will get surprised by the weather sooner or later (with these couple of programs).
×
×
  • Create New...