Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It is good but a different thing altogether. Vatsim has pretty poor full flight coverage for most areas.
The basic idea is setup pro-atc and the FMC in your aircraft with the same flightplan, initially without SID/STARs. The SID and STAR procedures are then assigned dynamically when you ask for clearance, which you then enter in the FMC to complete the flightpath. Pro-atc can generate and edit the initial flightplan and then export it to the PMDG format for loading into the FMC or you can import flightplans from sources such as simbrief or pfpx into both pro-atc and your FMC. This all goes a bit smoother if everything is on the same ARINC cycle. Once everything is in sync, you get ATC clearance for startup and pushback, taxi, take off, enroute, arrival, approach and finally taxi to gate.
Interaction with pro-atc in the aircraft is done through a separate popup window rather than the familiar atc window, which takes a bit of getting used to. Pro-atc instructions are relayed to you via a scrolling text banner, voice through the primary sound device (you cant easily redirect to headphones) and the pro-atc application which ideally you have up on a second monitor.
Pro-atc can control various aspects of your flight. At a minimum let it control the COM radios for frequency switching when your handed off to different controllers. It can also control the autopilot for a completely hands off experience (particularly in the 777) but isn’t generally recommended.
Missing a waypoint can happen on high time acceleration (16x). If things get out of sync you can direct proatc to proceed to the next waypoint that makes sense.
For my workflow I use PFPX for flight planning then export an rte file for the FMC and a squawkbox file to load into proatc. I previously used simbrief to do this.
proatc is ok but without a trial it takes a leap of faith to buy into it. You can also look at pilot2atc or pf3 which at least have trial periods.