Jarkko

Aren't you the individual who posted the same thing on a different thread? EDIT: Found my answer to your post: http://www.avsim.com/topic/475950-proatc-x-v17-released/?p=3308164 I even recorded video that shows that your example flight works perfect with ProATC 1.7 (my flying though was terrible, almost stalled twice...). Judge for your self if it works as I described in my answer to your original post. Complete flight on Twitch, no edits: 03:50 Departure clearance 19:29 Taxi clearance 23:50 Takeoff clearance 30:32 Arrival clearance 38:23 TOD 51:00 Cleared for approach 53:00 Landing clearance Once more. Please join the forums and please post a log. More than likely you haven't imported AIRAC or aligned scenery with the AIRAC. Both are mandatory for ATC to work. Hard to tell without proper info.

I haven't tested this yet, but it seems that the requested feature is already supported but in a bit different manner. Have a look here: At the left bottom, you should be able to set the Controller In-sim text to None. Once again I haven't tested this yet, but at the moment it would look good. The difference is, that you wouldn't see the text on the laptop/networked computer like you would, when using WideFS. You would check the ATC instructions from the ProATC's moving map.

Not changed in the new version. Sounds behave as before. Above alpha117 mentioned that this could change. I would like to add a bit of expectations management: To support correct airline codes, a real person must sit down and record the correct callsign and all the ATC commands needed. If you go here: https://en.wikipedia.org/wiki/List_of_airline_codes and spend a few minutes reading out loud every callsign on the list, you can start to see, how much work it would be to record only the callsigns, let alone all the things ATC might instruct you to do during a normal flight. Hope this helps to explain, why this isn't just a minor change.

Just flew the same route with ProATC 1.7 and I have some good and bad news. The bad news: My flying sucked today. The good news: ATC worked without a problem. I was given the same SID as PFPX had selected. Taxi instructions were N, D to runway 09 (from gate 40). On departure, initial altitude was 5000. Then a climb to FL110 and FL190, which was my cruise level. ATC gave me descent before my aircraft's TOD so all good there. Arrival was TESBI1M to ILS04L. Step downs were FL100, FL070, 4000ft and 3000ft (IIRC). Not once was I given an altitude below altitudes on the plates. After landing, I accidentally took a high speed exit to the right even though ATC instructed me to exit left. Even so, ATC gave me taxi instructions after vacating. So a good flight. Please join the ProATC support forum and let's get you up and running!

First things first, ProATC doesn't generate the flight plan for you until you have read back your clearance. Second: Please do the tutorial flights in the manual. This will help you get started. Third: A bit more details would be appreciated. What was the flight plan? Which route? Which aircraft profile in use? Which flight level? With this info, I could do the flight for you and post the results on Youtube. Final words: Please post this info on the ProATC forum with a log attached and will help you get started. Thanks!

Hello Pete! Yes, they are exclamation points As the exclamation points (indicating "at" altitude restriction) are in the 1.7 release, I will pass your good point to the developer.

@NyxxUK: Just in case you do not have access to ProATC, here are the waypoints ProATC would expect you to pass in transition between STAR exit and ILS27 approach in the EGNX case: The picture shows, that you would exit ROKUP at 8000ft. You would then fly the transition as instructed in the plates. The last transition waypoint (D116X in ProATC database) should be crossed at or above 3000ft.

A few disclaimers before I explain the moving map: 1) Text version of the ATC clearance is currently always displayed on the sim's green bar. Based on your request, I'm going to suggest to the developer, that there would be a new option to not display the green bar. 2) The picture below is from a very old version (1.2 beta if I remember correctly). Moving map has been enhanced since, but the old picture contains the info I was referring to (this was the only screenshot I could find in a hurry). The info I was talking about, is on the middle, left hand side (Inflight-info, just below the second "Current Weather" button). It contains the current ATC frequency, heading to fly (while vectoring), assigned altitude. Other useful pieces of info are the origin and destination weather, Assigned departures, arrivals and approaches are also shown on the moving map.

Unfortunately there isn't a way for me to check this in a reasonable timeframe. I would have to go though all the sound sets to check and verify. (I dont' have deep enough knowledge of ProATC to do this quickly) At the moment, it's safer for me to say, that Cityhopper isn't pronounced correctly. That way I won't cause you a disappointment as I can't verify.

I don't think there is such a list at the moment.

Here is how you do not need an extra pair headphones: I have a cable going from from laptop's headphone output to my sim computer's audio input. This way you can use single pair of headphones for listening both to the sim and the ATC. You can even loose the headphones if you have speakers attached to your computer.

Even though this wasn't asked from me and I'm part of the ProATC beta team, here are my two cents: I have years of usage out of ProATC, VoxATC and RC4, but... When ever I don't feel confident flying online, I will end up using all three for training. Here is why: - After using ProATC, I'm confident, that I can fly the holds, procedure turns, transitions and maybe even missed approaches as they are meant to be flown (note to self: I should fly missed approaches more often). - When I don't feel confident enough to speak to ATC, I will do a refresher flight with VoxATC (or with RC4 + It's your plane) - When I feel like becoming "Children of Magenta", I will fly with RC4 so I know that I can manage without LNAV/VNAV holding my hand. So what I'm saying is, that at least for me, there isn't an ATC program to rule them all. All have features that I wished the other programs had. It's about using the one that suites your needs or the type of flying you like to do.

Not that I know of. To be honest, with FS2Crew, I've gotten so used to the green bar, that I didn't realise, that it can be disruptive. But now that you have mentioned it, I can see what you mean. Programs that use FSUIPC/WideFS (RC4 and PFE) get this feature out of the box, but as ProATC uses SimConnect, I'm don't know what kind of changes would be needed. I will pass the suggestion along and let's see, what happens. Quick way about this might be an option to disable the sim text, as all the info given to you by the ATC can be seen on the moving map after you have read back the clearance.

I'm still saving up for v3 so I can't say from experience, but users have reported using ProATC with v3 without problems.

1) "Runs distributed over a network?" ProATC runs over the network using SimConnect. I prefer to have ProATC on my laptop so I can have ProATC's "Moving Map" open during the whole flight. The moving map displays the the airport layout so in case you do not have maps for your airport, you can taxi by looking up taxiways from the map. Also waypoint altitude restrictions (and ProATC's TOD) are shown on the map, so you can even fly without plates if need be. Other useful information is the weather info and the frequencies in use. 2) "Stable?" Has been since 1.4. So far, no problems for me with 1.7. 3) "Adheres to proper procedure and terminology". Not possible and haven't seen this done by any ATC add-on. There is too much variance around the world in what is considered "right". Europe is a small place and still you would be hard pressed to find two countries that operate the same way. ProATC uses terminology that can be understood around the world. 4) "Handles VFR and IFR flights?" Only IFR. No plans of VFR support that I know of. 5) "Active, helpful customer support?" I would like to think so, as I've been one of the forum moderator for the last 2 year With the launch of 1.7 a completely new customer forum has been opened.

ProATC doesn't override the default ATC. When you run ProATC, you can go to to the sim's sound menu and disable voices. This way the two ATC's won't talk over each other. ProATC also has it's own dedicated in-game menu so it will not mess with the default ATC. Then the saved flights. In theory, you could resume a saved flight about 25-40nm from TOD all the way to landing (at least ones). Having said that, there are dedicated tools for practicing approaches (was it FSIPANEL?), that would suite better for this type of training, than ProATC (at least in my opinion).

Hello! VFR is not supported. Only IFR and for optimal results, origin and destination should have SID/STAR in place. By saved flights, do you mean 1) flying the same saved flight plan multiple times or 2) saving/stopping flight during cruise and continuing later on. 1) is supported 2) should be supported, but not if you are already in the arrival phase of the flight. I'm not sure if you can only resume from cruise more than once though. To be honest, I haven't used these features as I always create my flight plans from scratch (a lower/higher altitude might save fuel based on winds, old route might not be valid after AIRAC cycle update and so on). Hope this helps!

Absolutely. I prefer an ATC program that get's me from gate to gate doesn't try and fly me into a mountain. I also love the MadDog and the MD11 even though they do not have modern VCs or liveries for my favourite airline. Why? Because of the system depth and modeling. In the end, we all prefer different things and this is why it's good that there are plenty of options available for us.

The voices are not computer generated voices. They have been recorded by real humans. When a voice set was recorded, the person recording the callsigns either said the wrong name, or had the old name in the voice set script. A single pilot/controller voice set takes about 4-12h to record in good quality. Then the voice set has to be level matched, split into coded sound sets, noise and silence has to be removed. The final result has to be tested and so on. The whole process can take for days (or weeks, depending on how many iterations are needed). This is the reason, why some callsigns are missing or are not read out correctly (at least at the moment). I can understand that for some, this might be a deal breaker. I personally prefer ATC that works from gate to gate using as much of the AIRAC data as possible (departures+transitions, arrivals+transitions, approaches+transitions, missed approaches) over complete voice sets.

About the v3 support, I'll have to quote an asnwer (to a similar question) from the ProATC user's Facebook group: "Works for me P3D v3 + Windows 10"

I don't trust anyone who talks down on me, you can be sure about that. For future reference, I'm not your friend, pal or mate. Yes, the 04s are used up to 6kts of tailwind (and maybe more). Yesterday I would have had 6kts of tail wind and would have been happy to land on the 22s (and that 04 ILS isn't used much as it goes over Cannes). The problem is, that there is no way for ProATC to know that, as info like this isn't included in the AIRAC data. It might be included in the scenery, but Pete Dowson would know much more about that, than I do. FWIW. There isn't anything stopping you from asking for runway 04 if you were assigned 22 for landing. Just do it the same way I requested RNAV instead of VOR approach. ProATC already works the way you want it. If you get vectored during arrival or approach, you are doing something wrong and ATC is trying to correct you. You can check the video. No vectoring during the whole flight.

Go back and read my post again. No one gave me a circle to land. (if my english is hard to understand, then watch the video I recorded) The question was: are you using Navigraph or Aerosoft for the navdata? I have filed a bug report to Navigraph about the corrupted AIRAC. EDIT: On a second though, with a comment like that, you sir are on your own. Shame on me for spending couple of hours trying to help a fellow simmer out...

Ok, so I just completed the flight. I think I found the source of the problem and on my system it isn't ProATC. Do you happen to use Navigraph for AIRAC data? Here is the reason I'm asking: 1) I was cleared for STAR VEVAR6C and VOR22R-A approach with NERAS transition First problem: I flew the route with Aerosoft's A320 and it failed to load the NERAS transition for the assigned approach. Aivlasoft's EFB and ProATC contained the NERAS transition. 2) As the aircraft didn't have the needed transition, I requested RNAV22R from ProATC and I was cleared for the RNAV approach with NERAS transition. Second problem (and this is a big one): Navigraph's 1508 cycle's LFMN is corrupted for all programs I have. I loaded RNAV 22R with NERAS transition in Aivlasoft's EFB and also in the aircraft. The "good" thing is that all the programs show the same data. The bad thing is that they all now showed the 04L/R approach, instead of the requested 22R approach :blink: So I flew the whole "22R" approach which left me west of the airport at the FAF for runways 04... I had to circle the airport to land at 22R. Also the altitude data for the approach was corrupted. First a hard limit of 3000ft followed by hard limit of 2000ft followed by hard limit of 3000ft. No such up and down jumping required in the approach charts. ---- So my conclusion is that my problems were caused by broken 1508 AIRAC data from Navigraph. How does this compare to your flight? If you are interested, here is the whole flight (including me positioning for a landing on a taxiway instead of the runway => terrible landing): http://www.twitch.tv/virtualfreightdog/b/681710105 or here

A quick answer: 1) N0357 means speed 357 knots 2) A170 means altitude 17 000ft. It has the A in front, indicating that you are below transition level (18 000ft), so you will not be using standard pressure setting while flying at this altitude.

FSUIPC + PMDG MD-11 + FSGRW or ASN